Carl,
Thanks for your reply. I would love to have a service which I could
call, unfortunately my Windows development skills don't stretch that far
as I am an infrastructure person with some basic VBscripting skills.
Do you (or another member of this list as CC'ed) have something that
Leon:
I suggest that you write a program that uses file descriptors for IO? I'd
write it in C.
On Mon, Oct 22, 2012 at 5:51 AM, Funnell, Leon leon.funn...@catlin.comwrote:
We have Windows application which passes data to OpenSSL.exe to encrypt as
a Windows command, then scrapes the encrypted
I would hope that one of us could provide you something given a week or so...
very busy with work currently but I'm sure I could do something in time.
Carl
From: owner-openssl-us...@openssl.org [owner-openssl-us...@openssl.org] on
behalf of John Zavgren [j...@zavgren.com]
Sent: 14 November
(Top posting to keep this thread consistent)
Hi,
As for encrypting/decrypting a file via stdin/stdout, the openssl.exe
program can already do that (it is almost the default behavior for those
commands that encrypt/decrypt things, you may need to add the -passin
option to indicate if the
Got it working (almost) in vbscript. I have the following problem however:
If I run Openssl.exe on it’s own waiting for input, I can tell it to do one
encryption only. See the steps I have followed below:
1. In Windows, run CMD.exe
2. Cd to C:\OpenSSL-Win64\bin
3.
Do have really have to use OpenSSL.exe or could you create/use a modified
version of that tool that does exactly what you expect?
Your scaling problem is because of the entropy gathering each time OpenSSL is
launched. This takes a significant amount of time, especially compared to the
actual
We have Windows application which passes data to OpenSSL.exe to encrypt
as a Windows command, then scrapes the encrypted data back from the
output. The Windows app can call external Windows commands but we
cannot call APIs or extend the functionality programmatically.
Functionally it works, but
If you start openssl.exe, that's the mode it's in by default - waiting for
commands from stdin, writing the output from those commands to stdout. Isn't
that what you're looking for?
If you're looking for advice on the programming details of attaching to its
stdin and stdout and
Msdn.com is excellent. Good advice, few flames.
--
Sent from my mobile phone. Please excuse my brevity.
Charles
Jeremy Farrell jeremy.farr...@oracle.com wrote:
If you start openssl.exe, that's the mode it's in by default - waiting for
commands from stdin, writing the output from those commands