<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Phorm: public meeting announced for next Tuesday</title>
	<atom:link href="http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/</link>
	<description>Protecting your rights in the digital age</description>
	<pubDate>Fri, 16 May 2008 08:03:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: The Open Rights Group : Blog Archive &#187; FIPR calls on Home Office to withdraw misleading advice on Phorm</title>
		<link>http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163599</link>
		<dc:creator>The Open Rights Group : Blog Archive &#187; FIPR calls on Home Office to withdraw misleading advice on Phorm</dc:creator>
		<pubDate>Wed, 23 Apr 2008 14:17:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163599</guid>
		<description>[...] the system is lawful, creating &#8220;an obstacle to the just enforcement of the law&#8221;. At the public meeting attended by Phorm and their critics last week, Simon Davies of 80/20 Thinking Ltd identified the legality of Phorm under RIPA as a legitimate [...]</description>
		<content:encoded><![CDATA[<p>[...] the system is lawful, creating &#8220;an obstacle to the just enforcement of the law&#8221;. At the public meeting attended by Phorm and their critics last week, Simon Davies of 80/20 Thinking Ltd identified the legality of Phorm under RIPA as a legitimate [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Very Worried Messenger</title>
		<link>http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163592</link>
		<dc:creator>A Very Worried Messenger</dc:creator>
		<pubDate>Sat, 19 Apr 2008 19:03:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163592</guid>
		<description>It looks like the ubiquitous Phorm redirects  can be prevented from calling the webwise system by blocking the proper sites using IPSEC rules, I am not sure if some Firewalls run at a low enough system level to achieve this. 

Using the Hosts File to block these sites is problematic as the True IP address can be used to redirect the Web Application instead of the URL address.

This does not however prevent the Packet Sniffing that the Phorm System is doing! ( I consider this totally illegal without the consent of both parties, or for proper legal or operational reasons)</description>
		<content:encoded><![CDATA[<p>It looks like the ubiquitous Phorm redirects  can be prevented from calling the webwise system by blocking the proper sites using IPSEC rules, I am not sure if some Firewalls run at a low enough system level to achieve this. </p>
<p>Using the Hosts File to block these sites is problematic as the True IP address can be used to redirect the Web Application instead of the URL address.</p>
<p>This does not however prevent the Packet Sniffing that the Phorm System is doing! ( I consider this totally illegal without the consent of both parties, or for proper legal or operational reasons)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Very Worried Messenger</title>
		<link>http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163576</link>
		<dc:creator>A Very Worried Messenger</dc:creator>
		<pubDate>Thu, 17 Apr 2008 20:40:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163576</guid>
		<description>The Spotlight needs to be turned on to this Company as well, which appears to be quietly sneaking under the radar whilst the fuss is going on about Phorm!

This also appears to imply direct Packet Examination at the ISP level!
Which is under current UK law illegal monitoring, without the direct permission of both parties in the communication!

Please Note they also state the US Version Opt-out NOT Opt-in (not that this make any difference both are illegal under current UK legislation without the consent of both parties in the communication!) 

http://www.nebuad.com/privacy/uk_servicesPrivacy.php</description>
		<content:encoded><![CDATA[<p>The Spotlight needs to be turned on to this Company as well, which appears to be quietly sneaking under the radar whilst the fuss is going on about Phorm!</p>
<p>This also appears to imply direct Packet Examination at the ISP level!<br />
Which is under current UK law illegal monitoring, without the direct permission of both parties in the communication!</p>
<p>Please Note they also state the US Version Opt-out NOT Opt-in (not that this make any difference both are illegal under current UK legislation without the consent of both parties in the communication!) </p>
<p><a href="http://www.nebuad.com/privacy/uk_servicesPrivacy.php" rel="nofollow">http://www.nebuad.com/privacy/uk_servicesPrivacy.php</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hugh Paterson</title>
		<link>http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163569</link>
		<dc:creator>Hugh Paterson</dc:creator>
		<pubDate>Thu, 17 Apr 2008 10:51:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163569</guid>
		<description>Were the questions from here answered during the meeting or was there a commitment to answer them? I hope to see them answered soon. Thanks</description>
		<content:encoded><![CDATA[<p>Were the questions from here answered during the meeting or was there a commitment to answer them? I hope to see them answered soon. Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Very Worried Messenger</title>
		<link>http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163567</link>
		<dc:creator>A Very Worried Messenger</dc:creator>
		<pubDate>Wed, 16 Apr 2008 11:55:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163567</guid>
		<description>In the light of Recent developments BT need to be asked a VERY DIRECT QUESTION!

What is your description of a BT Broadband Customer &#38; what Information have you released to Phorm about BT Customer Accounts, does it include all users connected to your Broadband Network, whether or not they are a direct BT Broadband Customer! 

This potentially affects Sky, Orange....etc, Customers who are connected to the BT Broadband Network.

Remember that BT is also the Telephone Company &#38; therefore has control of the Master Router/MAC, which can also potentially be viewed by BT as part of their ISP Network!</description>
		<content:encoded><![CDATA[<p>In the light of Recent developments BT need to be asked a VERY DIRECT QUESTION!</p>
<p>What is your description of a BT Broadband Customer &amp; what Information have you released to Phorm about BT Customer Accounts, does it include all users connected to your Broadband Network, whether or not they are a direct BT Broadband Customer! </p>
<p>This potentially affects Sky, Orange&#8230;.etc, Customers who are connected to the BT Broadband Network.</p>
<p>Remember that BT is also the Telephone Company &amp; therefore has control of the Master Router/MAC, which can also potentially be viewed by BT as part of their ISP Network!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alert</title>
		<link>http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163559</link>
		<dc:creator>Alert</dc:creator>
		<pubDate>Tue, 15 Apr 2008 16:10:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163559</guid>
		<description>The following information may explain the problem I highlighted above:
If the IP address is dynamic, in the case of BT or Virgin Media? when the user switches ON/OFF regularly the the user may easily get a blacklisted IP address or vise versa &#38; the surfing of http addresses may become problematic &#38; or erratic!

"AND THIS SUBMISSION ON FIRST ATTEMPT WAS BLOCKED BY MY ROUTER FIREWALL BECAUSE AN ATTEMPT WAS MADE TO RE-ROUTE IT THROUGH A """PHORM""" ADDRESS!!!!!"


27. If the user has disabled cookies for CNN (viz: they don’t record their values and don’t supply them with further requests), then there is potential for an infinite loop – repeating all the 307 responses forever. The Layer 7 switch recognises this situation and records that future traffic (at least for a while) from the particular IP address to the particular (CNN) domain is not to be redirected.

28. If the user has set a cookie within the webwise.net domain indicating that they do not wish to be tracked, then this preference is passed to the Layer 7 switch during the process in paragraph 16 above. The details on how this is done were not explained by Phorm... but it is presumably related to the mechanism described in the previous paragraph.

29. If the user does not accept any cookies in the webwise.net domain then they will always be allocated a new identifier for every website they visit. This situation is detected by the Layer 7 switch and the IP address is “blacklisted” and future traffic is not redirected.

30. Note that the blacklisting of IP addresses by the Layer 7 switch (as described in the three previous paragraphs), whether general, or for particular domains, will apply to all of the users who are sharing a particular IP address, not just users with a particular UID.
However, because the “blacklisting” will time out eventually, the exact behaviour will depend upon the mixture of requests made by different users who have different browser settings.</description>
		<content:encoded><![CDATA[<p>The following information may explain the problem I highlighted above:<br />
If the IP address is dynamic, in the case of BT or Virgin Media? when the user switches ON/OFF regularly the the user may easily get a blacklisted IP address or vise versa &amp; the surfing of http addresses may become problematic &amp; or erratic!</p>
<p>&#8220;AND THIS SUBMISSION ON FIRST ATTEMPT WAS BLOCKED BY MY ROUTER FIREWALL BECAUSE AN ATTEMPT WAS MADE TO RE-ROUTE IT THROUGH A &#8220;&#8221;"PHORM&#8221;"&#8221; ADDRESS!!!!!&#8221;</p>
<p>27. If the user has disabled cookies for CNN (viz: they don’t record their values and don’t supply them with further requests), then there is potential for an infinite loop – repeating all the 307 responses forever. The Layer 7 switch recognises this situation and records that future traffic (at least for a while) from the particular IP address to the particular (CNN) domain is not to be redirected.</p>
<p>28. If the user has set a cookie within the webwise.net domain indicating that they do not wish to be tracked, then this preference is passed to the Layer 7 switch during the process in paragraph 16 above. The details on how this is done were not explained by Phorm&#8230; but it is presumably related to the mechanism described in the previous paragraph.</p>
<p>29. If the user does not accept any cookies in the webwise.net domain then they will always be allocated a new identifier for every website they visit. This situation is detected by the Layer 7 switch and the IP address is “blacklisted” and future traffic is not redirected.</p>
<p>30. Note that the blacklisting of IP addresses by the Layer 7 switch (as described in the three previous paragraphs), whether general, or for particular domains, will apply to all of the users who are sharing a particular IP address, not just users with a particular UID.<br />
However, because the “blacklisting” will time out eventually, the exact behaviour will depend upon the mixture of requests made by different users who have different browser settings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alert</title>
		<link>http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163558</link>
		<dc:creator>Alert</dc:creator>
		<pubDate>Tue, 15 Apr 2008 16:07:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163558</guid>
		<description>The following information may explain the problem I highlighted above:
If the IP address is dynamic, in the case of BT or Virgin Media? when the user switches ON/OFF regularly the the user may easily get a blacklisted IP address or vise versa &#38; the surfing of http addresses may become problematic &#38; or erratic!


27. If the user has disabled cookies for CNN (viz: they don’t record their values and don’t supply them with further requests), then there is potential for an infinite loop – repeating all the 307 responses forever. The Layer 7 switch recognises this situation and records that future traffic (at least for a while) from the particular IP address to the particular (CNN) domain is not to be redirected.

28. If the user has set a cookie within the webwise.net domain indicating that they do not wish to be tracked, then this preference is passed to the Layer 7 switch during the process in paragraph 16 above. The details on how this is done were not explained by Phorm... but it is presumably related to the mechanism described in the previous paragraph.

29. If the user does not accept any cookies in the webwise.net domain then they will always be allocated a new identifier for every website they visit. This situation is detected by the Layer 7 switch and the IP address is “blacklisted” and future traffic is not redirected.

30. Note that the blacklisting of IP addresses by the Layer 7 switch (as described in the three previous paragraphs), whether general, or for particular domains, will apply to all of the users who are sharing a particular IP address, not just users with a particular UID.
However, because the “blacklisting” will time out eventually, the exact behaviour will depend upon the mixture of requests made by different users who have different browser settings.</description>
		<content:encoded><![CDATA[<p>The following information may explain the problem I highlighted above:<br />
If the IP address is dynamic, in the case of BT or Virgin Media? when the user switches ON/OFF regularly the the user may easily get a blacklisted IP address or vise versa &amp; the surfing of http addresses may become problematic &amp; or erratic!</p>
<p>27. If the user has disabled cookies for CNN (viz: they don’t record their values and don’t supply them with further requests), then there is potential for an infinite loop – repeating all the 307 responses forever. The Layer 7 switch recognises this situation and records that future traffic (at least for a while) from the particular IP address to the particular (CNN) domain is not to be redirected.</p>
<p>28. If the user has set a cookie within the webwise.net domain indicating that they do not wish to be tracked, then this preference is passed to the Layer 7 switch during the process in paragraph 16 above. The details on how this is done were not explained by Phorm&#8230; but it is presumably related to the mechanism described in the previous paragraph.</p>
<p>29. If the user does not accept any cookies in the webwise.net domain then they will always be allocated a new identifier for every website they visit. This situation is detected by the Layer 7 switch and the IP address is “blacklisted” and future traffic is not redirected.</p>
<p>30. Note that the blacklisting of IP addresses by the Layer 7 switch (as described in the three previous paragraphs), whether general, or for particular domains, will apply to all of the users who are sharing a particular IP address, not just users with a particular UID.<br />
However, because the “blacklisting” will time out eventually, the exact behaviour will depend upon the mixture of requests made by different users who have different browser settings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alert</title>
		<link>http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163557</link>
		<dc:creator>Alert</dc:creator>
		<pubDate>Tue, 15 Apr 2008 13:13:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163557</guid>
		<description>Just had to deal with a problem concerning a Virgin Media customer.

The customer could no longer connect to several http sites as of this morning, having noticed similar symptoms on BT, indicating Phorm activity!, I was able to advise the customer on how to re-establish connections to these sites.

This however was not an ideal mitigation, it involved altering certain Firewall settings!</description>
		<content:encoded><![CDATA[<p>Just had to deal with a problem concerning a Virgin Media customer.</p>
<p>The customer could no longer connect to several http sites as of this morning, having noticed similar symptoms on BT, indicating Phorm activity!, I was able to advise the customer on how to re-establish connections to these sites.</p>
<p>This however was not an ideal mitigation, it involved altering certain Firewall settings!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Ransome</title>
		<link>http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163554</link>
		<dc:creator>Phil Ransome</dc:creator>
		<pubDate>Mon, 14 Apr 2008 12:13:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163554</guid>
		<description>Where does the routing of packets take place? If we do not opt in (or we opt out) does that mean the ISP will send our packets down the clean route to their destination? Alternatively will the ISP still route everything to Phorm and the opt out will just mean the ads don't get delivered back to our browsers. If the latter then what use is any opt out?</description>
		<content:encoded><![CDATA[<p>Where does the routing of packets take place? If we do not opt in (or we opt out) does that mean the ISP will send our packets down the clean route to their destination? Alternatively will the ISP still route everything to Phorm and the opt out will just mean the ads don&#8217;t get delivered back to our browsers. If the latter then what use is any opt out?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hugh Paterson</title>
		<link>http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163553</link>
		<dc:creator>Hugh Paterson</dc:creator>
		<pubDate>Mon, 14 Apr 2008 09:56:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.openrightsgroup.org/2008/04/09/phorm-public-meeting-announced-for-next-tuesday/#comment-163553</guid>
		<description>http://www.dephormation.org.uk/ is a site presenting tools to prevent, evade, or detect your profiling. In view of the fact that use of such tools constitutes a clear refusal to consent, will you commit to not attempting to work around these tools.

It appears that a website can easily read your cuckoo in their domain by making the web page call for an image by a non-standard port. In view of this, any site or group of sites can easily and conveniently track all webwise-encumbered surfers. Please explain how this enhances their privacy. A website has a right to any cookies (including cuckoos) in their domain.

A surfer can block access to webwise.net. Will this break her browsing? Do you plan to prevent this legitimate reaction to your intrusion?

Do you plan to attach a “profile” mark to the user agent string (or elsewhere) of browsers you are profiling, as a courtesy to the websites, and to permit them to exercise their informed consent?</description>
		<content:encoded><![CDATA[<p><a href="http://www.dephormation.org.uk/" rel="nofollow">http://www.dephormation.org.uk/</a> is a site presenting tools to prevent, evade, or detect your profiling. In view of the fact that use of such tools constitutes a clear refusal to consent, will you commit to not attempting to work around these tools.</p>
<p>It appears that a website can easily read your cuckoo in their domain by making the web page call for an image by a non-standard port. In view of this, any site or group of sites can easily and conveniently track all webwise-encumbered surfers. Please explain how this enhances their privacy. A website has a right to any cookies (including cuckoos) in their domain.</p>
<p>A surfer can block access to webwise.net. Will this break her browsing? Do you plan to prevent this legitimate reaction to your intrusion?</p>
<p>Do you plan to attach a “profile” mark to the user agent string (or elsewhere) of browsers you are profiling, as a courtesy to the websites, and to permit them to exercise their informed consent?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
