From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.25
Date: Tue, 18 Jul 2006 17:07:53 -0400 [thread overview]
Message-ID: <e9jid5$fak$1@sea.gmane.org> (raw)
In-Reply-To: <20060715025906.GA11167@kroah.com>
Greg KH wrote:
> We (the -stable team) are announcing the release of the 2.6.16.25 kernel.
>
> I'll also be replying to this message with a copy of the patch between
> 2.6.16.24 and 2.6.16.25, as it is small enough to do so.
Why does the patch make it to linux-kernel-announce and the nice
announcement, like this one, not? The short patch description is far
more useful, since if it's to something I don't use I don't need to
apply or examine it.
>
> The updated 2.6.16.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git
> and can be browsed at the normal kernel.org git web browser:
> www.kernel.org/git/
>
> thanks,
>
> greg k-h
>
> --------
>
>
> Makefile | 2 +-
> fs/proc/base.c | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> Summary of changes from v2.6.16.24 to v2.6.16.23
> ================================================
>
> Greg Kroah-Hartman:
> Linux 2.6.16.25
>
> Linus Torvalds:
> Fix nasty /proc vulnerability (CVE-2006-3626)
>
--
Bill Davidsen <davidsen@tmr.com>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
next prev parent reply other threads:[~2006-07-18 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-15 2:59 Linux 2.6.16.25 Greg KH
2006-07-15 2:59 ` Greg KH
2006-07-15 3:29 ` [stable] " Greg KH
1970-01-01 13:26 ` Pavel Machek
2006-07-16 14:42 ` Pavel Machek
2006-07-16 18:20 ` Greg KH
2006-07-16 21:27 ` Pavel Machek
2006-07-18 21:07 ` Bill Davidsen [this message]
2006-07-25 4:34 ` Greg KH
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='e9jid5$fak$1@sea.gmane.org' \
--to=davidsen@tmr.com \
--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.