Timeline for How is PKCS a syntax to digitally sign, digest, authenticate, or encrypt arbitrary message content
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 7:59 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Oct 6, 2021 at 9:24 | history | edited | Maarten Bodewes♦ | CC BY-SA 4.0 |
added 178 characters in body
|
| Apr 17, 2020 at 22:46 | comment | added | Maarten Bodewes♦ | No, they are not outright wrong. In a sense they are ways of signing, but they are reliant on the signature generation algorithms used. They should be cleared up, I agree. As for a task: create a key pair and X.509 self signed certificate (plenty of tutorials on that) and then sign a message. You have to start somewhere I guess. My first task was to sign a Java Applet using a HSM and key tool. Then I had to recreate the entire protocol to sign the applet. In case you think your first crypto task is hard ;) I was hired in that first month though. | |
| Apr 17, 2020 at 6:14 | comment | added | Finlay Weber | Also what are your thoughts on those phrases from wikipedia and the rfcs i mentioned in the questions..are they just outright wrong? | |
| Apr 17, 2020 at 6:04 | comment | added | Finlay Weber | Thanks for this answer. I now have a better mental model of things. If I were a junior engineer, and you want to give me a task that would help in getting a more hands on feel for CMS...what task would you suggest I do? | |
| Apr 17, 2020 at 6:03 | vote | accept | Finlay Weber | ||
| Apr 16, 2020 at 23:30 | history | edited | Maarten Bodewes♦ | CC BY-SA 4.0 |
edited body
|
| Apr 16, 2020 at 23:23 | history | edited | Maarten Bodewes♦ | CC BY-SA 4.0 |
added 221 characters in body
|
| Apr 16, 2020 at 23:16 | history | answered | Maarten Bodewes♦ | CC BY-SA 4.0 |