Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I can't really say I understand the details. But it looks like RSA does not deserve any trust anymore. When this Snowden guy managed to get all that stuff from NSA, how can we know other malicious people don't have access to the backdoors?
We have been using RSA keys for ssh login and I think for HTTPS for some servers. Is there anything we can or should do?
But it looks like RSA does not deserve any trust anymore.
...
We have been using RSA keys for ssh login and I think for HTTPS for some servers. Is there anything we can or should do?
RSA may refer to:
...
RSA (algorithm), an algorithm for public-key encryption
...
RSA (security firm), a U.S. network security provider, a division of EMC Corporation
RSA the security firm may not deserve trust. RSA the algorithm used for ssh keys and HTTPS is fine (although HTTPS itself has some problems).
They weakened encryption by using the Dual EC PRNG, which is known to be backdoored by the NSA, and is a NIST standard.
Quote:
An algorithm called Dual Elliptic Curve, developed inside the agency, was on the road to approval by the National Institutes of Standards and Technology as one of four acceptable methods for generating random numbers. NIST's blessing is required for many products sold to the government and often sets a broader de facto standard.
RSA adopted the algorithm even before NIST approved it. The NSA then cited the early use of Dual Elliptic Curve inside the government to argue successfully for NIST approval, according to an official familiar with the proceedings.
RSA's contract made Dual Elliptic Curve the default option for producing random numbers in the RSA toolkit. No alarms were raised, former employees said, because the deal was handled by business leaders rather than pure technologists.
"The labs group had played a very intricate role at BSafe, and they were basically gone," said labs veteran Michael Wenocur, who left in 1999.
Within a year, major questions were raised about Dual Elliptic Curve. Cryptography authority Bruce Schneier wrote that the weaknesses in the formula "can only be described as a back door."
Here is something useful, a proof of concept for the Dual EC PRNG backdoor: http://blog.0xbadc0de.be/archives/155
It leaks its internal state in 32 bytes of output. It was purposefully introduced as an NIST and FIPS standard by the NSA, and they paid off RSA to use it too.
Note that only the NSA can exploit the weakness that they introduced.
I'm looking forward to seeing more NSA-recommended crypto standards being taken apart to see what is underneath. Not that I can't imagine what is there.
Last edited by metaschima; 01-01-2014 at 01:53 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.