linux-kernel - Re: [RFC PATCH] netconsole.txt: "nc" needs "-p" to specify the listening port

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120727131535.GA3485@x1.osrc.amd.com>
Date:	Fri, 27 Jul 2012 15:15:36 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Dirk Gouders <gouders@...bocholt.fh-gelsenkirchen.de>
Cc:	Cong Wang <xiyou.wangcong@...il.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] netconsole.txt: "nc" needs "-p" to specify the
 listening port

On Fri, Jul 27, 2012 at 11:24:53AM +0200, Dirk Gouders wrote:
> Cong Wang <xiyou.wangcong@...il.com> writes:
> 
> > On Fri, Jul 27, 2012 at 2:35 PM, Dirk Gouders
> > <gouders@...bocholt.fh-gelsenkirchen.de> wrote:
> >> Hi Jesse,
> >>
> >> I would like to ask you to check if the documentation of "nc" in
> >> netconsole.txt is still correct.  I tried two different netcat packages
> >> and both require "-p" to specify the listening port.  I am wondering if
> >> that changed after the use of "nc" has been documented.
> >
> > On Fedora 16, `nc -u -l <port number>` works fine.
> 
> Thanks for checking that.
> 
> If the information I found is correct, Fedora uses OpenBSD's nc
> codebase.  The two netcat packages I tested on a Gentoo system differ in
> requiring the -p switch for the port specification.

So say exactly that in the doc: that the *BSD's version of nc doesn't
need the port number specified with '-p' and you're covered.

-- 
Regards/Gruss,
Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/