From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Jimmy Durand Wesolowski via buildroot <buildroot@buildroot.org>,
romain.naour@smile.fr,
Jimmy Durand Wesolowski <jimmy.wesolowski@mobileye.com>,
guenther.harrasser@mobileye.com
Subject: Re: [Buildroot] [PATCH] package/openssh: enable DES when using libopenssl
Date: Fri, 21 Aug 2026 16:44:03 +0200 [thread overview]
Message-ID: <874ign8rf0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <aohFF1WM2HaL7WU9@windsurf> (Thomas Petazzoni's message of "Fri, 21 Aug 2026 14:38:26 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
Hi,
> So basically, the idea is that if we have OpenSSL, we don't have
> crypt(), but we have DES_crypt, then we use DES_crypt() as
> crypt(). Otherwise, the crypt() call in the OpenSSH xcrypt() function
> remains crypt(), and things blow up when you're building with glibc
> and you don't have libxcrypt around to provide crypt().
> So indeed, we have two options here:
> - Always provide a crypt() implementation by making libxcrypt
> mandatory for OpenSSH as a whole, not just for the server-side
> - Require OpenSSH to provide DES support, which is what Jimmy was
> proposing.
> I honestly don't have a strong argument. My vague feeling is that DES
> being obsolete, it feels odd to be forced to enable it. Though perhaps
> libxcrypt would in fact provide exactly the same obsolete crypto
> algorithm?
> Peter: thoughts?
I am not sure what openssh uses crypt() for exactly when the server is
not built, but perhaps it just ends up building a bit too much?
Anyway, given that we already use libxcrypt for the server part and
libxcrypt supports a bunch of other algorithmns than just legacy DES, I
think it makes sense to just move the libxcrypt select to the main
option instead.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-21 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 10:07 [Buildroot] [PATCH] package/openssh: enable DES when using libopenssl Jimmy Durand Wesolowski via buildroot
2026-07-28 20:42 ` Peter Korsgaard
2026-08-21 12:38 ` Thomas Petazzoni via buildroot
2026-08-21 14:44 ` Peter Korsgaard [this message]
2026-08-31 16:09 ` [Buildroot] [PATCH] openssh: ensure libxcrypt is enabled to provide a crypt() implementation Jimmy Durand Wesolowski via buildroot
2026-08-31 19:10 ` Peter Korsgaard
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=874ign8rf0.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=guenther.harrasser@mobileye.com \
--cc=jimmy.wesolowski@mobileye.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
/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.