From: Saul Wold <saul.wold@intel.com>
To: Yu Ke <ke.yu@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/1] upgrade shadow for security vulnerability
Date: Tue, 01 Mar 2011 10:52:59 -0800 [thread overview]
Message-ID: <4D6D408B.90600@intel.com> (raw)
In-Reply-To: <cover.1298950650.git.ke.yu@intel.com>
On 02/28/2011 07:39 PM, Yu Ke wrote:
> per Scott's suggest, upgrade the shadow to fix security vulnerability
>
> CC: Scott Garman<scott.a.garman@intel.com>
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: kyu3/shadow
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kyu3/shadow
>
> Thanks,
> Yu Ke<ke.yu@intel.com>
> ---
>
>
> Yu Ke (1):
> shadow: upgrade to 4.1.4.3 to fix security vulnerability
>
> .../{shadow-4.1.4.2 => files}/login_defs_pam.sed | 0
> .../shadow/{shadow-4.1.4.2 => files}/pam.d/chfn | 0
> .../{shadow-4.1.4.2 => files}/pam.d/chpasswd | 0
> .../shadow/{shadow-4.1.4.2 => files}/pam.d/chsh | 0
> .../shadow/{shadow-4.1.4.2 => files}/pam.d/login | 0
> .../{shadow-4.1.4.2 => files}/pam.d/newusers | 0
> .../shadow/{shadow-4.1.4.2 => files}/pam.d/passwd | 0
> .../shadow/{shadow-4.1.4.2 => files}/pam.d/su | 0
> .../shadow/{shadow-4.1.4.2 => files}/securetty | 0
> .../shadow-4.1.3-dots-in-usernames.patch | 0
> .../shadow-4.1.4.2-env-reset-keep-locale.patch | 0
> .../shadow-4.1.4.2-groupmod-pam-check.patch | 0
> .../shadow-4.1.4.2-su_no_sanitize_env.patch | 0
> .../shadow.automake-1.11.patch | 0
> .../{shadow_4.1.4.2.bb => shadow_4.1.4.3.bb} | 4 ++--
> 15 files changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/login_defs_pam.sed (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/pam.d/chfn (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/pam.d/chpasswd (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/pam.d/chsh (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/pam.d/login (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/pam.d/newusers (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/pam.d/passwd (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/pam.d/su (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/securetty (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/shadow-4.1.3-dots-in-usernames.patch (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/shadow-4.1.4.2-env-reset-keep-locale.patch (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/shadow-4.1.4.2-groupmod-pam-check.patch (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/shadow-4.1.4.2-su_no_sanitize_env.patch (100%)
> rename meta/recipes-extended/shadow/{shadow-4.1.4.2 => files}/shadow.automake-1.11.patch (100%)
> rename meta/recipes-extended/shadow/{shadow_4.1.4.2.bb => shadow_4.1.4.3.bb} (70%)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Merged into master and Bernard
Thanks
Sau!
prev parent reply other threads:[~2011-03-01 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 3:39 [PATCH 0/1] upgrade shadow for security vulnerability Yu Ke
2011-03-01 3:39 ` [PATCH 1/1] shadow: upgrade to 4.1.4.3 to fix " Yu Ke
2011-03-01 18:52 ` Saul Wold [this message]
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=4D6D408B.90600@intel.com \
--to=saul.wold@intel.com \
--cc=ke.yu@intel.com \
--cc=poky@yoctoproject.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.