Michael,
i am curious, how would we detect DOS attack on server if someone sends too
many such packets? dtls server would keep silently dropping them, will it
report any error/status?
thanks,
manish
On Thu, Mar 15, 2012 at 6:16 PM, Michael Tuexen
michael.tue...@lurchi.franken.de wrote:
On
On Mar 16, 2012, at 8:31 AM, Manish Yadav wrote:
Michael,
i am curious, how would we detect DOS attack on server if someone sends too
many such packets? dtls server would keep silently dropping them, will it
report any error/status?
Just dropping, no report.
Best regards
Michael
Hi Michael, Robin,
i had a basic doubt, suppose i have dtls client (ip address:cip, source
port: cport) and dtls server (ip address: dip, destination port: dport).
both are connected. then client goes down/crashes without calling
ssl_shutdown, so server still has the client context information.
On Mar 15, 2012, at 1:08 PM, Manish Yadav wrote:
Hi Michael, Robin,
i had a basic doubt, suppose i have dtls client (ip address:cip, source port:
cport) and dtls server (ip address: dip, destination port: dport). both are
connected. then client goes down/crashes without calling
Hi Michael,
thanks for info.
thanks,
manish
On Thu, Mar 15, 2012 at 6:16 PM, Michael Tuexen
michael.tue...@lurchi.franken.de wrote:
On Mar 15, 2012, at 1:08 PM, Manish Yadav wrote:
Hi Michael, Robin,
i had a basic doubt, suppose i have dtls client (ip address:cip, source
port: cport)
Hi Michael, Robin,
thanks for input. i was thinking if i am not implementing dtls heartbeat in
that scenario, how could client detect if server is still getting the
messages (assuming the server deleted inactive session after sometime or
server got reloaded), is there any mechanism that could
On Feb 5, 2012, at 10:25 AM, Manish Yadav wrote:
Hi Michael, Robin,
thanks for input. i was thinking if i am not implementing dtls heartbeat in
that scenario, how could client detect if server is still getting the
messages (assuming the server deleted inactive session after sometime or
On Jan 25, 2012, at 5:16 PM, Michael Tuexen wrote:
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
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
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
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
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.
after looking at : http://crypto.stanford.edu/~nagendra/papers/dtls.pdf
i
12 matches
Mail list logo
