Bug 21775

Summary: Add info on port usage to services
Product: Base System Reporter: dann <dann>
Component: miscAssignee: Doug Barton <dougb>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.1-STABLE   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description dann 2000-10-05 21:30:01 UTC 
add usage info to /etc/services.  TCP port 98 is officially tacnews but is 
used by Red Hat Linux's linuxconf tool as well. I've seen a lot of port
scans for this, and thought it would be good to have this noted in
services.

Fix: diff below:
How-To-Repeat: 
N/A
Comment 1 jedgar 2000-10-05 21:44:52 UTC 
On Thu, Oct 05, 2000 at 01:24:21PM -0700, Dann Lunsford wrote:

> >Description:
> 
> add usage info to /etc/services.  TCP port 98 is officially tacnews but is 
> used by Red Hat Linux's linuxconf tool as well. I've seen a lot of port
> scans for this, and thought it would be good to have this noted in
> services.
> 
> -tacnews		 98/tcp	   #TAC News
> +tacnews		 98/tcp	   #TAC News; Red Hat linuxconf

Did IANA officially assign this port to RedHat?  And do we really want to
start adding a bunch of cruft into /etc/services about systems using
unassigned ports?

-- 
Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org
--------------------------------------------------------
FreeBSD: The Power To Serve   -   http://www.FreeBSD.org
Comment 2 dann 2000-10-06 20:45:06 UTC 
On Thu, Oct 05, 2000 at 04:44:52PM -0400, Chris Faulhaber wrote:
> On Thu, Oct 05, 2000 at 01:24:21PM -0700, Dann Lunsford wrote:
> 
> > >Description:
> > 
> > add usage info to /etc/services.  TCP port 98 is officially tacnews but is 
> > used by Red Hat Linux's linuxconf tool as well. I've seen a lot of port
> > scans for this, and thought it would be good to have this noted in
> > services.
> > 
> > -tacnews		 98/tcp	   #TAC News
> > +tacnews		 98/tcp	   #TAC News; Red Hat linuxconf
> 
> Did IANA officially assign this port to RedHat?  And do we really want to
> start adding a bunch of cruft into /etc/services about systems using
> unassigned ports?

I don't think IANA had anything to do with it, actually.  I just
checked the IANA site, and can find no reference to Red Hat stuff in
the port numbers list.  But there are notices in that list about
unoffical port usages, and incorrect and unauthorized port grabs. 
My motive in this PR was to get similar info into our services file, 
at least for some of the more egregions cases.  In this particular 
instance, I spent about an hour searching various places before I found 
that RH had usurped the tacnews port for linuxconf, and that versions  
of linuxconf were remotely exploitable, which explained the scans.  I 
looked in /etc/services first, of course; if a note had been there, 
that hour could have been spent elsewhere :-).

I am mostly in sympathy with the "anti cruft" attitude, but is info
that saves an admin some time or effort really cruft? In any case, 
the final decision is yours as to what gets distributed with the 
system; I can always add my own notes to my copy.  

Thanks for the consideration.


-- 
Dann Lunsford       The only thing necessary for the triumph of evil
dann@greycat.com    is that men of good will do nothing.  --  Cicero
Comment 3 Doug Barton freebsd_committer freebsd_triage 2001-07-28 21:04:02 UTC 
State Changed
From-To: open->analyzed


This seems reasonable. If ISI's site ever comes back on line, 
I'll commit this.
Comment 4 Doug Barton freebsd_committer freebsd_triage 2001-07-28 21:04:02 UTC 
Responsible Changed
From-To: freebsd-bugs->dougb


I'll handle it, and the MFC
Comment 5 Doug Barton freebsd_committer freebsd_triage 2001-08-11 21:43:19 UTC 
State Changed
From-To: analyzed->closed


This was actually MFC'ed 10 days ago, so my work here is done. :)