I forgot to mention: the original application uses the Enhanced Cryptography
Provider (http://msdn.microsoft.com/en-us/library/aa386986%28v=vs.85%29.aspx)
which supports 128 bit RC4 keys. The application sets the RC4 cipher from a
full 128 bit key and a 128 bit salt.
On May 6, 2011, at 10:41 PM
Michael Tüxen wrote:
On May 7, 2011, at 10:40 PM, Justin Schoeman wrote:
William A. Rowe Jr. wrote:
On 5/7/2011 7:16 AM, Justin Schoeman wrote:
It does not matter which of these I try, openssl always binds to '::1:8008',
which does
not accept IPV4.
I h
On May 7, 2011, at 10:40 PM, Justin Schoeman wrote:
> William A. Rowe Jr. wrote:
>> On 5/7/2011 7:16 AM, Justin Schoeman wrote:
>>
>>> It does not matter which of these I try, openssl always binds to
>>> '::1:8008', which does
>>> not accept IPV4.
>>>
>>
>>
I have tried various comb
William A. Rowe Jr. wrote:
On 5/7/2011 7:16 AM, Justin Schoeman wrote:
It does not matter which of these I try, openssl always binds to '::1:8008',
which does
not accept IPV4.
I have tried various combinations of:
BIO_new_accept("0.0.0.0:8008")
This syntax should have bou
On 5/7/2011 7:16 AM, Justin Schoeman wrote:
>
> It does not matter which of these I try, openssl always binds to '::1:8008',
> which does
> not accept IPV4.
>> I have tried various combinations of:
>> BIO_new_accept("0.0.0.0:8008")
This syntax should have bound to all IPv4 interfaces alone,
so
On Fri, May 06, 2011, Bugcollect.com wrote:
> Hello,
>
> I need to exchange encrypted content with an existing application on Windows
> with an RC4 key that is salted as per
> http://msdn.microsoft.com/en-us/library/aa387782%28v=vs.85%29.aspx
> (KP_SALT_EX). Note that this is not a passphrase
On May 7, 2011, at 2:16 PM, Justin Schoeman wrote:
> Further information...
>
> I have read the source, and it says that either the port number (eg. "8008"
> alone, or '*:' (eg:"*:8008) will bind to all interfaces, and
> '::' (eg "::8008") will bind to the IPV6 wildcard, which on most
> OSs wi
Remus Rusanu wrote on Saturday, May 07, 2011 07:41:
> I need to exchange encrypted content with an existing application
> on Windows with an RC4 key that is salted as per
> http://msdn.microsoft.com/en-us/library/aa387782%28v=vs.85%29.aspx
> (KP_SALT_EX). Note that this is not a passphrase and sal
Further information...
I have read the source, and it says that either the port number (eg.
"8008" alone, or '*:' (eg:"*:8008) will bind to all
interfaces, and '::' (eg "::8008") will bind to the IPV6
wildcard, which on most OSs will also accept IPV4 connections.
It does not matter which of
Hi All,
We currently have a CA Server (a Solaris server) running openssl 0.9.8e
And clients (Embedded Linux) running with openssl 0.9.8m
We are thinking of upgrading the openssl versions on both the server, as
well as the clients.
We have some limitations regarding which versions are available o
Hi,
I'm not sure but I think salt and IV are two different things.
-re
On Sat, May 7, 2011 at 1:41 PM, Bugcollect.com wrote:
> Hello,
>
> I need to exchange encrypted content with an existing application on
> Windows with an RC4 key that is salted as per
> http://msdn.microsoft.com/en-us/librar
11 matches
Mail list logo
