Re: Ensuring certificate chain when creating certificates in memory without db.

2013-02-10 Thread passfree
On Friday, February 8, 2013 9:08:50 PM UTC, Brian Smith wrote: > pass@googlemail.com > > > I use SSL_ConfigSecureServer with a certificate which was created in > > > memory (no db). The certificate was created with the > > > CERT_CreateCertificate passing the CA's issuer. The same cert was >

Ensuring certificate chain when creating certificates in memory without db.

2013-02-04 Thread passfree
Hi everyone, I use SSL_ConfigSecureServer with a certificate which was created in memory (no db). The certificate was created with the CERT_CreateCertificate passing the CA's issuer. The same cert was also signed with the CA's key. The CA cert was also created on the fly, i.e. without the need

static builds

2011-12-15 Thread passfree
Hi there, I am creating a cmd based on NSS. I decided to use the NSS build system just like all other cmds. It builds well and it works. Now, I really want to be able to distribute this executable but without the need to ship NSS and NSPR and all other dependant libraries from the mozilla tree. I

Re: SSL_ConfigSecureServer and on the fly cert generation

2011-12-07 Thread passfree
On Dec 2, 6:26 pm, Robert Relyea wrote: > On 12/02/2011 07:46 AM, passfree wrote:> I am writing an experimental tool > and I need to generate an SSL server > > on the fly. Needless to say, NSS seams like the perfect choice but > > here is where I am stuck. > > > SS

SSL_ConfigSecureServer and on the fly cert generation

2011-12-02 Thread passfree
I am writing an experimental tool and I need to generate an SSL server on the fly. Needless to say, NSS seams like the perfect choice but here is where I am stuck. SSL_ConfigSecureServer excepts a cert a key and a type. I've tried to look into certutil to see how these are generated but I find it

NSS and nonblocking sockets

2010-11-26 Thread passfree
Hi list, I am developing a XPCOM component to wrap input/output stream pairs into ssl for server or client communication. I am not familiar with NSS and I don't know how to write proper xpcom components in C but I have a working implementation. I have one problem though. I do not know how to deal

Re: NSS ss->sec.uncache is NULL

2010-11-26 Thread passfree
On Nov 24, 7:17 pm, passfree wrote: > On Nov 24, 6:28 pm, Nelson Bolyard > wrote: > > > > > > > On 2010-11-24 09:32 PDT, passfree wrote: > > > > Hi there, > > > > I am developing a generic SSL pipe XPCOM component which can be used > > &

Re: importing CAs into the certificate store

2010-11-24 Thread passfree
On Nov 24, 6:19 pm, Nelson Bolyard wrote: > On 2010-11-22 14:40 PDT, passfree wrote: > > > I am building a firefox extension which provides a http proxy server > > which will be used for development and testing web applications, (all > > in one development and testing env

Re: NSS ss->sec.uncache is NULL

2010-11-24 Thread passfree
On Nov 24, 6:28 pm, Nelson Bolyard wrote: > On 2010-11-24 09:32 PDT, passfree wrote: > > > Hi there, > > > I am developing a generic SSL pipe XPCOM component which can be used > > on any Input/Output stream pair. So far it sort of works but I am > > facing one

NSS ss->sec.uncache is NULL

2010-11-24 Thread passfree
Hi there, I am developing a generic SSL pipe XPCOM component which can be used on any Input/Output stream pair. So far it sort of works but I am facing one problem and I am not sure how to deal with it. The problem arrises when a client connects to a server but refuses to continue because of certi

importing CAs into the certificate store

2010-11-23 Thread passfree
I am building a firefox extension which provides a http proxy server which will be used for development and testing web applications, (all in one development and testing environment). The extension makes use of one binary component which I conveniently called SSL Pipe. The pipe simply wraps an inpu

ssl stream pipe

2010-10-02 Thread passfree
Hi, I am trying to build a SSL stream pipe component and I am stuck so I am hoping someone can give me the right direction. the component is used like this: let p = CC['sslpipe'].createInterface(CI.ISSLPipe); p.init(); p.write("GET / HTTP/1.0\r\n\r\n"); Now when p.read(count); is called it shou