Greetings:
How does one configure openSSL so that it builds with DTLS support?
I've been trying to configure (and build) net-snmp so that it supports the
DTLSUDP transport (as well as SSH). I keep getting informed that I need an
openSSL library that supports DTLS.
I downloaded the most recent
I am using SSL_is_init_finished this API function to check if init is
finished.
But its not even reaching that code.
The very first call i made to SS_Connect, and after that i read data from
w_BIO and then sending that on TCP, and on getting that data, server gives
this error.
and for debugging pur
On 05/24/2011 08:58 PM, Bill Durant wrote:
> ...
>> Ah that explains it. There is no darwin64-x86_64-cc target for the validated
>> tarball so it isn't supported. It is possible to add new platforms via a
>> change letter but so far no one has been interested in including that one.
>
> What is the
Okay, u r writing the client, so you need to do connect, now ssl_connect is
going to do the complete SSL handshake, which involves multiple read and
writes, now since you are using memory bios, ssl connect is going to read
from the r_membio and write into the w_membio. The data has to go out the
tc
On 05/24/2011 07:00 PM, vidyasagar Ravipati wrote:
> Hi, I am compiling and running open ssl fips compliant version and
> trying to run the power on self tests during boot up time as part of
> FIPS requirements. I have observed invokation of zeroization function
> as well as output displayed as par
FYI
Here is the steps:
- See Install.w32 and follow steps for "Borland C++ builder 5"
- You will have erros at compilation time
Errors are due to the following 2 lines
struct _timeb tb;
and
_ftime(&tb);
Workaround for BCB 6:
Change those lines to the following.
#if (__BORLANDC__==0x
Just to clarify my last message, I am using state machine, i called
SSL_connect after creating ctx and ssl objs, 2 mem bios and set them to ssl,
and then read data from bio, and sent that to server and that gave me error.
On Wed, May 25, 2011 at 10:12 AM, Harshvir Sidhu wrote:
> Thanks Gayatri.
Thanks Gayatri.
This is what i am doing, but i dont have any buffer to send initially, my
data transfer start from server side.
What i was doing is, calling SSL_connect after initialization and then in
the socket read and write code, i was doing encrypt and decrypt accordingly,
but the very first m
So finally u have agreed to my initial suggestion of state machines :)
The basic steps in terms of am algorithm are as follows
A. Create the ssl ctx and ssl. Obj
B. Create a pair of memory bios and attach them to the ssl obj, one is
for read and the other is for write.
C. Create the tcp fds and c
Hi,
I am trying to implement State Machine based on the demo application,
that is a server code.
Like i am writting the client side.
So when i try to do handshake, by calling SSL_connect, which i have used
memory bios, after that i check for data available, and then i read data and
send to
On Wed, May 25, 2011, Thulasi wrote:
> > The answer however has changed: experimental TLS v1.2 code is present in
> HEAD
> > and the 1.0.1 stable branch. The code hasn't been fully tested yet so some
> > bugs may remain. There are some known interop problems with some ECC
> > ciphersuites: that is
> The answer however has changed: experimental TLS v1.2 code is present in
HEAD
> and the 1.0.1 stable branch. The code hasn't been fully tested yet so some
> bugs may remain. There are some known interop problems with some ECC
> ciphersuites: that is OpenSSL can connect to some servers but not oth
On Wed, 25 May 2011 12:21:04 +0200
"Dr. Stephen Henson" wrote:
> On Wed, May 25, 2011, Erwann ABALEA wrote:
>
> > Bonjour,
> >
> > Hodie VIII Kal. Iun. MMXI, shoutee scripsit:
> > > I want to run a TLS Server with support of cipher suite
> > > 'ECDH-ECDSA-AES128-SHA256' (RFC 5289). Unfortunatel
Bonjour,
Hodie VIII Kal. Iun. MMXI, Dr. Stephen Henson scripsit:
> On Wed, May 25, 2011, Erwann ABALEA wrote:
> > Hodie VIII Kal. Iun. MMXI, shoutee scripsit:
> > > I want to run a TLS Server with support of cipher suite
> > > 'ECDH-ECDSA-AES128-SHA256' (RFC 5289). Unfortunately I can't find these
As I know, the cipher suite 'ECDH-ECDSA-AES128-SHA256' is belong to the TLS 1.1
or TLS 1.2.OpenSSL has not supported TLS 1.1 or TLS 1.2 yet, but they are now
at implementation of TLS 1.1 ,1.2.
At 2011-05-25 18:50:23，shoutee wrote:
>Hi,
>
>I want to run a TLS Server with support of cipher su
Eric S. Eberhard wrote:
or ... keep it simple and at least consider using stunnel.
I use stunnel myself in some situations. It's a great tool.
But bear in mind that the application then has no access to authentication
information of the SSL layer.
Ciao, Michael.
On Wed, May 25, 2011, Erwann ABALEA wrote:
> Bonjour,
>
> Hodie VIII Kal. Iun. MMXI, shoutee scripsit:
> > I want to run a TLS Server with support of cipher suite
> > 'ECDH-ECDSA-AES128-SHA256' (RFC 5289). Unfortunately I can't find these
> > cipher suite
> > within tls1.h. ECDSA is only availab
Bonjour,
Hodie VIII Kal. Iun. MMXI, shoutee scripsit:
> I want to run a TLS Server with support of cipher suite
> 'ECDH-ECDSA-AES128-SHA256' (RFC 5289). Unfortunately I can't find these
> cipher suite
> within tls1.h. ECDSA is only available with SHA1.
>
> Since openssl supports SHA256 I though
Hi,
I want to run a TLS Server with support of cipher suite
'ECDH-ECDSA-AES128-SHA256' (RFC 5289). Unfortunately I can't find these cipher
suite
within tls1.h. ECDSA is only available with SHA1.
Since openssl supports SHA256 I thought that ECDSA with SHA256 should be
available, or am I missing
19 matches
Mail list logo
