Re: Accessing Firefox keystore

2015-01-14 Thread Opa114
> - People > (personal without related private key) --> how did you get this? -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto

Re: Using JSS SSLSocket and and SSLServerSocket TLS 1.1 and 1.2

2015-01-14 Thread deepreel
My bad, I wasn't clear (I think) that I'm talking about server side code, not client, i.e. essentially a Java based web server with the SSL Socket handled by JSS. so at this point all I have is SSLSocket.enableDefaultCipher(SSLSocket.) and socket.enableTLS(true) socket.disableSSLv3(true) t

Re: Accessing Firefox keystore

2015-01-14 Thread Opa114
Am Mittwoch, 14. Januar 2015 20:30:41 UTC+1 schrieb Opa114: > in the secmod.java it checks the Version of NSS: > > private void fetchVersions() { > supported = nssVersionCheck(nssHandle, "3.7"); > } > > But the NSS Version i copied from Mozilla-Folder has verson 3.17.2.0. But > this error me

Re: best practices - python-nss to serialize PEM

2015-01-14 Thread John Dennis
On 01/14/2015 02:59 PM, Robert Daniels wrote: > John, > > Some additional observations. > > If I debug with a breakpoint over the password callback, it's never > called when invoking pkcs12_export, however it is invoked when > calling find_key_by_any_cert. Hmmm ... that seems odd. It's NSS that

Re: best practices - python-nss to serialize PEM

2015-01-14 Thread Robert Daniels
John, Some additional observations. If I debug with a breakpoint over the password callback, it's never called when invoking pkcs12_export, however it is invoked when calling find_key_by_any_cert. I also notice 2 flavors of the callbacks for password, one taking 2 parameters and the other 3,

Re: best practices - python-nss to serialize PEM

2015-01-14 Thread Robert Daniels
On Wednesday, January 14, 2015 at 2:36:45 PM UTC-5, Robert Daniels wrote: > On Wednesday, January 14, 2015 at 11:27:50 AM UTC-5, John Dennis wrote: > > On 01/14/2015 09:58 AM, Robert Daniels wrote: > > > Trying as you suggested today, but ran into some other thing which is > > > puzzling. > > > >

Re: best practices - python-nss to serialize PEM

2015-01-14 Thread Robert Daniels
On Wednesday, January 14, 2015 at 11:27:50 AM UTC-5, John Dennis wrote: > On 01/14/2015 09:58 AM, Robert Daniels wrote: > > Trying as you suggested today, but ran into some other thing which is > > puzzling. > > > > When I call cert = find_cert_from_nickname(nn, pwd) I successfully pull the > >

Re: Accessing Firefox keystore

2015-01-14 Thread Opa114
in the secmod.java it checks the Version of NSS: private void fetchVersions() { supported = nssVersionCheck(nssHandle, "3.7"); } But the NSS Version i copied from Mozilla-Folder has verson 3.17.2.0. But this error message seems to be that there are problems with the version. -- dev-tech-cry

Re: Accessing Firefox keystore

2015-01-14 Thread Opa114
i played a little bit with my JSS-Code. it shows me all Certificates fromm all Tabs in the Firefox Builtin Certificate-Manager. But JSS seems to be very buggy. First i read out 183 Certificates. After i removed one certificate and i run the list certificates again it shows me 190 certificates. T

Re: Using JSS SSLSocket and and SSLServerSocket TLS 1.1 and 1.2

2015-01-14 Thread Christina Fu
jss-4.2.6-35 can be found on koji for various supported fedora platforms. For rhel it's the same version number. Christina On 01/13/2015 09:09 AM, Robert Relyea wrote: Christina, which version of JSS has TLS 1.1 and 1.2 support enabled? Bob On 01/12/2015 02:10 PM, deepr...@gmail.com wrote:

Re: Using JSS SSLSocket and and SSLServerSocket TLS 1.1 and 1.2

2015-01-14 Thread Christina Fu
On 01/13/2015 09:28 AM, Robert Relyea wrote: On 01/13/2015 09:18 AM, Christina Fu wrote: jss-4.2.6-35 can be found on koji for various supported fedora platforms. For rhel it's the same version number. Christina Are there any outside available builds, like windows? We hope to get to it, b

Re: best practices - python-nss to serialize PEM

2015-01-14 Thread John Dennis
On 01/14/2015 09:58 AM, Robert Daniels wrote: > Trying as you suggested today, but ran into some other thing which is > puzzling. > > When I call cert = find_cert_from_nickname(nn, pwd) I successfully pull the > server cert. > I then call find_key_by_any_cert(cert, certpassword) I get an object

Re: Accessing Firefox keystore

2015-01-14 Thread Opa114
i tried it now with JSS and there i could access the Trusted Root CAs and the own certificates. i could remove them, too. now i have to check if i could read the other certificates like Persons, other and root. and i have to check exactly what certificates i get when i call the getCACerts()-fun

Re: best practices - python-nss to serialize PEM

2015-01-14 Thread Robert Daniels
Trying as you suggested today, but ran into some other thing which is puzzling. When I call cert = find_cert_from_nickname(nn, pwd) I successfully pull the server cert. I then call find_key_by_any_cert(cert, certpassword) I get an object back (nss.nss.PrivateKey). So, presumably the PK exists f

Re: Accessing Firefox keystore

2015-01-14 Thread helpcrypto helpcrypto
Hi Matthias As stated in [1] you should use nssModule=trustanchors I have tried: String config = "name = NSS\r\n nssLibraryDirectory = "+ tmpDirName + "\r\n nssSecmodDirectory = " + profile.replace("\\", "/") + "\r\n nssDbMode = readOnly\r\n nssModule = trustanchors\r\n attributes = comp