SSL replacement idea

["Aaron D. Turner" <aturner@best.com>]

-----BEGIN PGP SIGNED MESSAGE-----


Ok, I was starting to compile Apache and going through the issues of
compiling with SSL and mod_perl.  What a pain.  Also, it means keeping two
copies of Apache, one with and one without SSL support (and two config
files, two html/cgi trees, etc.).  And if we have a httpd w/o mod_perl
support that now means 3 copies!  Anyways....

So I'm thinking, there's all this extra overhead (memory and maint),
there's gotta be an easier way since it's only us who will use the SSL
feature.

Then it hit me:

ssh -L 5555:vodka.linuxkb.org:80 vodka.linuxkb.org

then:

http://localhost:5555/

And viola, a secure and authenticated http connection to the server
without the overhead of SSL.  We use this at my work to give telecommuters
access to some internal web servers; it works really well.

Comments?

- -- 
Aaron Turner           | Either which way, one half dozen or another. 
aturner@pobox.com      | Check out the Red Hat Linux User's FAQ Online!
www.pobox.com/~aturner | http://www.pobox.com/~aturner/RedHat-FAQ/
All emails from this account are PGP signed.  Lack of a signature is "bad".
PGP Key fingerprint = FB E1 CE ED 57 E4 AB 80  59 6E 60 BF 45 1B 20 E8



-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNphCCTM3jpXy1kJtAQHv4gP/Xi7USSGJQfC6zCYMsNRWC2tj3nkfB8XW
G1CRiet0/x70RRIJ5wciFzhdKfhnCHwyxVNMm1yP2i3Jw8Zyw5DJuRAYxW4ntzcy
0ReI2BzeKH22BaWn2Lh/5SRD6mN0h9vGBxdy8u3Do2rjuFha2eZr12we6GCgefy5
pnjgJW1Oum4=
=Ytpk
-----END PGP SIGNATURE-----