From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Trying to update tftpd
Date: Wed, 14 Jul 2021 15:00:08 +0200 [thread overview]
Message-ID: <bd41917d-84fc-609e-8039-7f6bbe2b797c@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1771 bytes --]
Hi All,
I am looking to update the tftpd add-on. The existing version, 0.48, is from 2007. The most up to date version, 5.2, is from 2011.
When I run gpg to verify the package signature I get the following response:-
gpg: Signature made Sun 11 Dec 2011 23:14:47 CET
gpg: using RSA key 88AE647D58F7ABFE
gpg: BAD signature from "H. Peter Anvin (kernel.org file signing key) <hpa(a)kernel.org>" [expired]
I suspect that this is due to the key being from 2011 or earlier.
It looks like there might be a couple of bug fixes in the changelog but I am not sure how important they might be:-
Changes in 5.2:
Fix breakage on newer Linux when a single interface has
multiple IP addresses.
Changes in 5.1:
Add -P option to write a PID file. Patch by Ferenc Wagner.
Bounce the syslog socket in standalone mode, in case the
syslog daemon has been restarted. Patch by Ferenc Wagner.
Build fixes.
Fix handling of block number wraparound after a successful
options negotiation.
Fix a buffer overflow in option parsing.
Changes in 5.0:
Try to on platforms with getaddrinfo() without AI_ADDRCONFIG or
AI_CANONNAME.
Implement the "rollover" option, for clients which want block
number to rollover to anything other than zero.
Correctly disable PMTU in standalone mode. Patch by Florian
Lohoff.
Changes in 0.49:
Add IPv6 support. Patch by Karsten Keil.
Support systems with editline instead of readline.
Support long options in the server.
Unless someone comes back and suggests something different, I will leave tftpd as it currently is.
Regards,
Adolf
next reply other threads:[~2021-07-14 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 13:00 Adolf Belka [this message]
2021-07-14 13:09 ` Adolf Belka
2021-07-14 16:04 ` Michael Tremer
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=bd41917d-84fc-609e-8039-7f6bbe2b797c@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox