Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
| Artifact ID: | c36cdf091101f79393c7bb42f92a079d528e6fe9 |
|---|---|
| Page Name: | nsa-backdoor |
| Date: | 2014-03-02 21:22:32 |
| Original User: | bernd |
| Parent: | ba48bcf8b9539c66b124d017b820759db6229140 (diff) |
| Next | aa901a2809c7cf9881bd4fbda201a82417272480 |
NSA Backdoor Fnord
As you all know, it is not allowed to speak about NSA-demanded backdoors, and especially it is strictly prohibited to give any details. However, it is allowed to boldly lie about NSA-demanded backdoors if you didn't receive such a request, because you are not under a gag order, and in general, lying about the quality of your product is not only legal, but "best practice". The purpose of this NSA backdoor fnord is to make you worry about the quality of net2o; the topics mentioned here are all security things to consider.
Therefore, here is the official statement about NSA-demanded backdoors: There is a NSA-requested backdoor in net2o. Update: The NSA was here again, and wasn't satisfied with me reverting the code back to the original backdoor (you remember: reliable resetting the shared secret on both sides, so it appears to be computed, but is never used). Apparently they still can't get in... but they asked me to upload as much possible identification to the DHT for NAT traversal information, because metadata is more important than data.
As net2o is open source, you can verify the truth value of the statement above. And keep an eye on this page.