Re:Node.js used to mirror DOM across browsers
by tlrobinson on Tuesday August 31, 2010 @10:16AM
(#1649430)
You understand this works by proxying webpages, right? The URL bar is going to show the URL of the proxy, not my bank.
If you consider this to be dangerous that's a flaw in every web browser ever, not this piece of software. This kind of thing was possible 10 years ago too.
Re:Node.js used to mirror DOM across browsers
by Kliment on Tuesday August 31, 2010 @10:54AM
(#1649554)
That's how every phishing plot works, no? And still they get data. This makes it a step smoother.
Re:Node.js used to mirror DOM across browsers
by jorangreef on Tuesday August 31, 2010 @03:04AM
(#1648689)
Re: "sounds plenty dangerous to me"
Often, it's the "sounds plenty dangerous" innovations (fire, automobile, chainsaw, theory of relativity), that provide the most utility.
Re:Node.js used to mirror DOM across browsers
by Kliment on Tuesday August 31, 2010 @06:01AM
(#1648909)
Oh, certainly. The fact that it can be used for evil makes it no less impressive and useful for other purposes. But thinking of this attack makes me wonder if our browser security models are getting outdated. With things like this possible, and so much valuable data being web-based these days, is there any way of using cool things like that yet avoiding the major risks?
Re:Node.js used to mirror DOM across browsers
by InclinedPlane on Tuesday August 31, 2010 @03:16AM
(#1648709)
Flight, gunpowder, surgery, sailing, heliocentrism.
A similar attack would be to override the back button. You know those sites where the back button takes you to a redirect that takes you to the same page? Take one of those, but on the redirect page save the referring URL. Then when the user hits back, have the redirect page start the session sharing and redirect to the referrer. Sounds plenty dangerous to me.