Repository navigation
Commit b737e9d
committed
bug fix: XDRBG - set initially seeded flag after seed operation was successful
Only set the initially seeded flag after all seeding steps were successful.
A caller could provide a too long personalization string which would trigger an
error where yet the XDRBG thinks it is initially seeded.
This is a bug fix. Yet, the caller receives an error during initially seeding
in this case and should process it properly. If he tries to reseed with
proper data, the resulting state of the XDRBG is cryptographically secure
but it may not be the state defined after an initial seeding operation.
Thus, it is considered a bug, but no security issue.
Reported-by: Conner Webber
Signed-off-by: Stephan Mueller <[email protected]>1 parent 4e46730 commit b737e9d
2 files changed
Lines changed: 6 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
47 | 47 | | |
48 | 48 | | |
49 | 49 | | |
50 | | - | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
51 | 53 | | |
52 | 54 | | |
53 | 55 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
259 | 259 | | |
260 | 260 | | |
261 | 261 | | |
262 | | - | |
263 | | - | |
264 | 262 | | |
265 | 263 | | |
266 | 264 | | |
| |||
273 | 271 | | |
274 | 272 | | |
275 | 273 | | |
| 274 | + | |
| 275 | + | |
| 276 | + | |
276 | 277 | | |
277 | 278 | | |
278 | 279 | | |
| |||
0 commit comments