![]() > If willing to change that, then that is of course also > The solution I outlined was for no changes to openssl_s. On Tuesday, Septemat 9:49:54 PM UTC-3, Arne Vajhøj wrote: Which I assume will not work well without more SYS$QIOW IO$_ACCESS with FIB block is not needed,īut SYS$QIOW IO$_READVBLK read blocks not lines, SYS$OPEN with FAB$M_UFO will give the channel so If willing to change that, then that is of course alsoīut more work is needed than described above. The solution I outlined was for no changes to openssl_s. > 2.) If device, call $ASSIGN, else call $OPEN. > 1.) Detect whether SYS$COMMAND is a file or device. > a pseudo terminal (PTD$ routines) and get the file input > program in a separate process attached to > Usual (?) workaround is to run the problematic > assign/define from terminal to a file will fail. > SYS$QIO(W) is device dependent, so all attempts to > VMS-specific code to detect an EOF condition and propagate it to the As far as I can see, there is no provision in the > shimmed in front, presumably to be able to play nice with the select() > It's doing a $QIO to SYS$COMMAND, but it's got a pair of sockets $ openssl s_client -quiet -no_ign_eof -connect GOOGLE.COM:443Ģ 12:49:12 TerminalSocket: SYS$QIO () - 000000ACĭepth=2 C = US, O = GeoTrust Inc., CN = GeoTrust Global CA Here's an excerpt from the log showing output/errors from the command: Here's some more test code, run in batch instead (just had to define the openssl command first, and quiet the output of that, since it turns on verify inside ssl1$ ): Still ignores the data provided in deck / eod, and prompts interactively. Usage (where x.y.z is a host with https on port 443) $ openssl s_client -quiet -no_ign_eof -connect 'p1':443 It's all variations on the same theme, so I didn't mention everything. > Have you tried redirecting sys$input to sys$command within a 1 line command procedure? That should retain the "terminal" characteristics without requiring any input from the user. On Tuesday, Septemat 12:28:58 PM UTC-3, abrsvc wrote: I only want to be able to do the same on VMS. Perfect for being able to script the test and run against a bunch of sites. It happily accepts I/O redirection, obeys the EOF, and quits after showing me what I wanted to see. $ echo Q | openssl s_client -quiet -connect x.y.z:443 Verify error:num=21:unable to verify the first certificate ![]() ![]() Verify error:num=20:unable to get local issuer certificate $ openssl s_client -quiet -no_ign_eof -connect x.y.z:443 < /dev/nullĭepth=0 C = CA, OU = Domain Control Validated, CN = x.y.z On another OS, I could do something like: $ openssl s_client -quiet -no_ign_eof -connect localhost:443 < NL: ![]() $ pipe openssl s_client -quiet -no_ign_eof -connect localhost:443 < NL: $ pipe echo "Q" | openssl s_client -quiet -no_ign_eof -connect localhost:443 I get the same result each time: it always reads from the terminal instead of the redirected I/O stream. It doesn't matter if I change the command to one of the following three alternatives. Now I have to wait for that to connect, then enter "Q" on a line by itself to make it disconnect. $ openssl s_client -quiet -no_ign_eof -connect localhost:443 define/user sys$input, redirection via PIPE command).Ĭonsider the following to quickly check if the cert chain for an OSU DECthreads HTTPServer is actually configured correctly: Argh! How do I convince openssl s_client to read input from somewhere other than the terminal? All the usual tricks don't work (e.g. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |