| Version annotated: |
2.3.4.2-15 |
|
Identified issues:
|
|
Identifier:
|
randomness_in_berkeley_db_files
|
|
Description
|
Creating an empty Berkeley DB file (or ones with the same contents) results
in a different file.
.
This comes from:
https://sources.debian.org/src/db5.3/latest/src/os/os_uid.c/#L20 but
it's unclear where to "set" this only on the creation case - we definitely
want the uid to change if one adds stuff later.
.
Compounding this, the debugging tools *additionally* return random data for
the uid/hash fields (!), so presumably srand is being called when you do a
"db_dump -d a /path/to/my.db" which is obviously broken.
|
|
|
Comments:
|
Randomness in example.db file, probably struct mem
|
| |
|
Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise).
|