Debian bug report logs -
#1739, boring messages
Message sent to debian-devel@pixar.com:
Subject: Bug#1739: syslog is uncommented in /etc/services by default
Reply-To: Ian Jackson <ian@chiark.chu.cam.ac.uk>, debian-bugs@pixar.com
Resent-From: Ian Jackson <ian@chiark.chu.cam.ac.uk>
Resent-To: debian-devel@pixar.com
Resent-Date: Mon, 23 Oct 1995 13:03:02 GMT
Resent-Message-ID: <debian-bugs-handler.1739.B10231256570@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: netbase
X-Debian-PR-Keywords:
Received: via spool for debian-bugs; Mon, 23 Oct 1995 13:03:02 GMT
Received: with rfc822 via encapsulated-mail; Mon, 23 Oct 1995 12:56:55 GMT
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t7MPW-000Bz5C; Mon, 23 Oct 95 05:55 PDT
Received: from artemis.chu.cam.ac.uk by pixar.com with SMTP id AA22404
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Mon, 23 Oct 1995 05:54:54 -0700
Received: from chiark.chu.cam.ac.uk by artemis.chu.cam.ac.uk with smtp
(Smail3.1.29.1 #33) id m0t7MOz-0007uaC; Mon, 23 Oct 95 12:54 GMT
Received: by chiark.chu.cam.ac.uk
id m0t7MOr-0002b7C
(Debian /\oo/\ Smail3.1.29.1 #29.33); Mon, 23 Oct 95 12:54 GMT
Message-Id: <m0t7MOr-0002b7C@chiark.chu.cam.ac.uk>
Date: Mon, 23 Oct 95 12:54 GMT
From: Ian Jackson <ian@chiark.chu.cam.ac.uk>
To: Debian bugs submission address <debian-bugs@pixar.com>
Package: netbase
Version: 1.19-1
I've now tracked down what it is that keeps reenabling my syslog's
network listening: the netbase package's /etc/services file has syslog
uncommented.
Commenting out the /etc/services entry is of course a very nasty way
of nixing syslog's usually-undesirable network listening feature, but
we should leave things that way until the syslog package is improved.
Ian.
Message sent:
From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Ian Jackson <ian@chiark.chu.cam.ac.uk>
Subject: Bug#1739: Acknowledgement (was: syslog is uncommented in /etc/services by default)
In-Reply-To: <m0t7MOr-0002b7C@chiark.chu.cam.ac.uk>
References: <m0t7MOr-0002b7C@chiark.chu.cam.ac.uk>
Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received. It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.
If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#1739" or "Re: Bug#1739" so that
we can identify it as relating to the same problem.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, debian-bugs)
Message sent to debian-devel@pixar.com:
Subject: Bug#1739: syslog is uncommented in /etc/services by default
Reply-To: Ian Jackson <ian@chiark.chu.cam.ac.uk>, debian-bugs@pixar.com
Resent-From: Ian Jackson <ian@chiark.chu.cam.ac.uk>
Resent-To: debian-devel@pixar.com
Resent-Date: Mon, 23 Oct 1995 22:48:02 GMT
Resent-Message-ID: <debian-bugs-handler.1739.B10232236460@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: netbase
X-Debian-PR-Keywords:
Received: via spool for debian-bugs; Mon, 23 Oct 1995 22:48:02 GMT
Received: with rfc822 via encapsulated-mail; Mon, 23 Oct 1995 22:36:44 GMT
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t7VNB-000C0GC; Mon, 23 Oct 95 15:29 PDT
Received: from artemis.chu.cam.ac.uk by pixar.com with SMTP id AA24072
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Mon, 23 Oct 1995 15:29:11 -0700
Received: from chiark.chu.cam.ac.uk by artemis.chu.cam.ac.uk with smtp
(Smail3.1.29.1 #33) id m0t7VN3-0007uaC; Mon, 23 Oct 95 22:29 GMT
Received: by chiark.chu.cam.ac.uk
id m0t7VMm-0002b4C
(Debian /\oo/\ Smail3.1.29.1 #29.33); Mon, 23 Oct 95 22:29 GMT
Message-Id: <m0t7VMm-0002b4C@chiark.chu.cam.ac.uk>
Date: Mon, 23 Oct 95 22:29 GMT
From: Ian Jackson <ian@chiark.chu.cam.ac.uk>
To: Debian bugs submission address <debian-bugs@pixar.com>
In-Reply-To: <9510231401.AA01409@server.et-inf.fho-emden.de>
References: <m0t7MOr-0002b7C@chiark.chu.cam.ac.uk>
<9510231401.AA01409@server.et-inf.fho-emden.de>
Peter Tobias asks me in email:
> Ian Jackson wrote:
> > Package: netbase
> > Version: 1.19-1
> >
> > I've now tracked down what it is that keeps reenabling my syslog's
> > network listening: the netbase package's /etc/services file has syslog
> > uncommented.
> >
> > Commenting out the /etc/services entry is of course a very nasty way
> > of nixing syslog's usually-undesirable network listening feature, but
> > we should leave things that way until the syslog package is improved.
>
> Why do you think it's a bug in the netbase package? This feature (and
> the syslog entry in /etc/services) is enabled on the systems that
> support it (at least on those I have access to). And I see no problem
> having it enabled by default. Anyway, it shouldn't be "fixed" by
> commenting out the syslog service in /etc/services. It should be fixed
> in the syslogd package.
It's a security problem, because it allows any machine anywhere on the
Internet to make your maching completely unusable very easily. syslog
writes its logfiles to disk synchronously, and the logs can fill up
the disk too.
Most people do not need or want the remote logging feature.
It should therefore be disabled by default.
I agree that it shouldn't be fixed by commenting out the syslog entry
in /etc/services, but that seems to be the only avenue open at the
moment. Please keep the entry commented out until the syslog package
is fixed.
Ian.
Message sent:
From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Ian Jackson <ian@chiark.chu.cam.ac.uk>
Subject: Bug#1739: Info received (was Bug#1739: syslog is uncommented in /etc/services by default)
In-Reply-To: <m0t7VMm-0002b4C@chiark.chu.cam.ac.uk>
References: <m0t7VMm-0002b4C@chiark.chu.cam.ac.uk>
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developers to
accompany the original report.
If you wish to continue to submit further information on your problem,
please do the same thing again: send it to debian-bugs@pixar.com, ensuring
that the Subject line starts with "Bug#1739" or "Re: Bug#1739" so that
we can identify it as relating to the same problem.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, debian-bugs)
Message sent:
From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: tobias@et-inf.fho-emden.de
In-Reply-To: <9510250045.AA25726@server.et-inf.fho-emden.de>
References: <9510250045.AA25726@server.et-inf.fho-emden.de> <m0t7MOr-0002b7C@chiark.chu.cam.ac.uk>
Subject: Bug#1739: marked as done (was: syslog is uncommented in /etc/services by default)
Your message dated Wed, 25 Oct 1995 01:45:06 +0100 (MET)
with message-id <9510250045.AA25726@server.et-inf.fho-emden.de>
and subject line Bug#1739: syslog is uncommented in /etc/services by default
has caused the attached bug report to be marked as done.
It is your now responsibility to ensure that the bug report is dealt
with.
(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Ian Jackson
(maintainer, debian-bugs)
Received: with rfc822 via encapsulated-mail; Mon, 23 Oct 1995 12:56:55 GMT
From chiark.chu.cam.ac.uk!ian Mon Oct 23 05:55:26 1995
Return-Path: <ian@chiark.chu.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t7MPW-000Bz5C; Mon, 23 Oct 95 05:55 PDT
Received: from artemis.chu.cam.ac.uk by pixar.com with SMTP id AA22404
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Mon, 23 Oct 1995 05:54:54 -0700
Received: from chiark.chu.cam.ac.uk by artemis.chu.cam.ac.uk with smtp
(Smail3.1.29.1 #33) id m0t7MOz-0007uaC; Mon, 23 Oct 95 12:54 GMT
Received: by chiark.chu.cam.ac.uk
id m0t7MOr-0002b7C
(Debian /\oo/\ Smail3.1.29.1 #29.33); Mon, 23 Oct 95 12:54 GMT
Message-Id: <m0t7MOr-0002b7C@chiark.chu.cam.ac.uk>
Date: Mon, 23 Oct 95 12:54 GMT
From: Ian Jackson <ian@chiark.chu.cam.ac.uk>
To: Debian bugs submission address <debian-bugs@pixar.com>
Subject: syslog is uncommented in /etc/services by default
Package: netbase
Version: 1.19-1
I've now tracked down what it is that keeps reenabling my syslog's
network listening: the netbase package's /etc/services file has syslog
uncommented.
Commenting out the /etc/services entry is of course a very nasty way
of nixing syslog's usually-undesirable network listening feature, but
we should leave things that way until the syslog package is improved.
Ian.
Message sent:
From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Ian Jackson <ian@chiark.chu.cam.ac.uk>
Subject: Bug#1739 acknowledged by developer (was: syslog is uncommented in /etc/services by default)
References: <9510250045.AA25726@server.et-inf.fho-emden.de> <m0t7MOr-0002b7C@chiark.chu.cam.ac.uk>
In-Reply-To: <m0t7MOr-0002b7C@chiark.chu.cam.ac.uk>
This is an automatic notification regarding your bug report.
Responsibility for it has been taken by one of the developers, namely
"Peter Tobias" <tobias@server.et-inf.fho-emden.de> (reply to tobias@et-inf.fho-emden.de).
You should be hearing from them with a substantive response shortly, if
you have not already done so. If not, please contact them directly,
or email debian-bugs@pixar.com or myself.
Ian Jackson
(maintainer, debian-bugs)
Message sent to debian-devel@pixar.com:
Subject: Bug#1739: syslog is uncommented in /etc/services by default
Reply-To: joey@finlandia.Infodrom.North.DE (Martin Schulze), debian-bugs@pixar.com
Resent-From: joey@finlandia.Infodrom.North.DE (Martin Schulze)
Resent-To: debian-devel@pixar.com
Resent-Date: Wed, 25 Oct 1995 06:03:02 GMT
Resent-Message-ID: <debian-bugs-handler.1739.B10250549050@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: netbase
X-Debian-PR-Keywords:
Received: via spool for debian-bugs; Wed, 25 Oct 1995 06:03:02 GMT
Received: with rfc822 via encapsulated-mail; Wed, 25 Oct 1995 05:49:05 GMT
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t7ygy-0005MAC; Tue, 24 Oct 95 22:48 PDT
Received: from gimli.Informatik.Uni-Oldenburg.DE by pixar.com with SMTP id AA00407
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Tue, 24 Oct 1995 22:47:34 -0700
Received: by gimli.Informatik.Uni-Oldenburg.DE (Smail3.1.22.1)
id <m0t7yKE-00002VC>; Wed, 25 Oct 95 06:24 CET
Received: by olis.north.de (/\==/\ Smail3.1.28.1 #28.13)
id <m0t7y8p-0005RPC@olis.north.de>; Wed, 25 Oct 95 06:12 MEZ
Received: at Infodrom Oldenburg (/\##/\ Smail3.1.29.1 #29.10 Joey)
by finlandia.Infodrom.North.DE from joey (Martin Schulze)
id m0t7rVu-000KDxC; Tue, 24 Oct 95 23:08 MET
Message-Id: <m0t7rVu-000KDxC@finlandia.Infodrom.North.DE>
From: joey@finlandia.Infodrom.North.DE (Martin Schulze)
To: ian@chiark.chu.cam.ac.uk
Date: Tue, 24 Oct 1995 23:08:05 +0100 (MET)
Cc: debian-bugs@Pixar.com
In-Reply-To: <m0t7VMm-0002b4C@chiark.chu.cam.ac.uk> from "Ian Jackson" at Oct 23, 95 10:29:00 pm
X-Href: http://home.pages.de/~joey/
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 2343
Hallo Ian Jackson!
}Peter Tobias asks me in email:
}> Ian Jackson wrote:
}> > Package: netbase
}> > Version: 1.19-1
}> >
}> > I've now tracked down what it is that keeps reenabling my syslog's
}> > network listening: the netbase package's /etc/services file has syslog
}> > uncommented.
}> >
}> > Commenting out the /etc/services entry is of course a very nasty way
}> > of nixing syslog's usually-undesirable network listening feature, but
}> > we should leave things that way until the syslog package is improved.
}>
}> Why do you think it's a bug in the netbase package? This feature (and
}> the syslog entry in /etc/services) is enabled on the systems that
}> support it (at least on those I have access to). And I see no problem
}> having it enabled by default. Anyway, it shouldn't be "fixed" by
}> commenting out the syslog service in /etc/services. It should be fixed
}> in the syslogd package.
}
}It's a security problem, because it allows any machine anywhere on the
}Internet to make your maching completely unusable very easily. syslog
}writes its logfiles to disk synchronously, and the logs can fill up
}the disk too.
Yes. We (the sysklogd developers) found this problem long time
ago. Future releases will have a switch (-r) that has to be set if any
message should be received from remote. Otherwise the syslogd won't
open the socket for reading. This to look in the future...
}Most people do not need or want the remote logging feature.
That's correct.
}It should therefore be disabled by default.
dito
}I agree that it shouldn't be fixed by commenting out the syslog entry
}in /etc/services, but that seems to be the only avenue open at the
}moment. Please keep the entry commented out until the syslog package
}is fixed.
I have one more comment to make. What do you think about an
explanatery text when installing the sysklogd package. This could be
done in my postinst script (if I'm not mistaken).
Regards,
Joey
--
/ Martin Schulze * joey@infodrom.north.de * 26129 Oldenburg /
/ +49-441-777884 * Login&Passwd: nuucp * Index: ~/ls-lR.gz /
/ =?iso-8859-1?q?kristian_k=f6hntopp@cyberbox.north.de /
/ verursacht durch kaputte Gatesoftware auf der CyberBox /
----------------------------------------------------------------
30.10.95: Oldenburger Linux-Stammtisch, ab 20h im DaCapo
Message sent:
From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: joey@finlandia.Infodrom.North.DE (Martin Schulze)
Subject: Bug#1739: Info received (was Bug#1739: syslog is uncommented in /etc/services by default)
In-Reply-To: <m0t7rVu-000KDxC@finlandia.Infodrom.North.DE>
References: <m0t7rVu-000KDxC@finlandia.Infodrom.North.DE>
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developers to
accompany the original report.
If you wish to continue to submit further information on your problem,
please do the same thing again: send it to debian-bugs@pixar.com, ensuring
that the Subject line starts with "Bug#1739" or "Re: Bug#1739" so that
we can identify it as relating to the same problem.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, debian-bugs)
Ian Jackson /
iwj10@thor.cam.ac.uk,
with the debian-bugs tracking mechanism