Hi bigearsbilly
Quote:
Originally Posted by bigearsbilly
does the -e -n inhibit newlines?
if so the perl read is waiting for a newline char probably.
|
the -n does in fact not add a newline after the echo command, but I composed the $inp string with the required "\n" chars (that's what the -e is required for, at least acc. man echo). The proof is, that is actually runs "CA.pl -newca <inf2". Remember, inf is generated from same "echo -e "$inp" >inf2" $inp string. finally, I get the same behaviour when running "echo -e "$inp" | CA.pl -newca"
actually here is the way i generate inp:
Quote:
|
inp="\n$cc\n$sp\n$loc\n$on\n$un\n$cn\n$email\n\n\n"
|
you can see the new lines (\n) and the parameters like $cc (country code) ...
again, if $inp is echoed ot a file, and this is redirected to CA.pl it runs perfectly. The passphrases have to be keyed in physically (desired imho), the rest is read from $inp respectively inf2
besides: i run Suse 10.3, 64 bit, last updated 3 hours ago, xen-pae, AMD X2 64, 4G ram, Raid5 LVM.
any other idea?
