Re: [ncat] Behavior on non SCTP-aware systems

[David Fifield <david () bamsoftware com>]

On Thu, Jul 12, 2012 at 07:17:57PM +0200, Henri Doreau wrote:
> Hi,
>
> for some reasons, it looks like my system doesn't support SCTP.
> socket(PF_INET, SOCK_STREAM, IPPROTO_SCTP) always fails with
> EPROTONOSUPPORT. I've noticed the following inconsistent behavior in
> ncat:
>
> The connect mode fails as I would expect it to do:
> $ ncat --sctp localhost
> Socket troubles: Protocol not supported
> Ncat: Protocol not supported.
>
> but when using the listening mode I get:
> $ ncat --sctp -l
> setsockopt: Bad file descriptor
>
> I've committed a little patch in r29194 to make ncat exit more
> consistently in listening mode. I'm wondering whether it would be
> doable/interesting to disable SCTP (unless explicitly required) on
> systems that don't support SCTP. Any thought?

I don't think we should disable it at compile time. You could have a
static binary that could be copied from a system without SCTP to one
with.

Thanks for finding the output inconsistency.

David Fifield
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/