On Thu, Oct 3, 2013 at 5:32 PM, Ben Laurie wrote:
>
>
>
> On 3 October 2013 22:14, Jeff Trawick wrote:
>
>> E.g., run
>>
>> echo GET / | openssl s_client -connect host:port
>>
>> It does the handshake then stalls until you press a key (which will be
>> left unused in the buffer when openssl exit
On 3 October 2013 22:14, Jeff Trawick wrote:
> E.g., run
>
> echo GET / | openssl s_client -connect host:port
>
> It does the handshake then stalls until you press a key (which will be
> left unused in the buffer when openssl exits), then it sends the input. I
> guess the kbhit() in the s_client
On Fri, Oct 4, 2013 at 9:17 AM, Salz, Rich wrote:
> When you run it interactively, does it work right away or do you need to
> hit TWO returns?
>
It works right away.
The keypresses trigger the read of stdin (since the
WaitForSingleObject(stdin) is bypassed due to the OPENSSL_SYS_MSDOS issue),
When you run it interactively, does it work right away or do you need to hit
TWO returns?
--
Principal Security Engineer
Akamai Technology
Cambridge, MA
On Thu, Oct 3, 2013 at 5:14 PM, Jeff Trawick wrote:
> E.g., run
>
> echo GET / | openssl s_client -connect host:port
>
> It does the handshake then stalls until you press a key (which will be
> left unused in the buffer when openssl exits), then it sends the input. I
> guess the kbhit() in the s
