On ven., 2010-07-02 at 15:41 +0100, David Woodhouse wrote: > n Fri, 2010-07-02 at 16:27 +0200, Yves-Alexis Perez wrote: > > David: would it make sense to try fixing permissions in case they're > > considered wrong by NSS and thus it won't open the db? > > I would be _very_ reluctant to do that kind of thing. I don't want to > mess with permissions that someone else has set on the directory. > > Although if the problem was that the directory was _too_ permissive, and > we're talking about tightening it up, then perhaps I could be persuaded.
Yes, I was implying this. My understanding was that NSS refused to load the database because of the permissions (like you said on irc) and it seemed logical that it was because permissions were too open, so in that case it made sense to tighten them. But it seems it was not the problem. > > It would be interesting to know what the original problem was -- and > more to the point, how it got that way. Agreed. On ven., 2010-07-02 at 18:14 +0200, José Sánchez Moreno wrote: > I actually didn't delete the directory. I've just move. The output that > you ask me is. > > 2883631 4 drwx------ 3 jose jose 4096 ene 20 08:58 pki/ > 2888708 4 drwx------ 2 jose jose 4096 jul 2 16:02 > pki/nssdb > 2889579 16 -rw------- 1 jose jose 4669440 may 19 15:01 > pki/nssdb/cert9.db > 2889581 4 -rw------- 1 jose jose 441 ene 20 08:58 > pki/nssdb/pkcs11.txt > 2889580 12 -rw------- 1 jose jose 11264 ene 20 08:58 > pki/nssdb/key4.db > Looks like they are correct indeed, so we're back to speculations. I'll try to rebuild an eds packages so you can test with the “old” pki folder and see what nss replies. Cheers, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
