Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revisionBoth sides next revision
public:papers:acsac2017 [2017-12-04 19:54] – [Q&A section] xnemec1public:papers:acsac2017 [2017-12-04 20:14] – [Q&A section] xnemec1
Line 42: Line 42:
  
 ==Q: Does it mean the biased RSA key generation methods are broken?== ==Q: Does it mean the biased RSA key generation methods are broken?==
-A: No, in general, the bias is not enough for key factorization. However, we did break the Infineon implementation in our recent paper [[https://crocs.fi.muni.cz/public/papers/rsa_ccs17 | The Return of Coppersmith's Attack (ROCA)]]+A: No, in general, the bias is not enough for key factorization. However, we did break the Infineon implementation in our recent paper [[https://crocs.fi.muni.cz/public/papers/rsa_ccs17 | The Return of Coppersmith's Attack (ROCA)]]
 + 
 +==Q: What parts of an RSA public key are biased?== 
 +A: We extract an 8-bit feature vector from a public modulus N: we use the remainder of division of the modulus N modulo 3, remainder modulo 4, and the 2nd to 7th most significant bits of the modulus. 
 + 
 +{{:public:papers:acsac2017_explain_mask_openssl.png?400|}} 
 + 
 +==Q: What was the motivation for the measurement?== 
 +A: We developed a method for probabilistic classification of keys based on their source in our paper [[https://crocs.fi.muni.cz/public/papers/usenix2016 | The Million-Key Question]] at [[https://www.usenix.org/node/197198 | USENIX Security 2016]]. However, we were missing an accurate estimation of library popularity and could not find any papers accomplishing that. We also needed to measure the impacts of [[https://crocs.fi.muni.cz/public/papers/rsa_ccs17 | ROCA vulnerability]] and this is a general method for such measurements.
  
 ==Q: What libraries did you analyze? Can you tell all libraries apart?== ==Q: What libraries did you analyze? Can you tell all libraries apart?==
Line 50: Line 58:
  
 ==Q: I want to know the popularity of library X, why wasn't it included? == ==Q: I want to know the popularity of library X, why wasn't it included? ==
-A: To suggest other sources that we can add to our analysis, please get in touch with us. If you can also provide keys generated by hardware, open-source and proprietary libraries, we will add them to the [[https://drive.google.com/drive/u/3/folders/0B0PpUrsKytcyMllkUHJ0RkZkdzA | Collection of RSA keys from reference libraries]]+A: To suggest other sources that we can add to our analysis, please get in touch with us. If you can also provide keys generated by hardware, open-source and proprietary libraries, we will add them to the [[https://drive.google.com/drive/u/3/folders/0B0PpUrsKytcyMllkUHJ0RkZkdzA | Collection of RSA keys from reference libraries]]
 + 
 +==Q: Why can't you associate a key with its source with certainty?== 
 +A: The features extracted from the keys are not unique. Different (groups of) libraries can produce keys with the same features. Only the distribution of the features differs, as illustrated here: 
 + 
  
 +==Q: What is the accuracy of the measurement?==
 +A: We performed simulations to determine the accuracy. The expected error of the measurement was within 1 percentage point of the estimation (e.g., OpenSSL being estimated at 70% means that we expect it to be between 69% and 71%). The error might be larger in some cases, however the ground truth is not always known. Our estimation of ROCA vulnerable keys in a PGP dataset was at 0.10%, that is within 0.02 percentage points from the correct proportion found by a much more reliable method specific to the ROCA keys.