06-25-2003 05:25 AM - edited 02-20-2020 10:49 PM
We have some developers that have an application that they say needs to have the TCP timeout set to 4 hours (talking to some mainframe somewhere)and I need some ammunition/arguments that will show them how this is not a secure thing to do.
06-25-2003 08:07 AM
Hi,
I don't think that this is a real security problem for TCP connections because TCP headers include the sequence numbers of the packets.
It is not a good idea to do this for UDP connections since there are no sequence numbers inside the UCP header.
Regards,
Tom
06-25-2003 08:19 AM
It's not really a security issue. However, if the firewall handles alot of sessions, it may significantly impact memory consumption and slightly on the CPU load.
What type of client and server? What protocol is used for connectivity?
*nix hosts can be configured to send keepalives. The client side app can be configured/written to send keepalives. This will prevent the timeouts on the firewall.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide