4 ms·

The tool this seems to be based on is here: http://www.fi.muni.cz/~xsekan/ http://www.fi.muni.cz/~xsekan/

by ryan-c 10y ago

peterwwillis 10y ago
"Q: So what did you do? A: Figured out that RSA public key is leaking info about a library which created it. So we can tell which library you used for your key - based on public key only. Q: Is single key enough to identify source library? A: Sometimes yes, but mostly no. If you have 5 keys from the same source, it will be quite accurate. Just press Classify button above. Q: Can I mutually distinguish all libraries? A: Not always. Source libraries introducing exactly same bias to the value of generated public moduli will be undistinguishable. Q: Can I identify also the version of used library? A: Sometimes. The new version of a library that did not change source code of key generation method will not be distinguishable from the older one. E.g., OpenSSL 1.0.2f is not distinguishable from OpenSSL 1.0.2g, but OpenSSL 1.0.2g is distinguishable from OpenSSL 2.0.12 FIPS. Q: Have you tested all libraries of the world? A: No. We test a lot of them, but not all. We also did not test all possible version of given library. We are also missing hardware sources like SSL accelerators (contact us please, if you have one and like to contribute). Q: How quickly will be the information leakage vulnerability you found fixed? A: Probably not soon. The fix would require changing code of key generation method for the most libraries. And developers don't like to mess with that part of crypto too often. Even if fixed in the new version, lot of old legacy libraries will use for a long time. Q: So how can I protect my key(s)? A: If you need just one key, it is easy - just generate 5 keys instead of one, let all to be classified by our tool (http://crcs.cz/rsapp/ http://crcs.cz/rsapp/) and then keep the one which is classified with the least accuracy. If you need more keys to keep, it is slightly more tricky, but still can be done (with more keys generated and discarded). Q: Are data you gathered and used publicly available? A: Definitely! Download everything in datasets section and try own analysis. Please don't forget to cite us." Apologies for the really long post, but this really should have been the entire article.

The tool this seems to be based on is here: http://www.fi.muni.cz/~xsekan/ http://www.fi.muni.cz/~xsekan/

by ryan-c 10y ago

The tool this seems to be based on is here: http://www.fi.muni.cz/~xsekan/ http://www.fi.muni.cz/~xsekan/

"Q: So what did you do? A: Figured out that RSA public key is leaking info about a library which created it. So we can tell which library you used for your key - based on public key only. Q: Is single key enough to identify source library? A: Sometimes yes, but mostly no. If you have 5 keys from the same source, it will be quite accurate. Just press Classify button above. Q: Can I mutually distinguish all libraries? A: Not always. Source libraries introducing exactly same bias to the value of generated public moduli will be undistinguishable. Q: Can I identify also the version of used library? A: Sometimes. The new version of a library that did not change source code of key generation method will not be distinguishable from the older one. E.g., OpenSSL 1.0.2f is not distinguishable from OpenSSL 1.0.2g, but OpenSSL 1.0.2g is distinguishable from OpenSSL 2.0.12 FIPS. Q: Have you tested all libraries of the world? A: No. We test a lot of them, but not all. We also did not test all possible version of given library. We are also missing hardware sources like SSL accelerators (contact us please, if you have one and like to contribute). Q: How quickly will be the information leakage vulnerability you found fixed? A: Probably not soon. The fix would require changing code of key generation method for the most libraries. And developers don't like to mess with that part of crypto too often. Even if fixed in the new version, lot of old legacy libraries will use for a long time. Q: So how can I protect my key(s)? A: If you need just one key, it is easy - just generate 5 keys instead of one, let all to be classified by our tool (http://crcs.cz/rsapp/ http://crcs.cz/rsapp/) and then keep the one which is classified with the least accuracy. If you need more keys to keep, it is slightly more tricky, but still can be done (with more keys generated and discarded). Q: Are data you gathered and used publicly available? A: Definitely! Download everything in datasets section and try own analysis. Please don't forget to cite us." Apologies for the really long post, but this really should have been the entire article.