<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: sslstrip, hijacking SSL in network</title>
	<atom:link href="http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/feed/" rel="self" type="application/rss+xml" />
	<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/</link>
	<description>Fresh hacks every day</description>
	<lastBuildDate>Fri, 10 Feb 2012 17:43:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: nobann</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-296487</link>
		<dc:creator><![CDATA[nobann]]></dc:creator>
		<pubDate>Wed, 05 Jan 2011 01:31:21 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-296487</guid>
		<description><![CDATA[Lol
all of you dunno anything
it&#039;s not phishing lol
It&#039;s arp poisoning + redirection through hacker computer then sslstrip do some makup...
if u understand how internet works, you will never feel secure since the lower level isnt secure ...]]></description>
		<content:encoded><![CDATA[<p>Lol<br />
all of you dunno anything<br />
it&#8217;s not phishing lol<br />
It&#8217;s arp poisoning + redirection through hacker computer then sslstrip do some makup&#8230;<br />
if u understand how internet works, you will never feel secure since the lower level isnt secure &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eric fajardo</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-105176</link>
		<dc:creator><![CDATA[eric fajardo]]></dc:creator>
		<pubDate>Mon, 02 Nov 2009 08:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-105176</guid>
		<description><![CDATA[Moxie made a good presentation with defeating SSL over HTTPS. Cheating the traffic to be redirected to solely HTTP is very crafty in deed. This is basically true for public / not-so secured websites like Yahoo and Google and the rest, but I guess finding way to smash in for some corporate traffic would be hard if:

1. Force-all traffic as HTTPS in the infrastructure side.
2. Using a 2FA for all standard, remote access. 
3. Combining 2FA with OTP for all logins.

I believe that Two-Factor-Authentication is not fool-proof though, but it can definitely make a pain in the ass for a guy listening on your wire to gain access.]]></description>
		<content:encoded><![CDATA[<p>Moxie made a good presentation with defeating SSL over HTTPS. Cheating the traffic to be redirected to solely HTTP is very crafty in deed. This is basically true for public / not-so secured websites like Yahoo and Google and the rest, but I guess finding way to smash in for some corporate traffic would be hard if:</p>
<p>1. Force-all traffic as HTTPS in the infrastructure side.<br />
2. Using a 2FA for all standard, remote access.<br />
3. Combining 2FA with OTP for all logins.</p>
<p>I believe that Two-Factor-Authentication is not fool-proof though, but it can definitely make a pain in the ass for a guy listening on your wire to gain access.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: web user</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-100435</link>
		<dc:creator><![CDATA[web user]]></dc:creator>
		<pubDate>Sun, 11 Oct 2009 08:08:41 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-100435</guid>
		<description><![CDATA[I just read about 8 comments of absolute drivel. I hereby declare half of you (at least) to be crap headed. If you were in binary form (a file) I would rm -rf every trace of you.

Respectfully sincere,
Web User]]></description>
		<content:encoded><![CDATA[<p>I just read about 8 comments of absolute drivel. I hereby declare half of you (at least) to be crap headed. If you were in binary form (a file) I would rm -rf every trace of you.</p>
<p>Respectfully sincere,<br />
Web User</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Andrusko</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-83534</link>
		<dc:creator><![CDATA[Aaron Andrusko]]></dc:creator>
		<pubDate>Thu, 30 Jul 2009 04:26:51 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-83534</guid>
		<description><![CDATA[Also, the laser map key capture feels a bit off because:

A: if it&#039;s a laptop (where the screen is bolted on to the keyboard) it might be more simple to get a logger onto the machine via it&#039;s weak wireless transfers.

B: who is using a laptop outside doing anything worth capture?

C: if someone is using a laptop outside while doing anything of sensitivity, and he or she is behind glass, how does that attenuate the signal&#039;s strength? Window treatments? Polarization? At what point would proximity be hindered to a point of futility?

D: the carrier laser would have to be in the non visible spectra to convey the data without detection of the target. That entails using a camera instead of a simple sensor to see the IR scatter from the laser on the &quot;laptop&quot;s screen or some area for alignment, greatly complicating things as the sample rate of the ccd would have to be very high, and thats contra indicative of using the on-board sound as an ADC. Sure, you could build some sort of alignment mechanics to compensate for a simple 3d index of the screen, with a reduction in return power over the angle of observation, but by then, the camera implementation would be cheaper. I would rather socially engineer my way into the cookie and boogie. Still, a nice paper though!]]></description>
		<content:encoded><![CDATA[<p>Also, the laser map key capture feels a bit off because:</p>
<p>A: if it&#8217;s a laptop (where the screen is bolted on to the keyboard) it might be more simple to get a logger onto the machine via it&#8217;s weak wireless transfers.</p>
<p>B: who is using a laptop outside doing anything worth capture?</p>
<p>C: if someone is using a laptop outside while doing anything of sensitivity, and he or she is behind glass, how does that attenuate the signal&#8217;s strength? Window treatments? Polarization? At what point would proximity be hindered to a point of futility?</p>
<p>D: the carrier laser would have to be in the non visible spectra to convey the data without detection of the target. That entails using a camera instead of a simple sensor to see the IR scatter from the laser on the &#8220;laptop&#8221;s screen or some area for alignment, greatly complicating things as the sample rate of the ccd would have to be very high, and thats contra indicative of using the on-board sound as an ADC. Sure, you could build some sort of alignment mechanics to compensate for a simple 3d index of the screen, with a reduction in return power over the angle of observation, but by then, the camera implementation would be cheaper. I would rather socially engineer my way into the cookie and boogie. Still, a nice paper though!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Andrusko</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-83533</link>
		<dc:creator><![CDATA[Aaron Andrusko]]></dc:creator>
		<pubDate>Thu, 30 Jul 2009 04:13:01 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-83533</guid>
		<description><![CDATA[The key capture window is predicated on using a PS2 keyboard. Try again.]]></description>
		<content:encoded><![CDATA[<p>The key capture window is predicated on using a PS2 keyboard. Try again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: smyd</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-83519</link>
		<dc:creator><![CDATA[smyd]]></dc:creator>
		<pubDate>Wed, 29 Jul 2009 23:45:25 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-83519</guid>
		<description><![CDATA[pffft it is just phishing. Move along.]]></description>
		<content:encoded><![CDATA[<p>pffft it is just phishing. Move along.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IceBrain</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-65550</link>
		<dc:creator><![CDATA[IceBrain]]></dc:creator>
		<pubDate>Sat, 07 Mar 2009 13:03:14 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-65550</guid>
		<description><![CDATA[a.b.z.: You&#039;re right, I didn&#039;t read the part where they &quot;redirect&quot; the user to the real webserver. AFAIK most phishing pages don&#039;t do that.

Is there any tips on how to avoid this? If we type the url by hand using &quot;https&quot; it should be safe, no?
But my bank redirects me to http to login :facepalm:]]></description>
		<content:encoded><![CDATA[<p>a.b.z.: You&#8217;re right, I didn&#8217;t read the part where they &#8220;redirect&#8221; the user to the real webserver. AFAIK most phishing pages don&#8217;t do that.</p>
<p>Is there any tips on how to avoid this? If we type the url by hand using &#8220;https&#8221; it should be safe, no?<br />
But my bank redirects me to http to login :facepalm:</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A.B.Z</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-65508</link>
		<dc:creator><![CDATA[A.B.Z]]></dc:creator>
		<pubDate>Sat, 07 Mar 2009 02:07:43 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-65508</guid>
		<description><![CDATA[icebrain you should be called nobrain. Ive tested this on firefox and even if you type in the wrong pssword it wont log you in.]]></description>
		<content:encoded><![CDATA[<p>icebrain you should be called nobrain. Ive tested this on firefox and even if you type in the wrong pssword it wont log you in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DarkFader</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-64450</link>
		<dc:creator><![CDATA[DarkFader]]></dc:creator>
		<pubDate>Thu, 26 Feb 2009 20:39:34 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-64450</guid>
		<description><![CDATA[This calls for some IDS to be installed. Anyone know some good one for OS X with not too much overhead and in a nice .dmg/.app package?]]></description>
		<content:encoded><![CDATA[<p>This calls for some IDS to be installed. Anyone know some good one for OS X with not too much overhead and in a nice .dmg/.app package?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IceBrain</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-64277</link>
		<dc:creator><![CDATA[IceBrain]]></dc:creator>
		<pubDate>Wed, 25 Feb 2009 15:14:53 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-64277</guid>
		<description><![CDATA[Hey, this doesn&#039;t hijack https! Hijacking would mean tack over a established connection. This redirects the user &quot;before&quot; a ssl connection is made, to a similar site. If you&#039;re already loggen in to the bank, they can&#039;t hijack you, the connection is encrypted.

And there&#039;s a simple way to tell if you&#039;re on the right website before logging in: Just try to login with false data first. The fake website won&#039;t know it&#039;s false and will let you &quot;login&quot;, but the real website will give you &quot;wrong password&quot;.]]></description>
		<content:encoded><![CDATA[<p>Hey, this doesn&#8217;t hijack https! Hijacking would mean tack over a established connection. This redirects the user &#8220;before&#8221; a ssl connection is made, to a similar site. If you&#8217;re already loggen in to the bank, they can&#8217;t hijack you, the connection is encrypted.</p>
<p>And there&#8217;s a simple way to tell if you&#8217;re on the right website before logging in: Just try to login with false data first. The fake website won&#8217;t know it&#8217;s false and will let you &#8220;login&#8221;, but the real website will give you &#8220;wrong password&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ex-parrot</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-64269</link>
		<dc:creator><![CDATA[ex-parrot]]></dc:creator>
		<pubDate>Wed, 25 Feb 2009 11:59:34 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-64269</guid>
		<description><![CDATA[atrain: even for TLD&#039;s such as .cn, they have a filter in place for blocking fraudulent characters.

check the list of links to policies I linked :)]]></description>
		<content:encoded><![CDATA[<p>atrain: even for TLD&#8217;s such as .cn, they have a filter in place for blocking fraudulent characters.</p>
<p>check the list of links to policies I linked :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: supershwa</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-64212</link>
		<dc:creator><![CDATA[supershwa]]></dc:creator>
		<pubDate>Tue, 24 Feb 2009 23:10:01 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-64212</guid>
		<description><![CDATA[heh crap -- i read this article after completing a payment card industy self-assesment questionnaire for a client&#039;s merchant account.  

i&#039;ll pretend i never saw this.]]></description>
		<content:encoded><![CDATA[<p>heh crap &#8212; i read this article after completing a payment card industy self-assesment questionnaire for a client&#8217;s merchant account.  </p>
<p>i&#8217;ll pretend i never saw this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ejonesss</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-64190</link>
		<dc:creator><![CDATA[ejonesss]]></dc:creator>
		<pubDate>Tue, 24 Feb 2009 18:24:51 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-64190</guid>
		<description><![CDATA[that is an extremely dangerous program.

for those who care about the security of their online transactions needs to be careful]]></description>
		<content:encoded><![CDATA[<p>that is an extremely dangerous program.</p>
<p>for those who care about the security of their online transactions needs to be careful</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steaky</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-64179</link>
		<dc:creator><![CDATA[steaky]]></dc:creator>
		<pubDate>Tue, 24 Feb 2009 16:29:40 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-64179</guid>
		<description><![CDATA[question:

As opposed to just bank, ISP and user PC, couldnt this be done on a dns server or someones router?
or, as he said, on a Tor node. 
it would seem that the people that could get burned with this use the tor network and so, stereotypically dont want ppl seeing what they are doing.]]></description>
		<content:encoded><![CDATA[<p>question:</p>
<p>As opposed to just bank, ISP and user PC, couldnt this be done on a dns server or someones router?<br />
or, as he said, on a Tor node.<br />
it would seem that the people that could get burned with this use the tor network and so, stereotypically dont want ppl seeing what they are doing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: atrain</title>
		<link>http://hackaday.com/2009/02/23/sslstrip-hijacking-ssl-in-network/comment-page-1/#comment-64176</link>
		<dc:creator><![CDATA[atrain]]></dc:creator>
		<pubDate>Tue, 24 Feb 2009 14:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=8719#comment-64176</guid>
		<description><![CDATA[ex-parrot:
So you just use an international tld. That&#039;s exactly what he does in his his lecture, uses a .cn site. You get you own cert for it, etc.

Even that isn&#039;t really necessary since 99% of people wouldn&#039;t be able to notice the difference between http and https.]]></description>
		<content:encoded><![CDATA[<p>ex-parrot:<br />
So you just use an international tld. That&#8217;s exactly what he does in his his lecture, uses a .cn site. You get you own cert for it, etc.</p>
<p>Even that isn&#8217;t really necessary since 99% of people wouldn&#8217;t be able to notice the difference between http and https.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

