Timeline for Signature Generation Time vs Verification Time
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 27, 2020 at 22:23 | comment | added | Maarten Bodewes♦ | Yeah, I guess when you start looking at one producer many consumers then you'll quickly find more. Signed configuration files is a similar one (although often the same cert is used for that). I also thought up one where multiple signatures may be generated but almost never consumed: audit logging. | |
| Aug 27, 2020 at 21:11 | comment | added | fgrieu♦ | Another common use case where we verify a signature many times, making RSA preferable, is signature of executable code. | |
| Aug 27, 2020 at 21:04 | history | edited | Maarten Bodewes♦ | CC BY-SA 4.0 | removed some spurious text from end-of-day answer (even later at the same day, oh boy) |
| Aug 27, 2020 at 20:59 | history | edited | Maarten Bodewes♦ | CC BY-SA 4.0 | added 24 characters in body |
| Aug 27, 2020 at 15:56 | comment | added | Maarten Bodewes♦ | Alright. You'd still have two signatures to verify in that case of course: the one under the leaf cert and the one to perform the actual authentication (although the latter requires signature generation as well, so it won't imbalance the signature generation & verification). | |
| Aug 27, 2020 at 15:04 | comment | added | poncho♦ | "although you could in principle cache signature verification results, I suppose"; actually, caching intermediate certificates once you have verified them is standard practice... | |
| Aug 27, 2020 at 14:45 | history | answered | Maarten Bodewes♦ | CC BY-SA 4.0 |