From: Peter Korsgaard <peter@korsgaard.com>
To: Florian Larysch <fl@n621.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libjwt: require openssl
Date: Thu, 21 Aug 2025 23:05:24 +0200 [thread overview]
Message-ID: <87plcol71n.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250816204354.sdds7hpjzb5n7bkx@n621.de> (Florian Larysch's message of "Sat, 16 Aug 2025 22:43:54 +0200")
>>>>> "Florian" == Florian Larysch <fl@n621.de> writes:
> On Sat, Aug 16, 2025 at 10:17:47PM +0200, Peter Korsgaard wrote:
>> While it can work with the combination gnutls + libopenssl, would there
>> be any advantage over just using openssl for everything?
> I've been wondering about this as well. It seems that applications using
> libjwt can select between backends using an API call[1]. There don't
> seem to be any feature differences between gnutls and openssl in my
> cursory reading of the code. Furthermore, I could find no public use of
> the backend switching API beyond libjwt's own test cases.
> There seem to have been differences in feature completeness in the past
> though[2][3], so it's possible that this is vestigial and/or the author
> doesn't want to break existing applications more than necessary.
> We could remove it from Buildroot entirely (though libjwt will still
> automatically link to it when it detects gnutls in its sysroot via
> pkg-config[4]), but it also doesn't hurt much as it doesn't enable the
> gnutls dependency itself, so the overhead just is linking another object
> file into the library
OK. Committed after dropping the gnutls support, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-21 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 19:55 [Buildroot] [PATCH 1/1] package/libjwt: require openssl Florian Larysch
2025-08-16 20:17 ` Peter Korsgaard
2025-08-16 20:43 ` Florian Larysch
2025-08-21 21:05 ` Peter Korsgaard [this message]
2025-09-08 10:56 ` Thomas Perale via buildroot
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=87plcol71n.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fl@n621.de \
/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