Bonjour à tous,
J'utilise NIS 3.9-6 sur une woody (noyau 2.4.18).
J'aimerait savoir comment faire pour que les gid 1000 soient
propagés et non pas ceux 1000.
Le problème est survenu suite à une mise à jour avec passage de
patate à woody.
Merci d'avance à celui ou ceux qui me répondront.
Hi All!
Source and an i386 .deb are now up on:
http://people.debian.org/~grantma
MD5sums:
$ md5sum apache_1.3.24-3.0.anathoth.1*
2694e435fcc5a8197d4942d38a651b43 apache_1.3.24-3.0.anathoth.1.diff.gz
b84b0f106079ab7f66f40d135f5ed3f9 apache_1.3.24-3.0.anathoth.1.dsc
Hallo!
Sprich Englisch, Mann!
On Thursday, 2002-06-20 at 09:28:11 +0200, Sebastien Picard wrote:
Bonjour à tous,
J'utilise NIS 3.9-6 sur une woody (noyau 2.4.18).
J'aimerait savoir comment faire pour que les gid 1000 soient
propagés et non pas ceux 1000.
Le problème est survenu
On Wed, 2002-06-19 at 06:57, René Seindal wrote:
If you use 32 bit machines you are 'only' vulnerable to a DoS attack,
not a real compromise of your servers.
Apache version 1.3.24 is vulnerable. The later version 1.3.26 is a
security fix to this issue and it would seem it shall be available
On Thu, 2002-06-20 at 08:28, Sebastien Picard wrote:
Hi all,
I'm using NIS 3.9-6 on woody (kernel 2.4.18).
I'd like to know how to make the gids 1000 propagate, and not those
1000.
The problem appeared after an update with an upgrade from potato to
woody.
Thank you in advance to
I'm proud to announce a slight, but significant change, in the published
security announcements (DSA) availables at security.debian.org. Starting
tomorrow (as you can appreciate from Apache's DSA at
http://www.debian.org/security/2002/dsa-131). Published DSAs now include
cross references to
Matthew Grant [EMAIL PROTECTED] writes:
Here is a rehashed version of the patch cert_vucert944335 chunk fix
patch used in apache_1.3.9-14.1 for potato which works for apache in
woody and sid.
The German publish Heise claims that this patch does not fix the
vulnerability, see:
Hello Matthew,
I'm a little confused as to why you're cc:ing me on these messages?
Steve Langasek
postmodern programmer
On Thu, Jun 20, 2002 at 08:20:56PM +1200, Matthew Grant wrote:
Source and an i386 .deb are now up on:
http://people.debian.org/~grantma
MD5sums:
$ md5sum
This should probably have gone to the lists and the poster, not me.
On Thu, 2002-06-20 at 15:02, Bertrand Orvoine wrote:
see in /var/yp/Makefile :
# We do not put password entries with lower UIDs (the root and system
# entries) in the NIS password database, for security. MINUID is the
#
Thanks and excuse me for using french
Chris Boyle wrote:
This should probably have gone to the lists and the poster, not me.On Thu, 2002-06-20 at 15:02, Bertrand Orvoine wrote:
see in /var/yp/Makefile :# We do not put password entries with lower UIDs (the root and system# entries) in
The German publish Heise claims that this patch does not fix the
vulnerability, see:
http://www.heise.de/newsticker/data/pab-20.06.02-000/
But I hope this is an editorial error. :-/
Do you means the one-line patch from ISS ?
That patch don't work.
The one in apache offical 1.3.26
Hi there
I got a little question, a bit silly perhaps. When will there be any
packages of Apache 1.3.26 or a backported patch for 1.3.24 for woody? Will
it be in the next time or would it make sense to upgrade by hand, say by
compiling one's own binaries. Well yes I know, that there is some
On Thu, 2002-06-20 at 17:40, Marcel Weber wrote:
Hi there
I got a little question, a bit silly perhaps. When will there be any
packages of Apache 1.3.26 or a backported patch for 1.3.24 for woody? Will
it be in the next time or would it make sense to upgrade by hand, say by
compiling one's
On Thu, 20 Jun 2002, Marcel Weber wrote:
Hi there
I got a little question, a bit silly perhaps. When will there be any
packages of Apache 1.3.26 or a backported patch for 1.3.24 for woody? Will
it be in the next time or would it make sense to upgrade by hand, say by
compiling one's own
As Paul Hosking pointed out today [1] a debian package
for apache 1.3.26 might be available soon for everybody to download.
In fact the bug [2] is already closed and packages might have been
uploaded yesterday.
Given the importance of the problem I thought I'd ask
how long it will approximately
SDiZ \(UHome\) [EMAIL PROTECTED] writes:
The German publish Heise claims that this patch does not fix the
vulnerability, see:
http://www.heise.de/newsticker/data/pab-20.06.02-000/
But I hope this is an editorial error. :-/
Do you means the one-line patch from ISS ?
That patch don't
NEW PRODUCT ANNOUNCEMENT
From: OUTSOURCE ENG. MFG. INC.
Sir/Madam;
This note is to inform you of new watchdog board technology for maintaining
continuous unattended operation of PC/Servers etc. that we have released for
distribution.
We are proud to announce Watchdog Control Center
On Thu, 2002-06-20 at 17:40, Marcel Weber wrote:
Hi there
I got a little question, a bit silly perhaps. When will there be any
packages of Apache 1.3.26 or a backported patch for 1.3.24 for woody?...
As the list archive from 7 hrs and 20 mins ago says - the packages are
out. Look above.
Hi
Quoting Ren? Seindal ([EMAIL PROTECTED]):
I don't know about apache-ssl
libapache-mod-ssl is in incoming.
Greets,
Robert
--
( o Linux Generation o )
///\finger [EMAIL PROTECTED] for my GnuPG/PGP key./\\\
\V_/
On Don, 20 Jun 2002, Bernhard Reiter wrote:
Hello,
Given the importance of the problem I thought I'd ask
how long it will approximately take until these packages will be
available from the public ftp servers?
Yesterday it was available from http://incoming.debian.org/
and moved today to the
Cool, thank you all!
Marcel
-Ursprungliche Nachricht-
Von: Vincent Renardias [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 20. Juni 2002 20:51
An: Marcel Weber
Cc: debian-testing@lists.debian.org; debian-security@lists.debian.org
Betreff: Re: DSA 131: Apache Vulnerability
On Thu, 20
Hate to beat a dead horse, but
deb http://http.us.debian.org/debian potato main contrib non-free
deb http://http.us.debian.org/debian dists/potato-proposed-updates/
deb http://non-us.debian.org/debian-non-US potato/non-US main contrib
non-free
deb http://non-us.debian.org/debian-security
Mike Dresser [EMAIL PROTECTED] writes:
Hate to beat a dead horse, but
deb http://http.us.debian.org/debian potato main contrib non-free
deb http://http.us.debian.org/debian dists/potato-proposed-updates/
deb http://non-us.debian.org/debian-non-US potato/non-US main contrib
non-free
On Thu, 20 Jun 2002 23:22, Olaf Meeuwissen wrote:
(wait for official release updates) and then just s/potato/stable/g.
Note that non-US is being phased out.
Can you point me to the mail-archive thread that discusses this?(I haven't
been following debian lists for very long).
Cheers
For a truly stable Debian system, drop
deb http://http.us.debian.org/debian dists/potato-proposed-updates/
(wait for official release updates) and then just s/potato/stable/g.
Note that non-US is being phased out.
I've seen way too many packages that take too long to get into stable when
On Fri, 21 Jun 2002 00:36, Olaf Meeuwissen wrote:
Geoff Crompton [EMAIL PROTECTED] writes:
On Thu, 20 Jun 2002 23:22, Olaf Meeuwissen wrote:
(wait for official release updates) and then just s/potato/stable/g.
Note that non-US is being phased out.
Can you point me to the
I have two relative policies:
1. Always use a firewall to filter out everything but what is absolutely
necessary, ie web, email, etc.
2. Always build stuff filtered to the internet from source that way when a
vulnerability is released, you can update it rather quickly, no matter
what the distro
Geoff Crompton [EMAIL PROTECTED] writes:
Oops! I confused the crypto in main issue with non-US being phased
out. Of course, the patented bits will stay in non-US so it will not
disappear in the foreseeable future.
What is the 'cypto in main' issue? (Or better, have you got a URL
on
Mike Dresser [EMAIL PROTECTED] writes:
For a truly stable Debian system, drop
deb http://http.us.debian.org/debian dists/potato-proposed-updates/
(wait for official release updates) and then just s/potato/stable/g.
Note that non-US is being phased out.
I've seen way too many
29 matches
Mail list logo