4 ms·
From the "Conclusions" section: > Change of sharing paradigm that introduced this vulnerability happened after the first releases. This may be the result of NS
by atmosx 12y ago
From the "Conclusions" section:
> Change of sharing paradigm that introduced this vulnerability happened after the first releases. This may be the result of NSL (National Security Letters, from US Government to businesses to pressure them in giving out the keys or introducing vulnerabilities to compromise previously secure systems) that could have been received by BitTorrent Inc and/or developers.
IF that's true, then it's extremely alarming. I wouldn't use their software to share sensitive files.
- JohnTHaller 12y agoThe government has a window into basically all the file sharing services.
- higherpurpose 12y agoI'm no security expert, but when I saw they did that whole "easier sharing" thing over e-mail that raised a major red flag for me. It seemed quite obvious that many of the previously secure systems would now be broken by that insecure e-mail sharing system.
- benguild 12y agoI disagree... My guess is that if you choose to enable features like that you're most likely opening a door, but if you don't it won't compromise anything. At least, that's how any competent developer would code it.
- sehugg 12y agoI think there's a bit of FUD and jumping to conclusions; the hashes shared are not permanent keys but one-time secrets (i.e. invite codes) according to this link (although we probably will want some confirmation): http://forum.bittorrent.com/topic/31588-wont-use-getsynccom-link-for-sharing/ http://forum.bittorrent.com/topic/31588-wont-use-getsynccom-...