From: Leo Famulari <leo@famulari.name>
To: 24674@debbugs.gnu.org
Subject: bug#24674: Dropbear bundled libraries
Date: Wed, 12 Oct 2016 11:15:03 -0400 [thread overview]
Message-ID: <20161012151503.GA22149@jasmine> (raw)
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
Our Dropbear package bundles the libraries libtommath and libtomcrypt
[0], and their bundled changelogs imply that they date from 2006.
The Dropbear CHANGES [1] file shows that some attempt has been made to
cherry-pick some bug fixes. It also looks like Dropbear has made their
own changes to the bundled libraries.
Apparently it is possible to build against non-bundled libraries [2].
Both libraries have had new releases in the last ten years [3].
It appears that Debian does use the bundled libraries [4].
In July, I asked Matt Johnston, the Dropbear author, how far the bundled
copies had diverged from upstream and if it was safe to unbundle them,
but I didn't get a response.
[0]
https://github.com/libtom
https://github.com/mkj/dropbear/tree/master/libtomcrypt
https://github.com/mkj/dropbear/tree/master/libtommath
[1]
https://github.com/mkj/dropbear/blob/master/CHANGES#L481
[2]
https://github.com/mkj/dropbear/blob/master/CHANGES#L532
"- Attempt to build against system libtomcrypt/libtommath if available.
This can be disabled with ./configure --enable-bundled-libtom"
[3]
https://github.com/libtom/libtomcrypt/releases
https://github.com/libtom/libtommath/releases
[4]
https://packages.debian.org/sid/dropbear
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-10-12 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 15:15 Leo Famulari [this message]
2020-12-18 19:53 ` bug#24674: Dropbear bundled libraries zimoun
2020-12-18 21:29 ` Leo Famulari
2020-12-19 6:40 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161012151503.GA22149@jasmine \
--to=leo@famulari.name \
--cc=24674@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).