From: Brad House <brad@mainstreetsoftworks.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] openssl-0.9.7l (security)
Date: Sun, 05 Aug 2007 16:28:45 -0400 [thread overview]
Message-ID: <46B632FD.60607@mainstreetsoftworks.com> (raw)
0.9.7e has a few advisories against it.
Here's a patch to bring it up to a more 'secure' version,
should maintain binary compatibility as well.
I've also switched the option 'no-threads' to 'threads'. It
doesn't actually add any link dependencies to openssl,
it simply enables some callbacks where a programmer can
'register' thread-safe callbacks for mutexes, etc. If the
programmer doesn't implement them, the library behaves the
same as a no-threads build, so there is no impact here.
Programs which use threads and OpenSSL _will_ crash randomly
if openssl is not compiled with thread support.
Please apply the attached patch, and also remove the
openssl-0.9.7e-no-fips.patch
-Brad
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: openssl-0.9.7m.patch
Url: http://busybox.net/lists/buildroot/attachments/20070805/1c73b2f1/attachment.diff
next reply other threads:[~2007-08-05 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 20:28 Brad House [this message]
2007-08-11 13:22 ` [Buildroot] [patch] openssl-0.9.7l (security) Brad House
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=46B632FD.60607@mainstreetsoftworks.com \
--to=brad@mainstreetsoftworks.com \
--cc=buildroot@busybox.net \
/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