RE: security on sqlexec port
A port scan will obviously pick them up, if you want to prevent
that then use a firewall and block the port. Sqlexec doesn't
fail with the 'standard' scans
17:08:35 listener-thread: err = -408: Invalid message type received from the sqlexec process.
However how it copes with a really aggressive port
attack I don't know. But if it's an externally facing port
you should be using wrappers etc
Paul Watson #
WF Software Ltd # All answers are
Tel: +44 1436 674729 # pure fantasy
Fax: +44 1436 678693 #
www.wfsoftware.com #
> -----Original Message-----
> From: Michal Hajek [mailto:hajek@nspuh.cz]
> Sent: Monday, October 09, 2000 1:01 PM
> To: informix-list@iiug.org
> Subject: security on sqlexec port
>
>
> Hi,
>
> it seems we will have to rearrange our network topology so that
> server with IDS will be connected to our intranet directly.
> Is it possible to allow connect to sqlexec port only from
> a list of hosts ? Is sqlexec robust against scanning ports or
> any other kind of non-IDS connections ?
>
> Any comments or URLs ?
>
> Thanks,
> Michal
>
>
> --
> --------------------------------------------------------------
> Michal Hajek mailto:hajek@nspuh.cz
> --------------------------------------------------------------
>
**********************************************************************
The contents of this e-mail are confidential to the ordinary user(S) of the
mail address(es) to which it was sent and may be legally privileged.
If you are not the intended recipient, any disclosure, copying, distribution
or use of it, or any part of it, in any form whatsoever, and any actions
taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.
**********************************************************************