I have written a test script to semi-automate the testing of stunnel by
configuring a couple of systems to allow network services between them to be
encrypted using stunnel. The script sets up:
* stunnel config files (both machines)
* Sets up a single CA using OpenSSL
* Generates server certificates and signs them.
* Sets up an unencrypted web server (apache).
* spits out a script which uses wget to connect to the
webserver (running on the other machine) via stunnnel.
The reason for writing the script is it gives a simple test case should anybody
need to make some basic sanity checks on stunnel, say after upgrading. I was
also a usefull exercise for me WRT learning stunnel and OpenSSL syntax :-)
Does putting the script in the sfwnv gate make sense ? I was not actually going
to deliver the script in the final package (because it would need supporting)
but putting it in the gate makes it available should anybody need to use it.
The gatekeeper is neutral about this, but he does not want the gate full of
unused or dead code, which makes sense.
Anybody have any opinions about this ?
(The "correct" answer here is probably to put the script in the STC framework,
but thats simply too much effort.)
Thanks
Mark
----------------------------------------------------------------------------
Mark Fenwick, Solaris Security Technologies.
__o
Sun Microsystems Inc, Menlo Park, California. `\<,_
(*)/ (*)
----------------------------------------------------------------------------
