The mkcert.sh script can't easily be "scripted." We'd like to do this
as part of a nightly build and regression test. Writing an expect
script is too much overhead.
I'm not sure why, but for some reason the "Encrypt Private key?"
question
(at step 4; we're doing snakeoil since it's just for testing).
always ends up at /dev/tty. I gave up (for now) trying to figure out
why and instead my script patches mkcert.sh to have "rc=n" after the
read.
That's gross; if there's interest I'll try to figure out a real fix.
But given that, then the following works for me:
TERM=dumb echo @@@@@@@@@@n@ | tr @ '\012' | make certificate
'TYPE=test'
As an aside it would be nice if the prompting were all done
consistently.
Sometimes a "prompt" variable is used, sometimes it's set on the awk
command line, sometimes it's an inline printf, etc. Personally, my
taste would be for the following
prompt="Is this what you want (y/n) [n]?"
echo "$prompt" | tr -d '\012'
I can easily send a patch for that if desired.
/r$
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
