This is a multi-part message in MIME format.

------=_NextPart_000_0000_01C864CE.E377F7F0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi All;

I am trying to port Open SSL on VDSP4.5 (VDK RTOS).But open ssl
having 5 types of terminal interface supported,

* TERMIO, TERMIOS, VMS, MSDOS and SGTTY

*/

But VDK is not supporting it. So please tell me how to bypass it. here
sgtty.h header is not in open ssl project folder. Can we use rapper and
debug this problem. How we can solve this problem.

Onre doubt I have for porting VDK where I will change. What change is
required for porting on VDK(RTOS).

Please reply me.

Thnx.

Regards;

Ajeet Kumar Singh

------=_Part_8021_31114334.1201805817351
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Is your key in the right format?

On Jan 24, 2008 3:47 PM, Artur Jasowicz ondecktech.com> wrote:

Does TLSv1.1 support is provided in the latest openssl version.

Hello,

Openssl with Chil engine configuration getting error on Microsoft
Windows Server 2003 64 bit.

C:\openssl-0.9.8g\out32dll>openssl.exe speed -engine chil rsa2048
can't use that engine
1456:error:25078067:DSO support routines:WIN32_LOAD:could not load the
shared library:.\crypto\dso\dso_win32.c:172...

Hi,

I followed the INSTALL.WCE directions.
What resulted was the Crypto stuff works fine.

The SSL stuff does not seem to hand shake correctly. I am using TLSv1.
I am able to load my Cert and private key, but I keep getting a
SYS_ERROR_SYSCALL error on the SSL_Connect. As described below from the
man pages, it seems that the WinCE socket code is returning an EOF on
the SSL_Connect.

_______________________________
SSL_ERROR_SYSCALL
Some I/O error occurred. The OpenSSL error queue may contain
more information on the error. If the error queue is empty
(i.e. ERR_get_error() returns 0), ret can be used to find
out more about the error: If ret == 0, an EOF was observed
that violates the protocol. If ret == -1, the underlying BIO
reported an I/O error. (For socket I/O on Unix systems,
consult errno.)
_______________________________

This is a multipart message in MIME format.

--=_alternative 00253AF5652573DF_=
Content-Type: text/plain;
charset="US-ASCII"

Hi All,

The cipher-spec string - 'HIGH:!ADH:!MD5' when I executed, it gives
cipher suites as follows:

./openssl ciphers -v 'HIGH:!ADH:!MD5'

------=_Part_20538_10696737.1201679736081
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello,

I cannot compile and build openssl with Visual Studio 8 & Windows Vista
business. I don't know if openssl is compatible with Windows Vista or now it
is not possible use and run Openssl in this OS.

I have run the configure without any problem and I used masm but I run
"nmake -f ms\ntdll.mak" then I get the next error:

C:\openssl-0.9.8g>nmake -f ms\ntdll.mak
Microsoft (R) Program Maintenance Utility Version 8.00.50727.762
Copyright (C) Microsoft Corporation. All rights reserved.
Building OpenSSL
cl /Fotmp32dll\uplink...

I have OpenSSL running inside of a SOCKET based server to encrypt the IO. Im
finding that over time the memory use in the process grows w/re the amount
of data served over the socket. When the 'listening' socket closes
gracefully I see a small leak but nothing like the amount of growth that I
see in the process list.

When the process closes I see the following leak msg:
Detected memory leaks!
Dumping objects ->
{4956} normal block at 0x00E8BC10, 12 bytes long.
Data: <0 " > 30 BE E8 00 00 00 00 00 9C 22 02...

I am still having a problem running RSA_verify which returns 'Data too large
for modulus' errors. If I check the big number value of the 'signatureValue'
and 'Modulus' they are 268628280 and 268628488 respectively which obviously
explains the error I am receiving. I have changed my code from using
'strlen' to the base64 decoded length as suggested but this has made no
difference. These are the steps I am taking with the Signature XML I am
receiving in order to verify the signature:

1) Extracting the 'SignedInfo' node and creating a 20 byte SHA1 hash of the
value of it and its contents.
2) Extracting the 'Modulus' and 'Exponent' values and then Base64 decoding
both. This creates a 128 byte modulus and 3 byte exponent.
3) Extracting the 'SignatureValue' value and Base64 decoding it which
creates a 128 byte signature.
4) Converting the Base64 decoded modulus and exponent values and assigning
them to a RSA structure (n and e).
5) Calling RSA_Verify with 'NID_sha1', the 20 byte hash, the 128 byte
signature value, a signature size of 128, and the previously populated RSA
structure.

Is there something I am doing incorrectly here?

On Wed, Jan 30, 2008 at 09:57:27AM +1300, Chris Pugmire wrote:

The solution depends on how the server loads its certificates. If the
server is using:

SSL_CTX_use_certificate_chain_file()