DTLS handshake messages

I'm planning to implement an application that has multiple threads. This application uses DTLS protocol. Can each DTLS handshake message go to different thread or is it must that all the DTLS handshake messages should be handled by single thread. Please let me know if anyone has done something

Re: DTLS handshake messages

Hi Sravanthi, I have implemented this as follows: One thread per listen socket, calling DTLSv1_listen. This thread spawns one thread per client and those treads call SSL_accept. The listening threads share a single SSL_CTX, and each call to SSL_new is protected by a mutex. Each SSL object has

Regarding Rfc5764

Hi, I am new to openssl and I was reading rfc 5764 (DTLS-SRTP). It says that DTLS handshake and srtp flow will be done between same source and destination port, means same port will receive dtls message as well as srtp packets. In middle of srtp packets, DTLS handshake can also be done for

SSL3_GET_FINISHED:digest check failed on Solaris OpenSSL 1.0.0f

Occasionally (1% of the time), my SSL client throws a digest check failed when connecting to the server. The server gets the alert decrypt error. The scenario is this: 1. The client and server establish a successful handshake and dump the remote side's SSL information (including the session ID).

答复: How can I enable aes-ni in openssl on Linux

Hi John and all, I made one OpenSSL AES-NI study notes and one demo sample before, you can refer the enclosed files. By the way, you can also find some information from official Intel Developer Zone website for Intel AES-NI technology.

Somewhat conflicting configuration and strange behaviour (was: SELinux prevents running squid 3.3.11 on CentOS 6.5)

Hello Eliezer Croitoru, this is also to the OpenSSL mailing list, because can someone verify that the CA certificate and the SSL certificate fit together - the last section of this mail. (of course I can do this by myself, but here I want to opinion of a 3rd party) I have the solution that

Re: [openssl-users] Somewhat conflicting configuration and strange behaviour

Bonjour, The certificate specifies digitalSignature as its sole key usage. That means the certified key can only be used to sign data, and not perform any decrypt operation. If your server+client are negotiating a (EC)DHE-RSA-* ciphersuite, that's OK because the server's RSA private key will

ssh-add refuses to use the key on my USB thumb drive

This is because the thumb drive is a vfat device, which has a very limited permissions model. The permissions of every file, as reported by the device driver, are always 0644, and there is no escape. When I try to add the identity from the key file, ssh-add says:

Re: ssh-add refuses to use the key on my USB thumb drive

Use Google? ;) mount_msdosfs -u x -m 700 /dev/usbdevice /mnt/ where -u is the uid of your required user. alan -- Sent from my Android device with K-9 Mail. Please excuse my brevity.