[notes] 01/01: Expand note for randomness_in_berkeley_db_files.

[Chris Lamb]

This is an automated email from the git hooks/post-receive script.

lamby pushed a commit to branch master
in repository notes.

commit ca9a3ce78e05ae30d4c5bdac326172527d8e5a90
Author: Chris Lamb <lamby at debian.org>
Date:   Thu Feb 15 16:55:59 2018 +0000

    Expand note for randomness_in_berkeley_db_files.
---
 issues.yml | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/issues.yml b/issues.yml
index ada095e..f58a834 100644
--- a/issues.yml
+++ b/issues.yml
@@ -1786,5 +1786,11 @@ randomness_in_berkeley_db_files:
     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/5.3.28-13.1/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 (!).
+    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.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/notes.git