Release of 2.4.21
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 2 lines · [email protected] (Sebastian D.B. Krause) writes:
I think the best way is to release a 2.4.21 kernel with only the most important fixes (e.g. ptrace, ext3) and no new features.
You can do this on your own. So what?
Releasing an official 2.4.21 with some fixes (and no new features) is just a PR issue. I've already seen people comparing the alleged IIS bug (or this new IE hole) and the ptrace() bug...
Quoted 3 lines · Florian Weimer
Releasing an official 2.4.21 with some fixes (and no new features) is just a PR issue. I've already seen people comparing the alleged IIS bug (or this new IE hole) and the
ptrace()bug...
Comparing, how? There is no comparison.
The ptrace bug is only one of several local root holes. IIS would imply a remote vulnerability, something _far_ more serious.
This specific ptrace hole is closed, yay. Now what about the other 10,001 that still exist? People are blowing this ptrace bug WAY
out of proportion. The only reason why it demands a modicum of
vendor responsibility is that a-holes are making easy-to-use exploits available for the script kiddies.
In my more cynical moods, I wish bugtraq'ers would start posting exploits to all the races in GNU coreutils (cp/mv/rm/...). Assuming such actions would (finally) lead to bug fixes.... maybe then I will start taking local root holes a bit more seriously. I will no more than hint about this in public, but will respond privately with details (if I know you).
Jeff
Followup to: <[email protected]> By author: Jeff Garzik <[email protected]> In newsgroup: linux.dev.kernel
Quoted 4 lines
The ptrace bug is only one of several local root holes. IIS would imply a remote vulnerability, something _far_ more serious.
Don't forget: local root exploit + remote non-root exploit -> remote root exploit.
-hpa
Signature · 3 lines
<[email protected]> at work, <[email protected]> in private! "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
Quoted 6 lines · Jeff Garzik
The ptrace bug is only one of several local root holes. IIS would imply a remote vulnerability, something _far_ more serious.
This specific ptrace hole is closed, yay. Now what about the other 10,001 that still exist? People are blowing this ptrace bug WAY out of proportion.
That may be true, but inspite of that there is another important and dangerous bug in 2.4.20 (the ext3 thing) that IMHO is enough reason to release a new kernel.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 4 lines · Sebastian D.B. Krause
That may be true, but inspite of that there is another important and dangerous bug in 2.4.20 (the ext3 thing) that IMHO is enough reason to release a new kernel.
Btw, what ext3 patches are these exactly?
- From subdir 00-merged/ at
http://people.redhat.com/sct/patches/ext3-2.4/dev-20030314/
More/other patches? There seem to be some (all?) of those mentioned in the .21-pre changelog but can someone please cleary state what ext3 patches should be applied?
- --
Oliver Feiler <kiza@(kcore.de|lionking.org|gmx(pro).net)>
http://kiza.kcore.de/ <-- homepage
PGP-key --> /pgpkey.shtml
http://kiza.kcore.de/journal/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+evI+OpifZVYdT9IRAuksAJ45QBi9gPXrKRHrPGgDlRmanlSmNgCguKFL v5PrWhB/49KKgeE/kvwxF1A=
=A3QG
-----END PGP SIGNATURE-----
Quoted 2 lines · On Thu, 20 Mar 2003 16:03:05 -0500 Jeff Garzik <[email protected]> wrote:
10,001 that still exist? People are blowing this ptrace bug WAY
out of proportion. The only reason why it demands a modicum of
Indeed, everybody i know is recompiling and rebooting; although they're just plain linux where they're the one users and remote login isn't allowed.....
Quoted 9 lines · * Jeff Garzik ([email protected]) wrote:
The ptrace bug is only one of several local root holes. IIS would imply a remote vulnerability, something _far_ more serious.
This specific ptrace hole is closed, yay. Now what about the other 10,001 that still exist? People are blowing this ptrace bug WAY
out of proportion. The only reason why it demands a modicum of
vendor responsibility is that a-holes are making easy-to-use exploits available for the script kiddies.
I know it's already been said, but IMHO it needs to be underscored. Local root holes are just a simple non-root remote exploit away from being remotely exploitable root holes. Both are often considered insignificant, and that is scary! As far as fileutils...couldn't agree more ;-) But that doesn't make a locally exploitable root hole in the kernel any less significant.
cheers,
-chris
Signature · 1 line
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
security of fileutils (Re: Release of 2.4.21)
In reply to Jeff GarzikHi!
Quoted 6 lines
This specific ptrace hole is closed, yay. Now what about the other 10,001 that still exist? People are blowing this ptrace bug WAY
out of proportion. The only reason why it demands a modicum of
vendor responsibility is that a-holes are making easy-to-use exploits available for the script kiddies.
Quoted 6 lines
In my more cynical moods, I wish bugtraq'ers would start posting exploits to all the races in GNU coreutils (cp/mv/rm/...). Assuming such actions would (finally) lead to bug fixes.... maybe then I will start taking local root holes a bit more seriously. I will no more than hint about this in public, but will respond privately with details (if I know you).
Can you give me the details? I can
imagine holes like "if I can force root
to rm -rf /tmp/my-dir while my scripts
are running, I can rm whatever I want"
and probably could force root to cp
files he did not want to copy, but that would require a *lot* of social ingeneering... Unlike ptrace which seems to be "gimme root, now!" case.
Pavel
(I left l-k in cc, you may want to strip it)
Signature · 2 lines
Pavel Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...