From: "Marcos D. Marado Torres" <marado@student.dei.uc.pt>
To: linux-kernel@vger.kernel.org
Subject: Linux mremap bug correction (fwd)
Date: Tue, 6 Jan 2004 18:26:21 +0000 (WET) [thread overview]
Message-ID: <Pine.LNX.4.58.0401061825330.7109@student.dei.uc.pt> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Look what I've just recieved...
It seems that 2.2 isn't vulnerable after all.
Mind Booster Noori
- --
==================================================
Marcos Daniel Marado Torres AKA Mind Booster Noori
/"\ http://student.dei.uc.pt/~marado
\ / marado@student.dei.uc.pt
X ASCII Ribbon Campaign
/ \ against HTML e-mail and Micro$oft attachments
==================================================
- ---------- Forwarded message ----------
Date: Tue, 6 Jan 2004 17:30:35 +0100 (CET)
From: Paul Starzetz <ihaquer@isec.pl>
Reply-To: security@isec.pl
To: vulnwatch@vulnwatch.org, full-disclosure@lists.netsys.com,
bugtraq@securityfocus.com
Subject: Linux mremap bug correction
Hi,
our initial posting contains a mistake about the vulnerability of the 2.2
kernel series. Since the 2.2 kernel series doesn't support the
MREMAP_FIXED flag it is NOT vulnerable. The source states
"MREMAP_FIXED option added 5-Dec-1999" but it didn't make into recent
2.2.x. We apologize for inconvenience.
- --
Paul Starzetz
iSEC Security Research
http://isec.pl/
- ------------ Output from gpg ------------
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: Signature made Tue 06 Jan 2004 04:30:40 PM WET using DSA key ID 9E70A6EE
gpg: Can't check signature: public key not found
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQE/+v3SmNlq8m+oD34RAgF0AKDdqihpm5MWL2rxBvuwibehAoAEbACghemA
6wEeuJ/nEoWZpaSfUA0pDjU=
=VLWm
-----END PGP SIGNATURE-----
reply other threads:[~2004-01-06 18:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0401061825330.7109@student.dei.uc.pt \
--to=marado@student.dei.uc.pt \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.