I wrote before about the limitations of hashes as privacy protectors , which leaves us with a notentirely theoretical question: suppose that you have to create atraffic accounting system, but you don't want to keep too much logs . What's the best way to protect user privacy in thissituation?

Our answer is to drop the first octet of the IP address. This givesmuch better privacy protection than dropping the last octet or eventhe last two octets, because it cuts against how IP address space isorganized

There are a number of awkward things about URL fragments, including thatthey commit you to a certain implementation of your page structure ifyou are going to provide cool URLs . At the same time,I believe that they're the only way to make a reference to a part of apage, so they're pretty essential if you want to aggregate informationon a page but still be able to point to specific bits.

For example, WanderingThoughts uses URL fragments to point to thecomments on a specific entry and

Both virtualization and iSCSI are fundamentally 'sharing' technologies,where multiple things use a shared infrastructure. This means that theyhave a shared set of general security risks, pretty much common to anysharing technologies: cross-contamination and base system compromise.

Cross contamination is the ability to interfere with other things usingthe shared environment and to compromise them in turn; having a sharedinfrastructure necessarily gives you a channel to attack other thingsthat are using that infrastructure. This isn't novel, but virtualizationand iSCSI make it