On Wed, 14 May 2014 06:30:32 -0700 (PDT)
Matthew Polder <mpth...@gmail.com> wrote:

> > * This env. variable is not exported so that it's seen in your
> > shell but the Git process does not inherit it which causes libnss
> > to use the default value for that path. 
> >
> >   What happens if you do 
> >
> >   $ export SSL_DIR="$HOME/.ssl" 
> >   $ git clone ... 
> >
> >   ? 
> >
> When I do:
> setenv SSL_DIR /home/myusername/.ssl
> and then run git it does successfully incorporate this path:
> * Initializing NSS with certpath: sql:/home/myusername/.ssl
> * NSS error -8018 
> but it's not picking up the certificate info, likely do to
> my .gitconfig not being set correctly.

According to Google [1], the NSS error -8018 means NSS failed to load
your certificate from the indicated file.  Since we know NSS now sees
the correct certpath, the rest is to deal with this -8018 error.

According to Google [2], the error -8018 means "unknown PKCS#11 error",
and Google suggests [3] to

1) Check the permissions on files under that directory (and on that
   directory itself).

2) Enumerate the certs in that directory using

   certutil -d /home/myusername/.ssl -L

So I'd try to carry out those steps using the account you're using to
run Git.  (Note that the message "Initializing NSS with certpath" might
mean that the indicated pathname *will* be used by NSS when it will try
to access anything under it, not that NSS already checked everything is
okay with that path; so I'd say it's quite sensible that you only get
an error whey NSS actually tries to read from the cert storage.)

1. https://www.google.com/search?q="NSS+error+-8018";
3. https://www.google.com/search?q="unknown+PKCS%2311+error";

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to