Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Fix issue with newer glibc crypt() function
Date: Fri,  5 Apr 2013 10:09:30 -0700	[thread overview]
Message-ID: <1365181772-18644-1-git-send-email-sgw@linux.intel.com> (raw)

The 2.17 version of glibc's crypt() was changed to returning NULL if
it got an invalid seed, this broke tinylogin and shadow in different
ways.

Thanks to the Slackware team for "just in time patches", they found it 
first in shadow around March 28th!

I do not believe that these will introduce any security concerns, please 
review with a careful eye.

Sau!


Saul Wold (2):
  tinylogin: fix segfault from crypt()
  shadow: add patch to fix crypt: Invalid Argument

 .../tinylogin/tinylogin-1.4/glibc_crypt_fix.patch  | 23 ++++++++
 meta/recipes-core/tinylogin/tinylogin_1.4.bb       |  4 +-
 .../files/slackware_fix_for_glib-2.17_crypt.patch  | 63 ++++++++++++++++++++++
 meta/recipes-extended/shadow/shadow_4.1.4.3.bb     |  1 +
 4 files changed, 90 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-core/tinylogin/tinylogin-1.4/glibc_crypt_fix.patch
 create mode 100644 meta/recipes-extended/shadow/files/slackware_fix_for_glib-2.17_crypt.patch

-- 
1.8.0.2




             reply	other threads:[~2013-04-05 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 17:09 Saul Wold [this message]
2013-04-05 17:09 ` [PATCH 1/2] tinylogin: fix segfault from crypt() Saul Wold
2013-04-05 17:09 ` [PATCH 2/2] shadow: add patch to fix crypt: Invalid Argument Saul Wold

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=1365181772-18644-1-git-send-email-sgw@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox