Re: DTLSv1_get_timeout/DTLSv1_handle_timeout on server for each connection
On Jan 25, 2012, at 7:08 AM, Manish Yadav wrote: Hi all, could you please confirm if dtls timers are implemented at client side only and not on server side (only client retries/attempts to establish connection) or why they should be implemented on server side also. You need timers on the server side also. However, DTLSv1_get_timeout/DTLSv1_handle_timeout is only necessary if you use select. after looking at : http://crypto.stanford.edu/~nagendra/papers/dtls.pdf i understood that i need to call DTLSv1_get_timeout/DTLSv1_handle_timeout incase of non-blocking socket. but after looking at example available on net dtls_udp_echo2.c, i see only client side take care of this. i feel only client side should try to reconnect, why server should try to resend message to client. Not sure about dtls_udp_echo2.c. You might want to take a look at the examples available at http://sctp.fh-muenster.de/dtls-samples.html please share if you know any example on this. Maybe Robin has more examples... Best regards Michael thanks, manish __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: DTLSv1_get_timeout/DTLSv1_handle_timeout on server for each connection
Hi Michael, thanks for quick response. i had one more question, is it possible to do decoupling of ssl object and socket fd to avoid rehandshake? (i am thinking to create socketfd only for active clients, if it is inactive for sometime then close the connection/socket and for inactive clients keep the ssl object cached, whenever inactive clients send data create new fd and associate with old ssl object, similar to http://net-snmp.sourceforge.net/dev/agent/snmpDTLSUDPDomain_8c_source.html). is it possible? if i look at DTLSv1_listen, i am thinking i can not distinguish between active/inactive client? is it possible based on error value from DTLSv1_listen to tell if i received hello message or invalid message or invalid hello message/wrong cookie. thanks, manish On Wed, Jan 25, 2012 at 3:24 PM, Michael Tuexen michael.tue...@lurchi.franken.de wrote: On Jan 25, 2012, at 7:08 AM, Manish Yadav wrote: Hi all, could you please confirm if dtls timers are implemented at client side only and not on server side (only client retries/attempts to establish connection) or why they should be implemented on server side also. You need timers on the server side also. However, DTLSv1_get_timeout/DTLSv1_handle_timeout is only necessary if you use select. after looking at : http://crypto.stanford.edu/~nagendra/papers/dtls.pdf i understood that i need to call DTLSv1_get_timeout/DTLSv1_handle_timeout incase of non-blocking socket. but after looking at example available on net dtls_udp_echo2.c, i see only client side take care of this. i feel only client side should try to reconnect, why server should try to resend message to client. Not sure about dtls_udp_echo2.c. You might want to take a look at the examples available at http://sctp.fh-muenster.de/dtls-samples.html please share if you know any example on this. Maybe Robin has more examples... Best regards Michael thanks, manish __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
OpenSSL validation question
Hi, Does the FIPS module certification is missed if the fipscanister module is compiled to a configuration (architecture, compiler version etc) different from those listed on OpenSSL security policy? Our concern is if a change to something on the build tools like compiler version or architecture can invalidate the certification. Thanks -- Adriano Godinho
Re: DTLSv1_get_timeout/DTLSv1_handle_timeout on server for each connection
On Jan 25, 2012, at 2:21 PM, Manish Yadav wrote: Hi Michael, thanks for quick response. i had one more question, is it possible to do decoupling of ssl object and socket fd to avoid rehandshake? (i am thinking to create socketfd only for active clients, if it is inactive for sometime then close the connection/socket and for inactive clients keep the ssl object cached, whenever inactive clients send data create new fd and associate with old ssl object, similar to http://net-snmp.sourceforge.net/dev/agent/snmpDTLSUDPDomain_8c_source.html). is it possible? If you make sure that you don't send anything locally... Why not close the DTLS connection after some time and let the client do a new connect. You can cache the session and the client can use session resumption. if i look at DTLSv1_listen, i am thinking i can not distinguish between active/inactive client? is it possible based on error value from DTLSv1_listen to tell if i received hello message or invalid message or invalid hello message/wrong cookie. I don't think so. Robin? thanks, manish On Wed, Jan 25, 2012 at 3:24 PM, Michael Tuexen michael.tue...@lurchi.franken.de wrote: On Jan 25, 2012, at 7:08 AM, Manish Yadav wrote: Hi all, could you please confirm if dtls timers are implemented at client side only and not on server side (only client retries/attempts to establish connection) or why they should be implemented on server side also. You need timers on the server side also. However, DTLSv1_get_timeout/DTLSv1_handle_timeout is only necessary if you use select. after looking at : http://crypto.stanford.edu/~nagendra/papers/dtls.pdf i understood that i need to call DTLSv1_get_timeout/DTLSv1_handle_timeout incase of non-blocking socket. but after looking at example available on net dtls_udp_echo2.c, i see only client side take care of this. i feel only client side should try to reconnect, why server should try to resend message to client. Not sure about dtls_udp_echo2.c. You might want to take a look at the examples available at http://sctp.fh-muenster.de/dtls-samples.html please share if you know any example on this. Maybe Robin has more examples... Best regards Michael thanks, manish __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: OpenSSL 1.0.1 on OpenServer 5.0.7
Open crypto/modes/gcm128.c in text editor, locate line that
has '/* check MMX bit */' comment and replace '123' with '125'.
Changing crypto/modes/gcm128.c gets test to pass.
Another test to perform is following. Revert back to '123', then open
crypto/modes/asm/ghash-x86.pl in text editor and locate line that reads
'if (0) {{ # May MMX version is kept for reference Replace '(0)'
with '(!$sse2)'...
[ reverting crypto/modes/gcm128.c ]
This change to crypto/modes/asm/ghash-x86.pl works also.
http://cvs.openssl.org/chngview?cn=22074.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
Re: OpenSSL validation question
Hi, Does the FIPS module certification is missed if the fipscanister module is compiled to a configuration (architecture, compiler version etc) different from those listed on OpenSSL security policy? Our concern is if a change to something on the build tools like compiler version or architecture can invalidate the certification. That's a very general question, so I can't give a specific answer. It depends. A rough rule of thumb is that if you create a FIPS module (fipscanister.o) on a formally tested platform (O/S and processor as listed in the Security Policy), and if that binary file when copied as-is to another platform executes successfully, then you are *generally* justified in claiming it as validated. The Implementation Guidance document (http://csrc.nist.gov/groups/STM/cmvp/documents/fips140-2/FIPS1402IG.pdf) is a more official discussion. See in particular section G.5. -Steve M. -- Steve Marquess OpenSSL Software Foundation, Inc. 1829 Mount Ephraim Road Adamstown, MD 21710 USA +1 877 673 6775 s/b +1 301 874 2571 direct marqu...@opensslfoundation.com
Re: OpenSSL validation question
On Wed, Jan 25, 2012 at 06:35:58PM -0500, Steve Marquess wrote: A rough rule of thumb is that if you create a FIPS module (fipscanister.o) on a formally tested platform (O/S and processor as listed in the Security Policy), and if that binary file when copied Does the Security Policy list the compiler? When I did this, years ago, I think we did not have to specify the compiler even when we applied for our algorithm certificates. That seemed very, very wrong, since one of the changes most likely to break a highly optimized implementation of an algorithm is a change to the compiler! __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
