To answer your question: sort of, but with conditions on the intended uses. I’ve written about Detica and CView in this space (a few links at end of my comment) and they seem to have designed an appliance that is meant to engage in surveillance while ‘maintaining’ as much privacy as possible (through the anonymization and aggregation of data). Where this kind of pure ‘traffic management’ approach is taken, it is possible to limit the exposure of private information to ISPs.

I think, however, that this approach I take – minimizing the invasiveness of DPI – is drastically different from any kind of ‘privacy-enhanced’ DPI. An ‘enhancement strategy’ suggests that the device itself is somehow enhancing privacy, which it clearly is not. Think of it like a surveillance camera: you don’t ‘enhance’ the privacy provided by a camera, but recuperate the lost privacy. I focus on the loss -> regain, rather than just the ‘regain/enhance’ because rhetorically I see it as important to acknowledge that there are costs to installing surveillance gear. Sure, there can be benefits as well – and DPI is a great example of possible benefits to carriers, whereas the benefits are more nebulous when dealing with other systems of surveillance – but we should focus on costs when talking surveillance, or at least not obviate them from the discussion.

Such a discussion of costs *shouldn’t* turn to a ‘balancing’ discussion, but be put in the start terms of security (or other desired outcome of the surveillance apparatus) gain and rights loss. The two are not commensurate, as far as I’m concerned, and there isn’t any shame in recognizing this division. Instead, it makes for a more honest discussion of the actual implications of surveillance systems, and avoids the ‘is surveillance a threat to privacy’ nonsense, which is a loaded discussion that (in my view) requires the intermediary of constitutional rights to bridge the divide between surveillance and privacy as issues and concepts in contemporary Western environments.

Many apologies for that bad link, again. I’ve fixed it, and I’ll email along a copy of the article, just to be sure that you receive it!

Links as promised:
http://www.christopher-parsons.com/blog/privacy/aggregating-information-about-cview/
http://www.christopher-parsons.com/blog/privacy/update-to-virgin-media-and-copyright-dpi/
http://www.christopher-parsons.com/blog/privacy/virgin-media-to-monitor-copyright-infringement/

Hopefully now that my 8 month period of exam punishment is over, I’ll be able to both write AND update that feed a little more regularly

In the end, delicious is where I stuff most of my tagged content and I use tags based on my personal organization in delicious. If I feel strongly that I want to share the article, I tend to use Twitter or the share functions of GReader to make sure it gets shared with my network.

The solution was to use BatChmod, a tool that fixes permissions, including ACL.

http://www.macchampion.com/arbysoft/BatchMod/Download.html

Here’s the settings I used:
http://bayimg.com/kakMGaACh

Fixed!

Regards,

Willy T. Koch
Norway