Timeline for PKCS#12 integrity function
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 19 at 14:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 20 at 13:19 | answer | added | Klubo | timeline score: 0 | |
| Aug 18 at 9:30 | comment | added | Klubo | @dave_thompson_085: my mistake for the wrong location, I should have posted in Stack Overflow. Thanks for the MAC key, I need to understand why my mbedTLS and personal implementations are incorrect. | |
| Aug 18 at 9:25 | history | edited | Klubo | CC BY-SA 4.0 |
edited body
|
| Aug 18 at 2:08 | history | reopened | Maarten Bodewes♦ | ||
| Aug 18 at 1:45 | comment | added | Maarten Bodewes♦ | Ah, wow, that was hiding in plain sight. Commonly they are over the same passphrase right? So that would completely negate the 100k if the 10k can be calculated instead (?). I'm losing track of what happens within P12, I think I had a better grip when I was myself working with it. | |
| Aug 18 at 1:22 | comment | added | dave_thompson_085 | Implementation issues (writing or debugging code) that don't affect or involve the underlying crypto algorithms or attacks aren't considered ontopic here, but: the correct derived MAC key is A760BBE69A30C5286BEDB7FF4EEE04AA6BEC9B91 (and you do have the correct data). @Maarten: the keybag and certbag encryption are PBES2 with PBKDF2/HmacSHA256(32bytes)/10k, but the integrity check (MAC) derivation is indeed SHA1(20bytes)/100k. | |
| Aug 18 at 0:28 | history | closed | Maarten Bodewes♦ | Needs details or clarity | |
| S Aug 17 at 16:51 | review | First questions | |||
| Aug 18 at 0:33 | |||||
| S Aug 17 at 16:51 | history | asked | Klubo | CC BY-SA 4.0 |