An SSL-encrypting socket wrapper
Go to file
2007-08-28 15:02:14 +00:00
.cvsignore - Port to NSS 2007-08-28 15:02:14 +00:00
Certificate-Creation - Update to stunnel-4.11 2005-07-12 09:30:02 +00:00
Makefile Setup of module stunnel 2004-09-09 12:45:02 +00:00
nss_compat_ossl-0.9.1-stunnel.patch - Port to NSS 2007-08-28 15:02:14 +00:00
pop3-redirect.xinetd auto-import stunnel-4.04-4 from stunnel-4.04-4.src.rpm 2004-09-09 12:48:57 +00:00
README.NSS - Port to NSS 2007-08-28 15:02:14 +00:00
sfinger.xinetd auto-import stunnel-4.04-4 from stunnel-4.04-4.src.rpm 2004-09-09 12:48:57 +00:00
sources - Port to NSS 2007-08-28 15:02:14 +00:00
stunnel-4.08-authpriv.patch - update to 4.08 2005-03-16 20:45:02 +00:00
stunnel-4.18-sample.patch - Update to stunnel-4.18 2006-10-25 00:47:56 +00:00
stunnel-4.20-nss.patch - Port to NSS 2007-08-28 15:02:14 +00:00
stunnel-pop3s-client.conf auto-import stunnel-4.04-4 from stunnel-4.04-4.src.rpm 2004-09-09 12:48:57 +00:00
stunnel-sfinger.conf auto-import stunnel-4.04-4 from stunnel-4.04-4.src.rpm 2004-09-09 12:48:57 +00:00
stunnel.spec - Port to NSS 2007-08-28 15:02:14 +00:00

To convert an existing stunnel set up to NSS, at minimum it is necessary to:
- create a NSS database directory, $SSL_DIR
  $ certutil -d $SSL_DIR -N
- import server and CA certificates:
  $ certutil -d $SSL_DIR -A -n server_cert_nickname -i server_cert.pem
- import server private key:
  $ openssl pkcs12 -export -in server_key.pem -out server_key.pfx
  $ pk12util -d $SSL_DIR -i server_key.pfx
- modify stunnel.conf to use "server_cert_nickname" instead of path to
  "server_cert.pem" in "cert"
- when starting stunnel, make sure $SSL_DIR is present in the
  environment