News for hackers. Stuff that matters.
Re:The most dangerous code in the world by austinpilot on Wednesday October 24, 2012 @07:42PM (#4695593)
One of the authors here... The paper is accompanied by a FAQ, which among other things explains the impact on specific software:

https://docs.google.com/document/pub?id=1roBIeSJsYq3Ntpf6N0P...

For example, broken SSL in Amazon FPS allows a MITM attacker to forge instant payment notifications and defraud merchants who use vulnerable SDKs. This is a real vulnerability, acknowledged by Amazon.

Re:The most dangerous code in the world by moxie on Wednesday October 24, 2012 @07:59PM (#4695645)
Oh thanks, I think that FAQ is exactly what I was looking for. I realize we might not be your target audience, but it seems like it'd be worth including those impact analysis statements in the paper itself, since they're short and do really help to clarify the situation.

I'll have to take a second look at the instant payment notification forgery. Last I used FPS, I remember the transaction notifications being signed. Maybe "instant payments" are a new thing.

Re:The most dangerous code in the world by scott_s on Wednesday October 24, 2012 @07:56PM (#4695636)
Can you address his specific point about TextSecure?
Re:The most dangerous code in the world by zx2c4 on Wednesday October 24, 2012 @08:55PM (#4695833)
please would ya?