8012250b86
When the rootfs is read-only, keys will be generated in a volatile location, which is inherently bad as host keys will change on each boot, rendering them virtually useless. Add a warning so the user is at least aware of the issue. Hide the rm output to avoid noisy output, now that we have a proper warning. Move the starting message after the symlink-block, to avoid messages collision. Move the umask as well, since /etc/dropbear/ may be world readable; just the private host keys should be ?00 (and dropbear handles that by itself). [Peter: minor tweaks to commit message] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
27 lines
932 B
Desktop File
27 lines
932 B
Desktop File
[Unit]
|
|
Description=Dropbear SSH daemon
|
|
After=syslog.target network.target auditd.service
|
|
|
|
[Service]
|
|
# If /etc/dropbear is a symlink to /var/run/dropbear, and
|
|
# - the filesystem is RO (i.e. we can not rm the symlink),
|
|
# create the directory pointed to by the symlink.
|
|
# - the filesystem is RW (i.e. we can rm the symlink),
|
|
# replace the symlink with an actual directory
|
|
ExecStartPre=/bin/sh -c '\
|
|
if [ -L /etc/dropbear \
|
|
-a "$(readlink /etc/dropbear)" = "/var/run/dropbear" ]; then \
|
|
if rm -f /etc/dropbear >/dev/null 2>&1; then \
|
|
mkdir -p /etc/dropbear; \
|
|
else \
|
|
echo "No persistent location to store SSH host keys. New keys will be"; \
|
|
echo "generated at each boot. Are you sure this is what you want to do?"; \
|
|
mkdir -p "$(readlink /etc/dropbear)"; \
|
|
fi; \
|
|
fi'
|
|
ExecStart=/usr/sbin/dropbear -F -R
|
|
ExecReload=/bin/kill -HUP $MAINPID
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|