Notes about issue randomness_in_berkeley_db_files in buster
| Identifier: | randomness_in_berkeley_db_files |
|---|---|
| Suites: | unstable / trixie / bookworm / bullseye / buster / experimental |
| 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. |
|
Packages in 'buster' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
|
|
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). |
|
A package name displayed with a bold
font is an indication that this package has a note. Visited
packages are linked in green, those which have not been visited are
linked in blue.
A # sign after the name of a package
indicates that a bug is filed against it. Likewise, a
+ sign indicates there is a
patch available, a P means a
pending bug while # indicates a
closed bug. In cases of several bugs, the symbol is repeated.