Thanks to all that replied, interesting stuff. Looks like a web tool I may use in the future.
On a related note I have been putting together a p2p web app, (with Flash as opposed to JS) using a protocol known as RTMFP. >From the Adobe literature I assumed the channel was well encrypted >(http://www.ietf.org/proceedings/10mar/slides/tsvarea-1.pdf) but if you guys >know otherwise…Facebook uses the same protocol for some of its p2p file >transfers. So although I can promote it as secure, I’m not privy to the Adobe source code. I wonder if any of you had the opportunity to analyze it to any depth? Mario From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: April-01-12 4:29 AM To: [email protected]; [email protected] Subject: Re: [cryptography] crypto.cat Again - SSL flaws, bad server, etc... Maybe a buggy browser. Can you imagine a bug allowing JS injection in any tab? Post a bit.ly link and wait for keys... Bugs like that have existed before. 2012-04-01 02:54 skrev James A. Donald: On 2012-04-01 7:51 AM, [email protected] wrote: > It's running in a browser using JS... To attack JS, the attacker needs to induce the victim to open the attackers web page at the same time as the attacked web page, and successfully apply a cross site scripting attack. The simplicity of the crypto.cat web page is apt to make cross site scripting attacks difficult. _______________________________________________ cryptography mailing list [email protected] http://lists.randombit.net/mailman/listinfo/cryptography
_______________________________________________ cryptography mailing list [email protected] http://lists.randombit.net/mailman/listinfo/cryptography
