+++ This bug was initially created as a clone of Bug #368281 +++ Description of problem: When attempting to create a db file outside of /var/db, makedb gives an error about being unable to determine the context for the file. It works fine if the file is in /var/db. I believe this is related to the fix for https://bugzilla.redhat.com/show_bug.cgi?id=136522 Version-Release number of selected component (if applicable): nss_db-2.2-35.1 How reproducible: Every time Steps to Reproduce: 1. mkdir /tmp/foo 2. Edit /var/db/Makefile so that the VAR_DB line points to /tmp/foo 3. cd /var/db ; make Actual results: [root@svartalfheim db]# make passwd... makedb: cannot determine file context for `/tmp/foo/passwd.db' make: *** [/tmp/foo/passwd.db] Error 1 Expected results: passwd... done. group... done. protocols... done. rpc... done. services... done. shadow... done. Additional info: -- Additional comment from nalin on 2007-11-06 11:43 EST -- Should be a relatively simple change to the patch which adds labeling of files. Test cases will entail calling makedb directly using various destination filenames, in permissive and enforcing mode, and making sure that it exits with an error message only if the file is supposed to have a specific label, passing that label to setfscreatecon() generated an error, and we're in enforcing mode.
Based on the date this bug was created, it appears to have been reported during the development of Fedora 8. In order to refocus our efforts as a project we are changing the version of this bug to '8'. If this bug still exists in rawhide, please change the version back to rawhide. (If you're unable to change the bug's version, add a comment to the bug and someone will change it for you.) Thanks for your help and we apologize for the interruption. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
Hmm, we fixed this with FEDORA-2008-2285, but I must've forgotten there was a specific bug for it.