<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>HTTPS in </title>
<link>http://www.dslreports.com/forum/r20177830</link>
<description></description>
<language>en</language>
<pubDate>Wed, 02 Dec 2009 19:17:25 EDT</pubDate>
<lastBuildDate>Wed, 02 Dec 2009 19:17:25 EDT</lastBuildDate>

<item>
<title>Re: HTTPS</title>
<link>http://www.dslreports.com/forum/remark,20180191</link>
<description><![CDATA[<A HREF="/useremail/u/856950"><b>jap</b></A> : <div class="bquote"><small>said by factchecker :</small><br><br>Phorm uses an algorithm that scans webpages as they are loaded and finds "key words" and uses them to customize the ads for the user.   The Register had a good summary of how Phorm works a few days ago...<br><br>&raquo;<A HREF="http://www.theregister.co.uk/2008/03/07/phorm_interview_burgess_ertegrul/" >www.theregister.co.uk/2008/03/07&middot;&middot;&middot;rtegrul/</A><br></div>Cripes. I never thought of backtracking to scan referring url. Bastards. No way for a client to detect presence of such a server tool either. Maybe some kind Mozilla user - who doesn't work for a data mining company :uhh: - has created a redirect plugin. Time to locate some form of local referrer washer. <br><br>Thanks for the Register link. Evil for server owners to install such a tool. :mad:<br><br>[reminisces the pre-commercial web days] ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20180191</guid>
<pubDate>Mon, 17 Mar 2008 16:27:51 EDT</pubDate>
</item>

<item>
<title>Re: HTTPS</title>
<link>http://www.dslreports.com/forum/remark,20179655</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : <div class="bquote"><small>said by  TKJunkMail <A HREF="/useremail/u/594412"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>Would it? They would still have the URL you went to whether it was HTTP or HTTPS. So if you went to HTTPS://IhaveCancer.org they would still have that info to sell.</div>They would see the URL, but that is it.   <br><br>HTTPS would definitely go a long way toward foiling Phorm.   Phorm uses an algorithm that scans webpages as they are loaded and finds "key words" and uses them to customize the ads for the user.   The Register had a good summary of how Phorm works a few days ago...<br><br><div class="bquote"><small>said by &raquo;<A HREF="http://www.theregister.co.uk/2008/03/07/phorm_interview_burgess_ertegrul/" >www.theregister.co.uk/2008/03/07&middot;&middot;&middot;rtegrul/</A> :</small><br><br>Explain for our readers how Phorm's profiling system works.<br><br>Marc Burgess: What the profiler does is it first cleans the data. It's looking at two sets of information: the information in the request that's sent to the website and then information in the page that comes back.<br><br>From the request it pulls out the URL, and if that URL is a well known search engine such as Google or Yahoo! it'll also look for the search terms that are in the request.<br><br>And then from the information returned by the website, the profiler looks at the content. The first thing it does is it ignores several classes of information that could potentially be sensitive. So there's no form fields, no numbers, no email addresses (that is something containing an "@") and anything containing a title like Mr or Mrs.<br></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20179655</guid>
<pubDate>Mon, 17 Mar 2008 15:11:19 EDT</pubDate>
</item>

<item>
<title>Re: HTTPS</title>
<link>http://www.dslreports.com/forum/remark,20178428</link>
<description><![CDATA[<A HREF="/useremail/u/612876"><b>gaforces</b></A> : A better solution is to make the data mining backfire on them by inserting a worm into their database that sends info back :) Or it could do worse things ...<br><br>Payback is a mofo. Parse THIS, sucka.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20178428</guid>
<pubDate>Mon, 17 Mar 2008 11:16:42 EDT</pubDate>
</item>

<item>
<title>Re: HTTPS</title>
<link>http://www.dslreports.com/forum/remark,20178040</link>
<description><![CDATA[<A HREF="/useremail/u/214274"><b>russotto</b></A> : But they would not get &raquo;<small>https</small>://<A HREF="https://medicalstuff.org/ihavecancer">medicalstuff.org/ihavecancer</A> -- just medicalstuff.org<br><br>Still, encryption is a very heavyweight solution for a problem that is easier fixed by NOT HAVING THE ISP TRACK MY PACKETS.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20178040</guid>
<pubDate>Mon, 17 Mar 2008 09:56:42 EDT</pubDate>
</item>

<item>
<title>Re: HTTPS</title>
<link>http://www.dslreports.com/forum/remark,20177887</link>
<description><![CDATA[<A HREF="/useremail/u/594412"><b>TKJunkMail</b></A> : <div class="bquote"><small>said by  jjoshua <A HREF="/useremail/u/401000"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> :</small><br><br>Web can use https by default.  Performance may be slower but that's a tradeoff that some sites may be willing to take.<br><br>That would solve the problem.<br> </div>Would it? They would still have the URL you went to whether it was HTTP or HTTPS. So if you went to HTTPS://IhaveCancer.org they would still have that info to sell.<br><small>--<br><A HREF="http://tinyurl.com/bqv2h"><b>My BLOG ..</b></a><A HREF="http://tinyurl.com/2a9xcb"><i> .. Internet News ..</i></a><A HREF="http://tinyurl.com/yz8xto"><b> .. My Web Page</b></a></small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20177887</guid>
<pubDate>Mon, 17 Mar 2008 09:19:17 EDT</pubDate>
</item>

<item>
<title>HTTPS</title>
<link>http://www.dslreports.com/forum/remark,20177830</link>
<description><![CDATA[<A HREF="/useremail/u/401000"><b>jjoshua</b></A> : Web can use https by default.  Performance may be slower but that's a tradeoff that some sites may be willing to take.<br><br>That would solve the problem.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,20177830</guid>
<pubDate>Mon, 17 Mar 2008 09:01:43 EDT</pubDate>
</item>

</channel>
</rss>
