Timeline for Is encrypting data with a private key dangerous?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 23, 2017 at 10:51 | history | tweeted | twitter.com/StackSecurity/status/911543418773540865 | ||
| Sep 19, 2012 at 0:17 | answer | added | Thomas Pornin | timeline score: 10 | |
| Feb 18, 2012 at 2:49 | history | migrated | from stackoverflow.com (revisions) | ||
| Feb 18, 2012 at 0:44 | comment | added | Maarten Bodewes | I don't think you can really answer this question without knowing the full details of the algorithm used. It is highly suspect, and I don't see why a signature could not be used. If it is because of message size then I would advice on using eliptic curves (first encryption, then a signature) instead of designing proprietary crypto algorithms/protocols. | |
| Feb 16, 2012 at 20:48 | comment | added | CodesInChaos | When encryption the actual data (as opposed to a correctly padded hash) with the private key, I don't think it even achieves that goal. | |
| Feb 16, 2012 at 20:45 | answer | added | Steven Parkes | timeline score: 1 | |
| Feb 16, 2012 at 20:41 | comment | added | DwayneAllen | I think you are on the correct train of thought. The only time I've heard of encrypting with a private key is so that whoever receives the data can know without a doubt it came from you | |
| Feb 16, 2012 at 20:41 | answer | added | CodesInChaos | timeline score: 7 | |
| Feb 16, 2012 at 20:38 | history | asked | Dan Midwood | CC BY-SA 3.0 |