On Mon, Oct 7, 2013 at 7:47 AM, Jeff Trawick <[email protected]> wrote:
> See the attached patch which applies over openssl-1.0.1e and selects the > use of existing support for the Windows API > WaitForSingleObject(..STD_INPUT_HANDLE..) to trigger a read of stdin. That > logic is hidden currently because OPENSSL_SYS_MSDOS is defined whenever > OPENSSL_SYS_WINDOWS is defined. By enabling that existing Windows logic, > data on stdin triggers a read without the requirement of a physical > keyboard event. > Original symptom: On Windows, EOF on stdin isn't enough for s_client to realize that there's no more input; you have to press something on the keyboard. If this ever becomes interesting to someone with commit access, I can port this to the master branch and retest. > > ---------- Forwarded message ---------- > From: Jeff Trawick <[email protected]> > Date: Fri, Oct 4, 2013 at 9:44 AM > Subject: Re: redirected input to s_client on Windows: Any trick to avoid > the keypress? > To: [email protected] > > > On Fri, Oct 4, 2013 at 9:17 AM, Salz, Rich <[email protected]> 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), > so there's no problem in interactive mode. > > > >> >> >> >> >> -- >> >> Principal Security Engineer >> >> Akamai Technology >> >> Cambridge, MA >> > > > > -- > Born in Roswell... married an alien... > http://emptyhammock.com/ > > > > -- > Born in Roswell... married an alien... > http://emptyhammock.com/ > -- Born in Roswell... married an alien... http://emptyhammock.com/ http://edjective.org/
