Someone in your company is responsible for trade and/or export regulations. Find out
who that is and contact them for guidance. While regulations have become more liberal
in some cases, they are always changing so it's good to get up-to-date advice from
someone whose job it is to follow the regu
Eric is correct. It's the responsibility of the application to control timeouts on the
socket.
Be aware, though, that some applications ported from UNIX make the assumption that a
SIGALRM will cause outstanding recv() calls to complete. This is not the case on other
platforms such as OpenVMS an
Jeffrey Altman wrote:
>Since absolutely no one that is experiencing this problem
>has looked at a suffering process in a debugger it is
>impossible to know what is the cause of the problem. As
>far as I can tell all the theories that have been put
>forward as to what this is or is not are simply b
>>This is a classic denial-of-service which is impossible to defend against at
>>the application level.
>
> Nonsense. It's a result of a design flaw (process per connection, with the
>process assigned before the connection is validated along with a limited
>number of processes) in the appl
