sues
>
> Thanks
>
> Matt
>
>
> On 21/11/17 08:53, mahesh gs wrote:
> > Hi,
> >
> > We were able to further localize this problem and found the problem is
> > with the function "BIO_dgram_sctp_wait_for_dry". In this function after
> > e
Current version of openssl we are using is 01.01.00g.
We have tested and able to reproduce this issue with the OPENSSL 01.00.02k
version that is packaged with RHEL 7.4 as well.
Thanks,
Mahesh G S
On Mon, Nov 20, 2017 at 4:42 PM, mahesh gs <mahesh...@gmail.com> wrote:
> Hi Matt,
>
rs "read_state_machine" where alert is to be red.This causes
SSL_Connect to be in infinite loop.
Thanks,
Mahesh G S
On Fri, Nov 17, 2017 at 3:36 PM, Matt Caswell <m...@openssl.org> wrote:
>
>
> On 17/11/17 06:42, mahesh gs wrote:
> > Why
> > does client r
he handshake failure alert
is sent from server?
Openssl version used is 01.01.00g. I am also attaching the latest pcap file
for your reference.
On Tue, Nov 14, 2017 at 4:35 PM, Matt Caswell <m...@openssl.org> wrote:
>
>
> On 14/11/17 10:44, mahesh gs wrote:
>
> > case SSL_ERR
}
return true;
}
Thanks,
Mahesh G S
On Tue, Nov 14, 2017 at 4:01 PM, Graham Leggett <minf...@sharp.fm> wrote:
> On 14 Nov 2017, at 12:00 PM, mahesh gs <mahesh...@gmail.com> wrote:
>
> We have application that provide DTLS security for SCTP connections.
> During our
Hi All,
We have application that provide DTLS security for SCTP connections. During
our testing we found that API "*SSL_connect* " fail and always returns
SSL_ERROR_WANT_READ which causes infinite loop in the application.
Scenario:
1) On Server side "Client Certificate Request" is enabled by
Hi All,
I have query regarding the SSL_read on blocking socket. How to come out of
blocking SSL_read when we have to close the connection ?
As per the documentation SSL_read will only return if there is any data or
an error occurred.
"If the underlying BIO is *blocking*, SSL_read() will only
Hi,
We have an application which has SCTP connections we have secured the SCTP
connections using the openssl DTLS. DTLS is working as expected other than
the SCTP events.
We use the API "BIO_new_dgram_sctp" to create a BIO objects and we register
a callback function to openssl using API
Hi All,
I am using openssl version 01.01.00f for providing TLS and DTLS security
for TCP and SCTP connection for our application. I have query regarding the
"Ciphers" that are accepted by the SSL_CTX_set_cpiher_list API. The list of
ciphers that are supported by openssl version 01.01.00f that is
Hello All,
We are using openssl for providing the secured communication for our
application. I have some basic queries about the openssl behaviour.
1) What happens to the existing SSL connections on certification expiry?
Does the openssl disconnects the existing connection?
2) How can i get the
On Tue, May 2, 2017 at 2:36 PM, Matt Caswell <m...@openssl.org> wrote:
>
>
> On 02/05/17 06:59, mahesh gs wrote:
> > Hi Matt,
> >
> > Sorry for delayed response. I was on leave.
> >
> > Yes, ours is a library and we do not wish to ignore the signal
On Sun, Apr 30, 2017 at 11:11 PM, Michael Tuexen <
michael.tue...@lurchi.franken.de> wrote:
> > On 20. Apr 2017, at 20:01, mahesh gs <mahesh...@gmail.com> wrote:
> >
> > Hi,
> >
> > This issue occur purely based on the time (sequence of events) at whi
, Matt Caswell <m...@openssl.org> wrote:
>
>
> On 27/04/17 11:56, mahesh gs wrote:
> > Hi,
> >
> > We are using Openssl for establish a secure communications for both
> > TCP/SCTP connections.
> >
> > In our application it is possible that remo
Hi,
We are using Openssl for establish a secure communications for both
TCP/SCTP connections.
In our application it is possible that remote end forcefully disconnect the
connection due to which
SSL_Write raises a SIGPIPE which we want to suppress. Does openssl
provide any way to set
e
> with much more detail (at least I am assuming this is the same issue):
>
> https://github.com/openssl/openssl/issues/3251
>
> Matt
>
>
> On 18/04/17 21:17, Michael Tuexen wrote:
> >> On 13. Apr 2017, at 11:11, mahesh gs <mahesh...@gmail.com> wrote:
> >>
&
Hi,
We are running SCTP connections with DTLS enabled in our application. We
have adapted openssl version (openssl-1.1.0e) to achieve the same.
We have generated the self signed root and node certificates for testing.
We have a strange problem with the incomplete DTLS handshake if we run the
support.
On Thu, Feb 23, 2017 at 10:43 AM, mahesh gs <mahesh...@gmail.com> wrote:
> Hi Michael,
>
> I am using "Red Hat Enterprise Linux Server release 6.4 (Santiago)" and
> openssl version is 1.1.0.
>
> SCTP version :
>
> [root@localhost DIAMETER]# rpm -qa
Thanks,
Mahesh G S
On Wed, Feb 22, 2017 at 8:33 PM, Michael Tuexen <
michael.tue...@lurchi.franken.de> wrote:
> > On 22 Feb 2017, at 07:47, mahesh gs <mahesh...@gmail.com> wrote:
> >
> > Hi,
> >
> > Thank you for sharing the sample code.
> >
> >
Hi,
We have a client, server applications that is using SCTP as a transport
protocol. We have to secure the connections using DTLS. I am using openssl
version 1.0.2 which supports DTLS. But the problem i am facing is usage of
DTLS SCTP related API's. Openssl documentation does not clearly explain
19 matches
Mail list logo
