Timeline for Is it possible to detect SSL private key changes?
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 13, 2017 at 12:48 | history | edited | CommunityBot |
replaced http://crypto.stackexchange.com/ with https://crypto.stackexchange.com/
|
|
Oct 8, 2013 at 11:34 | comment | added | LateralFractal | Ultimately we all reasonably assume that this class of risk is rare, which it is; so just focus on what you can detect - public key changes. | |
Oct 8, 2013 at 7:53 | comment | added | that guy from over there | "This is an esoteric issue ... " yes, indeed. my questions is somehwat inspired by detector.io and i',m still trying to figure out if is is of any relevance to detect key-changes. | |
Oct 8, 2013 at 7:34 | comment | added | LateralFractal |
In practice the mapping of private to public RSA keys is N:1 but each private key of set N is equally effective at decrypting the message, so again the issue would be for apps that are unaware of this N:1 relationship in the few scenarios where it might matter.
|
|
Oct 8, 2013 at 7:31 | comment | added | LateralFractal | @thatguyfromoverthere The question whether private key changes can be detected. If the new private key differs mathematically from the old key, the public key will be a different and observable change. If the new private key is a certain mathematical variation of the previous private key, it will resolve to the same public key and be undetectable in any public certificate. This an esoteric issue that only matters for applications that store or compare private keys directly and assume that private keys map 1:1 with public keys. Normal consumers of SSL needn't worry about this. | |
Oct 8, 2013 at 7:08 | comment | added | that guy from over there | which of my 2 questions do you answer with no? | |
Oct 6, 2013 at 22:31 | history | answered | LateralFractal | CC BY-SA 3.0 |