Re: [stunnel-users] Username authentication

--===============0561648463==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="nO3oAMapP4dBpMZi"
Content-Disposition: inline


--nO3oAMapP4dBpMZi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

About 2008-03-04 17:05 -0500, Joe Kemp voiced:

> I want to try to use stunnel as a "simple" client vpn.
> It solves all of my encryption issues but I would like to
> verify a username/password before it lets the traffic
> through. I didn't see any patches or hacks out there
> that did this. Has this been attempted before or am I on
> my own. I would also be interested in other solutions
> based on openssl that are not network device level VPNs
> clients.

You want to use X509 certificate verification. It's the way
authentication is done in the SSL world. It's built into Stunnel.

You may also want to look at tappipe, which is Michal's
VPN-over-Stunnel package. I use it very successfully for
a few of my connections.

> Already using client side certificates and I know that is the normal SSL =
authentication mechanism....

Then why don't you want to use them? ;-)

--=20
Brian Hatch Waltz, nymph, for quick jigs vex Bud.
Systems and --28 letter panagram
Security Engineer
http://www.ifokr.org/bri/

Every message PGP signed

--nO3oAMapP4dBpMZi
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFH0QwhVkMj8/ymYEsRArfkAJ4p+jJ/Gq9j5pKof8zFbSNtZYWcUQCeItzr
ig7P79GsWhW/TDSxJMMrJv8=
=uPAK
-----END PGP SIGNATURE-----

--nO3oAMapP4dBpMZi--

--===============0561648463==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
stunnel-users mailing list
stunnel-users@mirt.net
http://stunnel.mirt.net/mailman/listinfo/stunnel-users

--===============0561648463==--