From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] ntp: remove dependency on libmd (ntp has internal MD5 code)
Date: Tue, 4 Oct 2016 15:57:42 +0200 [thread overview]
Message-ID: <20161004135742.kosdo66sya4jrwev@pengutronix.de> (raw)
In-Reply-To: <1475526692.15532.58.camel@ws-apr.office.loc>
On Mon, Oct 03, 2016 at 10:31:32PM +0200, Andreas Pretzsch wrote:
> On Mo, 2016-10-03 at 21:27 +0200, Andreas Pretzsch wrote:
> > libmd provides various message digest algorithms.
> > From these, ntp only uses MD5.
> > In case there is no system-wide MD5 (e.g. from libmd), ntp will use
> > its own implementation from lib/isc/md5.c instead.
> > Therefore, external dependency on libmd can be removed.
>
> Main reason I did this is that libmd license tagging is not that easy.
> See my parallel mail "libmd: specification of license tags".
>
> Beside, having an external lib just to externalize MD5, esp. one that
> seems to be not touched since 2009, might be a bit overkill.
>
>
> > Signed-off-by: Andreas Pretzsch <apr@cn-eng.de>
> > ---
> > build-tested with ntp-4.2.6p5, but code still present in ntp-4.2.8p7, so
> > I expect this will still work. Same applies for only using MD5 from libmd.
>
> Would be great if someone could check with a more recent ntp, i.e. the
> one in ptxdist mainline.
> On the concerned BSP here, I have some local
> work-around-ntp-tools-behaviour hacks, which I'm not keen on investing
> the time for porting...
>
> >
> > rules/ntp.in | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/rules/ntp.in b/rules/ntp.in
> > index a1aa6d9..9f85406 100644
> > --- a/rules/ntp.in
> > +++ b/rules/ntp.in
> > @@ -8,7 +8,6 @@ menuconfig NTP
> > select LIBC_M
> > select LIBC_RT
> > select GCCLIBS_GCC_S
> > - select LIBMD
> > help
> > Build the standard NTP Daemon Process and supplementary programs.
> > This conflicts with BSD openntpd.
>
> Michael, you added this dependency with the commit 3ad9148 from
> 2011-01-18 called "[ntp] fix dependencies". Guess you don't remember
> exactly why, do you ? ;-)
I think the version we used back then didn't have the internal
implementation. And if I read the code correctly, then the current version
doesn't even check any more and always used the internal version, so this
patch looks good.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-04 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 19:27 Andreas Pretzsch
2016-10-03 20:31 ` Andreas Pretzsch
2016-10-04 13:57 ` Michael Olbrich [this message]
2016-10-04 15:53 ` Andreas Pretzsch
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=20161004135742.kosdo66sya4jrwev@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.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