On 5/24/2013 8:58 PM, Dave Thompson wrote:
------------------------------------------------------------------------
*From:* [email protected]
[mailto:[email protected]] *On Behalf Of *Salz, Rich
*Sent:* Friday, 24 May, 2013 14:05
*To:* [email protected]
*Subject:* RE: Pipe command not working
Windows doesn’t do pipes; you have to use temp files.
Not true. IIRC the original MSDOS-based Windows (3.1, 95, 98) didn't,
but all "NT" series Windows do. I use Windows pipes all the time --
including for the sort of openssl commandline operations OP posted.
One thing to watch out for, though, with C programs (including openssl):
Actually, MS-DOS since version 2.00 did pipes, but it was emulated by
redirecting output to a temporary file, then when the first program
ended, starting the second program with input redirected from the temp
file, finally deleting the temp file after the second command exited.
For piping one commandline openssl to another, using (as I do) the
ShiningLight build and thus the "visual c++" runtime, it has worked,
but for arbitrary mixtures of other Windows programs I have had issues.
The Visual C++ runtime uses a hidden binary parameter to pass the
text/binary status and native NT handle mapping of each emulated POSIX
file handle to launched programs. It is possible that the ShiningLight
build has the good fortune of using a Visual C++ runtime which plays
well with the Visual C++ runtime used by the command shell in this
regard.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com
Transformervej 29, 2730 Herlev, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [email protected]
Automated List Manager [email protected]
