Timeline for SHA256: Padding a 512 bits length message
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 16, 2015 at 9:55 | history | edited | Richie Frame | CC BY-SA 3.0 |
more bits/bytes
|
| Oct 15, 2015 at 15:36 | comment | added | Maarten Bodewes♦ | @Zyend OK, glad you got it solved. It was bound to be an implementation mistake I guess. | |
| Oct 15, 2015 at 15:35 | history | edited | Maarten Bodewes♦ | CC BY-SA 3.0 |
added 11 characters in body
|
| Oct 15, 2015 at 9:38 | vote | accept | Zyend | ||
| Oct 15, 2015 at 9:36 | comment | added | Zyend | Sorry, I have edited my post above and the message is 64 bytes / 512 bits length. In my implementation, I made a mistake when copying the bytes of the 64 bits message length at the end of the block. | |
| Oct 15, 2015 at 9:03 | comment | added | Maarten Bodewes♦ | His message is 32 characters. That doesn't tell the byte size of course, so your answer would be valid for UTF-16 I suppose (64 * 8 = 512 = 200h). And you confuse bits and bytes. | |
| Oct 14, 2015 at 21:48 | history | answered | Richie Frame | CC BY-SA 3.0 |