Ian Batten | 1 Apr 2008 10:52

Re: one-to-many messaging


On 31 Mar 08, at 1445, Roland Perry wrote:
> In article <024e01c8932f$4a6e7cc0$e57ea8c0 <at> Jinja>, James Firth
<james2@... 
> > writes
>> On Mon, 31 Mar 2008 13:29:00, Roland Perry wrote:
>>> I wonder why such an easy-sounding inspection of traffic data was
>>> regarded as "too difficult" by ISPs, before BT came up with its  
>>> rather
>>> complex platform to implement "Cleanfeed"?
>>
>> And now I don't quite see what you're saying.  From what I  
>> understand,
>> Cleanfeed was necessarily complicated for both performance reasons
>
> ie It's not as simple as just snooping the traffic data.

Hmm, I suspect it's also a Moore's Law and price of silicon issue.  At  
one point you could shove the entire outbound traffic of a consumer  
ISP through a cluster of Squid proxies, because more than one ISP did  
just that.  What squid does with each request is more complex, more  
resource intensive and more invasive than matching complete GET  
requests against a stop list, so at the time people were Squid-ing  
their entire peering load they could equally well have matched against  
an IWF list.

At the time Cleanfeed was first mooted, ISPs were _not_ Squid-ing  
their entire workload.  I don't know if this was for performance, cost- 
effectiveness, legal or other reasons.  It could be any of those.

(Continue reading)

Charles Lindsey | 1 Apr 2008 12:13
Picon
Picon

Re: Phorm cookies

On Mon, 31 Mar 2008 17:17:15 +0100, Nicholas Bohm <nbohm@...> wrote:

> Thereafter I found that "opt-out" cookies were regularly set on my  
> machine from related sites, which I was not aware of having visited.  
> Only now that I have also blocked "webwise.net" and "a.webwise.net" do I  
> find that the setting of these cookies has ceased.

Odd! That implies some Phormery is already operational. Do you use any of  
BT, VM or Talktalk to access the net? If not, then I would be surprised if  
they were opt-out cookies. Can you show us an actual cookie?

I just connected to www.webwise.net, and it gave me the cookie

PHPSESSID iam84lo8kv8t8pdc7g38gfm760

 from the site www.webwise.com (note .com rather than .net), but that is  
just a normal session-id cookie such as lots of sites will set.

Note that webwise.net, www.webwise.net, webwise.com and www.webwise.com  
are all the same piece of hardware, though a.webwise.net does appear to be  
something different.

--

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131                       
   Web: http://www.cs.man.ac.uk/~chl
Email: chl@...      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5

(Continue reading)

Ian Batten | 1 Apr 2008 12:49

Phorm | Approach to User Privacy | Privacy Slideshow

There's an hilariously inept and unconvincing presentation from Phorm...

http://www.phorm.com/user_privacy/slideshow.php

Nicholas Bohm | 1 Apr 2008 13:00

Re: Phorm cookies

Charles Lindsey wrote:
> On Mon, 31 Mar 2008 17:17:15 +0100, Nicholas Bohm <nbohm@...> wrote:
> 
>> Thereafter I found that "opt-out" cookies were regularly set on my 
>> machine from related sites, which I was not aware of having visited. 
>> Only now that I have also blocked "webwise.net" and "a.webwise.net" do 
>> I find that the setting of these cookies has ceased.
> 
> Odd! That implies some Phormery is already operational. Do you use any 
> of BT, VM or Talktalk to access the net? 

I use Merula Limited - http://www.merula.net/

> If not, then I would be 
> surprised if they were opt-out cookies. Can you show us an actual cookie?

Sorry, I junked them all.  I have unblocked "webwise.net" and 
"a.webwise.net"
while leaving "www.webwise.net" blocked, and will report again if I find 
anything.

Nicholas
--

-- 
Salkyns, Great Canfield, Takeley,
Bishop's Stortford CM22 6SX, UK

Phone  01279 870285    (+44 1279 870285)
Mobile  07715 419728    (+44 7715 419728)

PGP public key ID: 0x899DD7FF.  Fingerprint:
5248 1320 B42E 84FC 1E8B  A9E6 0912 AE66 899D D7FF

Richard Clayton | 1 Apr 2008 13:17

Re: one-to-many messaging


In article <024e01c8932f$4a6e7cc0$e57ea8c0 <at> Jinja>, James Firth
<james2@...> writes

>On Mon, 31 Mar 2008 13:29:00, Roland Perry wrote:
>> I wonder why such an easy-sounding inspection of traffic data was 
>> regarded as "too difficult" by ISPs, before BT came up with its rather 
>> complex platform to implement "Cleanfeed"?

I think the main reason that people thought it was complicated task, was
because it IS a complicated task -- unless of course you merely wish to
block a relatively small number of sites that are not taking active
steps to avoid being blocked; and you don't mind that the system is
trivial for customers to evade.

BT apparently took the view that providing some blocking was better than
providing no blocking at all. They apparently hoped that this might
prevent a few accidental visits (despite there being no evidence that
people ever encountered these sites "by accident") and it might stop the
curious from viewing the sites and becoming corrupted (despite the fact
that the best way of achieving this latter aim is to persuade the search
engines not to display search results that lead to illegal images, as is
now the case).

At the time that BT rolled out their system (and they were not the only
ISP to roll out architecturally similar systems at that time, just the
first to go on the record [because a campaigner leaked news of the
system to one of the Sunday papers]), it could at least be said that the
blocking didn't do much harm (assuming that the IWF list could be
trusted -- which [unlike the recent situation in Finland] does seem to
be the case), and it might do a little good....

However, since that time, I have found [see Chapter 7 of my PhD thesis!]
that it is possible to use the BT system (and other related two-stage
systems) as an "oracle" that will allow you to reverse engineer the
identity of sites on the IWF list -- viz: you can locate illegal image
sites (and since there is a lack of truth in advertising in this area,
that might be a useful service for consumers of this material).

It seems to me that this makes the justification for running such
systems (which never did all that much good to begin with) somewhat
flaky... however, BT (and indeed the Government) do not agree with me!

>And now I don't quite see what you're saying.  From what I understand,
>Cleanfeed was necessarily complicated for both performance reasons 

Indeed so -- the only way that the system could get the necessary
precision to prevent overblocking was to use a proxy to inspect the URLs
being requested, and so (for reasons of economics, performance, and to
avoid other difficulties with proxies) it is necessary to have an
initial stage which arranges that only a small proportion of all
customer traffic passes through the proxy machine.

The amount of traffic is very much an issue here: in a second phase of
their system, BT had to significantly soup up the performance of their
proxies in order to be able to block sites on a very large free-web-
hosting site, because there is very substantial entirely legitimate
traffic to and from that site.

>and legal
>technicalities.

AIUI (and I have never signed an NDA about this system, so some of the
detail I have may be incorrect -- or indeed now significantly out of
date) there was no way around the fact that the "Cleanfeed" system
(Cleanfeed is in fact someone else's trademark, so BT never call it this
in public) drives a coach and horses through any claim for "mere
conduit" exemptions for web traffic.

Their official position was that if this became a significant risk for
them, they'd turn off the system. Since it is still operating, this will
be because they have found that in practice they still have sufficient
other legal coverage for their activities.

>The content of normal traffic is left uninspected.  IP address matching
>(clearly traffic information) re-routes packets to suspected sites hosting
>images of child abuse.  In order to avoid accusations of censorship and
>logistics of IP address recycling, this traffic is then "shunted" via a
>proxy server, which then decodes HTTP layer and checks specific URLs against
>the IWF list.

I don't think it could be said that the system avoids accusations of
"censorship" -- it's just that very few people are prepared to stand up
and say that suppressing access to child abuse images is "censorship".

>The two-stage process ensures there are good grounds for intercept before
>the content of a data packet is inspected.

BT would (I've no doubt) say that the blocking system was part of their
service, and hence the exemption in RIP s3(3) means that their
interception was lawful...  if indeed there is any interception of
content since in practice the system works entirely by inspection of
traffic data.

>Even ardent liberals like myself have to agree that such a system offers a
>good compromise, safeguarding individuals' rights of privacy 

At the outset BT declared that their policy was not to log any details
of traffic through the proxy.  They do however count the number of URLs
that are blocked per day. Early on they published this number, which was
considerably higher than anyone expected....

... the likely explanations for this high number include there being
very large numbers of people who wish to view illegal images [:-(], that
the system was blocking access to material that was to be displayed
within otherwise legal pages [the most likely explanation in my view] or
that prefetching software (designed to speed up web viewing) was
fetching stuff "one click away" from legal sites.

No-one knows which of these explanations is correct (or indeed whether
it was just errors in IWF list causing overblocking!) because no-one
wants to collect the logs and do the research lest they not like what
they find :(

>and access to
>(legally available) content, gives some protection for IP address owners who
>pick-up dodgy IP addresses 

que?

>and helps to some degree prevent access to
>illegal abuse images.

see above -- the degree is somewhat limited IMHO

--

-- 
richard                                              Richard Clayton

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety.         Benjamin Franklin

Nicholas Bohm | 1 Apr 2008 13:57

Re: Phorm cookies

Charles Lindsey wrote:
> On Mon, 31 Mar 2008 17:17:15 +0100, Nicholas Bohm <nbohm@...> wrote:
> 
>> Thereafter I found that "opt-out" cookies were regularly set on my 
>> machine from related sites, which I was not aware of having visited. 
>> Only now that I have also blocked "webwise.net" and "a.webwise.net" do 
>> I find that the setting of these cookies has ceased.
> 
> Odd! That implies some Phormery is already operational. Do you use any 
> of BT, VM or Talktalk to access the net? 

...Repeating previous reply...

I use Merula Limited - http://www.merula.net/

> If not, then I would be 
> surprised if they were opt-out cookies. Can you show us an actual cookie?

Sorry, I junked them all.  I have unblocked "webwise.net" and
"a.webwise.net" while leaving "www.webwise.net" blocked, and will report 
again if I find
anything.

...end of previous reply...

I have just now found the following:

.webwise.net||/||OPTED_OUT||YES||false||0
.webwise.net||/||webwise_status||0||false||0
a.webwise.net||/services/||uid||RespectMyPrivacy956586||||false||0

Nicholas
--

-- 
Salkyns, Great Canfield, Takeley,
Bishop's Stortford CM22 6SX, UK

Phone  01279 870285    (+44 1279 870285)
Mobile  07715 419728    (+44 7715 419728)

PGP public key ID: 0x899DD7FF.  Fingerprint:
5248 1320 B42E 84FC 1E8B  A9E6 0912 AE66 899D D7FF

PeteM | 1 Apr 2008 14:00

Re: one-to-many messaging

Richard Clayton wrote  on 1-04-08 12:17:
> 
> At the time that BT rolled out their system (and they were not the only
> ISP to roll out architecturally similar systems at that time, just the
> first to go on the record [because a campaigner leaked news of the
> system to one of the Sunday papers]), it could at least be said that the
> blocking didn't do much harm (assuming that the IWF list could be
> trusted -- which [unlike the recent situation in Finland] does seem to
> be the case), 

How would we know?

snip
> 
>> The content of normal traffic is left uninspected.  IP address matching
>> (clearly traffic information) re-routes packets to suspected sites hosting
>> images of child abuse.  In order to avoid accusations of censorship and
>> logistics of IP address recycling, this traffic is then "shunted" via a
>> proxy server, which then decodes HTTP layer and checks specific URLs against
>> the IWF list.
> 
> I don't think it could be said that the system avoids accusations of
> "censorship" -- it's just that very few people are prepared to stand up
> and say that suppressing access to child abuse images is "censorship".

Aren't they really? ISTM there can be no argument about that. Of course 
it is censorship. Whether it is *justified* censorship is certainly a 
matter of dispute, but that's a different argument.

It doesn't help rational discussion to blur the meaning of words like 
that, although the pro-censorship side probably favour it as a 
rhetorical trick.

> 
>> The two-stage process ensures there are good grounds for intercept before
>> the content of a data packet is inspected.
> 
> BT would (I've no doubt) say that the blocking system was part of their
> service, and hence the exemption in RIP s3(3) means that their
> interception was lawful...  if indeed there is any interception of
> content since in practice the system works entirely by inspection of
> traffic data.

Be that as it may, what is clearly not lawful is the presentation of 
forged 404s to people trying to access pages on the blocked list.

--

-- 
Pete Mitchell

Paul Graver | 1 Apr 2008 14:10

Re: Phorm cookies


Nicholas Bohm wrote:
> Charles Lindsey wrote:
>> On Mon, 31 Mar 2008 17:17:15 +0100, Nicholas Bohm <nbohm@...>
>> wrote:
>>
>>> Thereafter I found that "opt-out" cookies were regularly set on my
>>> machine from related sites, which I was not aware of having visited.
>>> Only now that I have also blocked "webwise.net" and "a.webwise.net"
>>> do I find that the setting of these cookies has ceased.
>>
>> Odd! That implies some Phormery is already operational. Do you use any
>> of BT, VM or Talktalk to access the net? 
> 
> ...Repeating previous reply...
> 
> I use Merula Limited - http://www.merula.net/
> 
>> If not, then I would be surprised if they were opt-out cookies. Can
>> you show us an actual cookie?
> 
> Sorry, I junked them all.  I have unblocked "webwise.net" and
> "a.webwise.net" while leaving "www.webwise.net" blocked, and will report
> again if I find
> anything.
> 
> ...end of previous reply...
> 
> I have just now found the following:
> 
> .webwise.net||/||OPTED_OUT||YES||false||0
> .webwise.net||/||webwise_status||0||false||0
> a.webwise.net||/services/||uid||RespectMyPrivacy956586||||false||0
> 
> Nicholas

Looks like you are running the Thunderbird add-on 'Dephormation'...

--
Paul Graver - Public KeyID: 0xF4A07485
Nicholas Bohm | 1 Apr 2008 14:23

Re: Phorm cookies

Paul Graver wrote:
> Nicholas Bohm wrote:
>> Charles Lindsey wrote:
>>> On Mon, 31 Mar 2008 17:17:15 +0100, Nicholas Bohm <nbohm@...>
>>> wrote:
>>>
>>>> Thereafter I found that "opt-out" cookies were regularly set on my
>>>> machine from related sites, which I was not aware of having visited.
>>>> Only now that I have also blocked "webwise.net" and "a.webwise.net"
>>>> do I find that the setting of these cookies has ceased.
>>> Odd! That implies some Phormery is already operational. Do you use any
>>> of BT, VM or Talktalk to access the net? 
>> ...Repeating previous reply...
> 
>> I use Merula Limited - http://www.merula.net/
> 
>>> If not, then I would be surprised if they were opt-out cookies. Can
>>> you show us an actual cookie?
>> Sorry, I junked them all.  I have unblocked "webwise.net" and
>> "a.webwise.net" while leaving "www.webwise.net" blocked, and will report
>> again if I find
>> anything.
> 
>> ...end of previous reply...
> 
>> I have just now found the following:
> 
>> .webwise.net||/||OPTED_OUT||YES||false||0
>> .webwise.net||/||webwise_status||0||false||0
>> a.webwise.net||/services/||uid||RespectMyPrivacy956586||||false||0
> 
>> Nicholas
> 
> Looks like you are running the Thunderbird add-on 'Dephormation'...

Now you remind me, yes, I am.  (Though I thought it was a Firefox add-on.)

Nicholas
--

-- 
Salkyns, Great Canfield, Takeley,
Bishop's Stortford CM22 6SX, UK

Phone  01279 870285    (+44 1279 870285)
Mobile  07715 419728    (+44 7715 419728)

PGP public key ID: 0x899DD7FF.  Fingerprint:
5248 1320 B42E 84FC 1E8B  A9E6 0912 AE66 899D D7FF

James Firth | 1 Apr 2008 14:43

RE: one-to-many messaging

On 01 April 2008 12:18, Richard Clayton wrote:
> >The content of normal traffic is left uninspected.  IP address matching
> >(clearly traffic information) re-routes packets to suspected sites
> hosting
> >images of child abuse.  In order to avoid accusations of censorship and
> >logistics of IP address recycling, this traffic is then "shunted" via a
> >proxy server, which then decodes HTTP layer and checks specific URLs
> against
> >the IWF list.
> 
> I don't think it could be said that the system avoids accusations of
> "censorship" -- it's just that very few people are prepared to stand up
> and say that suppressing access to child abuse images is "censorship".

Sorry, I meant over-censorship.

> 
> >The two-stage process ensures there are good grounds for intercept before
> >the content of a data packet is inspected.
> 
> BT would (I've no doubt) say that the blocking system was part of their
> service, and hence the exemption in RIP s3(3) means that their
> interception was lawful...  if indeed there is any interception of
> content since in practice the system works entirely by inspection of
> traffic data.

Hence my earlier mention of inspecting of lawful inspection of incoming
parcels by Customs/Royal Mail.

> >and access to
> >(legally available) content, gives some protection for IP address owners
> who
> >pick-up dodgy IP addresses
> 
> que?
> 

The earlier suggestions were a simple IP-ban, made most likely by naïve
officials who thought they understood the internet.  I lost interest in
Cleanfeed as a topic once it emerged the technical solution was very
unlikely to hinder "normal" operation of the internet. 

> >and helps to some degree prevent access to
> >illegal abuse images.
> 
> see above -- the degree is somewhat limited IMHO

Oh yes, but it's hardly worth protesting about so long as it is completely
transparent.

However, with one major open question: was there a sub-motive to the
roll-out?  It is now technically possible to discretely censor any given
website.

But as you say Richard, it will take a brave group to start arguing for
removal of this type of block.  And that probably goes some way to
explaining why Phishing blocks and the like would never be implemented
within Cleanfeed, in order to keep the motives for the system apparently
above scrutiny. 

James Firth


Gmane