On Sun, Oct 14, 2001 at 06:19:30PM +0200, Lutz Jaenicke wrote:
[...]
* If you have any patch to submit that will improve the behaviour of
s_client you are most welcome to post it to this list :-)
OK, here you go, someone please apply this:
diff -Naur apps/s_client.c apps/s_client.c
---
On Tue, Oct 16, 2001 at 02:30:03PM +0100, Adam Back wrote:
On Sun, Oct 14, 2001 at 06:19:30PM +0200, Lutz Jaenicke wrote:
[...]
* If you have any patch to submit that will improve the behaviour of
s_client you are most welcome to post it to this list :-)
OK, here you go, someone
I mentioned this to Ulf a while back when I found it.
I tried parsing the output of s_client with some perl code I was
writing, and I found that the connection information (cipher
selection, certificate chain if you ask for it with -showcerts) gets
mixed up with the HTTP response.
I tracked it
On Sun, Oct 14, 2001 at 04:01:23PM +0100, Adam Back wrote:
I tried parsing the output of s_client with some perl code I was
writing, and I found that the connection information (cipher
selection, certificate chain if you ask for it with -showcerts) gets
mixed up with the HTTP response.
What
Don't worry about the application -- it was a thow-away proof of
concept thing, already forgotten. You're probably right there are
otherways to do it. I did consider stunnel briefly but there was some
reason s_client fit better into the existing perl glue code I had.
Either way though
On Sun, Oct 14, 2001 at 04:43:30PM +0100, Adam Back wrote:
Either way though s_client's behavior is wrong, because even visually
you can't _find_ the connection info mixed in with the HTTP response;
my post was just to follow up having found the bug to fix the problem.
The note about the
