From: Nathanael D. Noblet <nathanael@gnat.ca>
To: buildroot@busybox.net
Subject: [Buildroot] update to newer openssl and openssh?
Date: Wed, 01 Nov 2006 08:27:24 -0700 [thread overview]
Message-ID: <1162394844.2945.6.camel@iridium.gnat.ca> (raw)
In-Reply-To: <ecb4efd10610311716t17f73770g4b4b5e041006cb88@mail.gmail.com>
On Tue, 2006-10-31 at 20:16 -0500, Clem Taylor wrote:
> I was wondering if there is a reason why the openssl in buildroot is
> so old? buildroot-svn is using 0.9.7e (Oct 25, 2004) and the latest
> version 0.9.8d (Sept 28, 2006). Likewise openssh 3.9p1 and the latest
> is 4.4p1 (Sept 27, 2006). It would seem that you would want to keep
> something like this fairly current.
All it takes is a patch bumping the version in
package/openssl/openssl.mk. You can email it to the mailing list or use
http://bugs.uclibc.org/.
--
Nathanael D. Noblet <nathanael@gnat.ca>
Gnat Solutions, Inc
next prev parent reply other threads:[~2006-11-01 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 1:16 [Buildroot] update to newer openssl and openssh? Clem Taylor
2006-11-01 15:27 ` Nathanael D. Noblet [this message]
2006-11-01 18:41 ` Bernhard Fischer
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=1162394844.2945.6.camel@iridium.gnat.ca \
--to=nathanael@gnat.ca \
--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