Skip to contentSkip to conversation

Announce: modutils 2.3.21 is available

DISCUSSION Keith Owens 5 participants 6 messages Nov 22, 2000

lore
Share & tools
lore
#0 lore raw

This is the "never release a security fix in a hurry" release. The security fixes in modutils 2.3.20 had some side effects on some config files. Linus knocked back environment variable MOD_SAFEMODE, instead the kernel propagates the real uid that caused modprobe to be invoked.

ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/modutils/v2.3

patch-modutils-2.3.21.bz2       Patch from modutils 2.3.20 to 2.3.21
modutils-2.3.21.tar.bz2         Source tarball, includes RPM spec file
modutils-2.3.21-1.src.rpm       As above, in SRPM format
modutils-2.3.21-1.i386.rpm      Compiled with egcs-2.91.66, glibc 2.1.2
modutils-2.3.21-1.sparc.rpm     Compiled for combined sparc 32/64

Changelog extract

* Remove compile warnings in xstrcat.
* snprintf cleanups.
* Set safemode when uid != euid.
* Strip quotes from shell responses.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#1 lore raw
Quoted 13 lines · Keith Owens

This is the "never release a security fix in a hurry" release. The security fixes in modutils 2.3.20 had some side effects on some config files. Linus knocked back environment variable MOD_SAFEMODE, instead the kernel propagates the real uid that caused modprobe to be invoked.

ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/modutils/v2.3

patch-modutils-2.3.21.bz2       Patch from modutils 2.3.20 to 2.3.21
modutils-2.3.21.tar.bz2         Source tarball, includes RPM spec file
modutils-2.3.21-1.src.rpm       As above, in SRPM format
modutils-2.3.21-1.i386.rpm      Compiled with egcs-2.91.66, glibc 2.1.2
modutils-2.3.21-1.sparc.rpm     Compiled for combined sparc 32/64
Quoted 6 lines

Changelog extract

* Remove compile warnings in xstrcat.
* snprintf cleanups.
* Set safemode when uid != euid.
* Strip quotes from shell responses.

+ add RedHat ism's with a --rhc (red hat compatible) -i -m (-F)

RedHat kind of is the standard in the commercial world in the US.

:-)

Jeff

Quoted 5 lines

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#2 lore raw
Quoted 3 lines · Jeff V. Merkey

+ add RedHat ism's with a --rhc (red hat compatible) -i -m (-F)

RedHat kind of is the standard in the commercial world in the US.

Regardless of the bogus nature of this statement, boss. GNU/OS packages are to be modified locally and a generic form that does not have flavor or spin is what maintainers release.

Regards,

Andre Hedrick
CTO Timpanogas Research Group
EVP Linux Development, TRG
Linux ATA Development

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#3 lore raw
In reply to Jeff V. Merkey
Quoted 11 lines · Andre Hedrick
Quoted 3 lines · Jeff V. Merkey

+ add RedHat ism's with a --rhc (red hat compatible) -i -m (-F)

RedHat kind of is the standard in the commercial world in the US.

Regardless of the bogus nature of this statement, boss. GNU/OS packages are to be modified locally and a generic form that does not have flavor or spin is what maintainers release.

Regards,

The -m option is a good idea. Strange since most of the commercial releases implement these additions. I just hope Keith has a good sense of humor.

:-)

Jeff

Quoted 5 lines

Andre Hedrick
CTO Timpanogas Research Group
EVP Linux Development, TRG
Linux ATA Development

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/

#4 lore raw
In reply to Keith Owens
Quoted 7 lines
Quoted 4 lines

* Remove compile warnings in xstrcat.
* snprintf cleanups.
* Set safemode when uid != euid.
* Strip quotes from shell responses.

+ add RedHat ism's with a --rhc (red hat compatible) -i -m (-F)

RedHat kind of is the standard in the commercial world in the US.

I don't think it's necessary or appropriate to taylor things for a particular distribution even if it may unfortunately be 'standard' for some people.

-d

begin:vcard
n:Ford;David
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:[email protected]
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard

#5 lore raw
Quoted 10 lines · David Ford
Quoted 7 lines
Quoted 4 lines

* Remove compile warnings in xstrcat.
* snprintf cleanups.
* Set safemode when uid != euid.
* Strip quotes from shell responses.

+ add RedHat ism's with a --rhc (red hat compatible) -i -m (-F)

RedHat kind of is the standard in the commercial world in the US.

I don't think it's necessary or appropriate to taylor things for a particular distribution even if it may unfortunately be 'standard' for some people.

Zackerly. My system will certainly look like a RedHat system; it's based on one. However (particularly with regards to kernels and modules), I can almost guarantee it won't react like a RedHat system.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/