The earlier commit ea119211b2 removed 'dsa' as one of the ssh_host_*_key
types that got generated. Problem was that it didn't remove that key
as one of the paths that the server looks for by default. As a
consequence, your log file might fill up with messages like:
2017-06-01T15:43:07-06:00 openwrt sshd[31929]: error: Could not load host key: /etc/ssh/ssh_host_dsa_key
The patch is forunately trivial. Don't set the path for the dsa
key file in the server configuration.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
MUSL is complaining about <sys/poll.h> instead of <poll.h>.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
[ Replaced the *-t1lib filtering stuff by simply removing the
left-over configure option ]
Signed-off-by: Michael Heimpold <mhei@heimpold.de>
If you have a firstboot script which seeds a passwd based on
run-time information (like MAC addresses, hostname, etc) then
you need to be able to pass in a cleartext string via chpasswd.
Other applets are similarly potentially useful in other corner
cases.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
Likewise fix default configuration to use SOCK_DGRAM and not SOCK_STREAM
as we currently do.
Add sha256 digest.
Rather than have the users replace syslog-ng.conf (which lately is
changing fairly frequently) and have them miss an important fix or
improvement, instead have them localize /etc/custom-logs.conf and
ship that as an empty file.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
lighttpd starts at priority 50, but promptly calls getrandom() on
initialization (li_rand_reseed() and li_rand_device_bytes() from
server_init()). If /dev/urandom (which getrandom() uses by default)
doesn't have sufficient entropy, this will block.
Since Openwrt runs the startup scripts serially, this can block
initialization indefinitely. I've seen 15-20 minutes typically.
Seeding the pool early on can quickly built sufficient entropy to
complete booting without blocking.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
Certain strings are misinterpreted as comments by perlmod.mk and removed
when they shouldn't be (in particular, perl-cgi). Enable this whenever
you have sufficient flash space.
Globally, CONFIG_PERL_NOCOMMENT=y (default) causes comments to be stripped
as before. However, a package (like perl-cgi) can override this with
PKG_LEAVE_COMMENTS=1.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
The macro perlmod/Install does comment stripping which gets confused by
the line:
in several files in this module, incorrectly deleting it as a comment.
It's not: it's the closure of a "= q/" literal.
See PR #3740 as this is a prerequisite.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
Install the plugins as various functionality is no longer in the
utility itself but is packaged as a .so plugin instead. Disable
plugins with too many dependencies (or too exotic).
Bump the version number on the config file to agree with the package's
version number.
Clean up any .la files from libtool.
Start much earlier so that logging doesn't miss startup messages from
other services.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
Version bumped to 4.3.5. Separated out compile/install steps since
compiling with $DESTDIR yields bogus results. Removed rfc-3527 patch
as something similar (better) is now upstream (well, more complete
error checking anyway). Change relay scripts from '-l ifname' to
'-U ifname' to correspond to upstream changes.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
