From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: David GOUARIN <dgouarin@gmail.com>,
Matt Weber <matthew.weber@collins.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/freeradius-server: requires MD4 in openssl
Date: Thu, 28 Jul 2022 22:52:43 +0200 [thread overview]
Message-ID: <20220728225243.57d51df7@windsurf> (raw)
In-Reply-To: <56e3cdc8-3c1a-de9c-be9e-b114790fa026@mind.be>
On Thu, 28 Jul 2022 21:39:09 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> > In file included from src/lib/md4.c:16:
> > src/lib/md4.c: In function 'fr_md4_calc':
> > src/freeradius-devel/md4.h:76:33: error: unknown type name 'MD4_CTX'; did you mean 'FR_MD4_CTX'?
> > 76 | # define FR_MD4_CTX MD4_CTX
> > | ^~~~~~~
>
> Would there instead be a way to convince freeradius not to use MD4? Using MD4
> these days is really a bad idea...
I agree, but for the time being, since freeradius-server uses it, from
a packaging point of view, we don't have much choice but to enable MD4
support. That being said, it would certainly be good to look into
freeradius and see if usage of MD4 can be disabled/removed.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-28 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 8:24 [Buildroot] [PATCH 1/1] package/freeradius-server: requires MD4 in openssl Fabrice Fontaine
2022-07-28 19:39 ` Arnout Vandecappelle
2022-07-28 20:52 ` Thomas Petazzoni via buildroot [this message]
2022-07-28 20:51 ` Thomas Petazzoni 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=20220728225243.57d51df7@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=dgouarin@gmail.com \
--cc=fontaine.fabrice@gmail.com \
--cc=matthew.weber@collins.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox