e7d04dd2df
dropbear generates its keys at the first connection, and wants to save
them in /etc/dropbear (not configurable).
Currently, our /etc/dropbear is a directory.
When the filesystem is read-only, dropbear can't save its keys, so
refuses all connections.
Fix that with:
- at build time, create /etc/dropbear as a symlink to
/var/run/dropbear
- at runtime, if the filesystem is RW (we can rm /etc/dropbear),
we replace the symlink with an actual directory; otherwise,
when the filesystem is RO (we can't rm /etc/dropbear), we create
/var/run/dropbear so the symlink points to an existing directory
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
Acked-by: "Maxime Hadjinlian" <maxime.hadjinlian@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
24 lines
675 B
Desktop File
24 lines
675 B
Desktop File
[Unit]
|
|
Description=Dropbear SSH daemon
|
|
After=syslog.target network.target auditd.service
|
|
|
|
[Service]
|
|
# If /etc/dropbear is not a directory, 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 ! [ -d /etc/dropbear ]; then \
|
|
if rm -f /etc/dropbear; then \
|
|
mkdir -p /etc/dropbear; \
|
|
else \
|
|
mkdir -p $(readlink /etc/dropbear); \
|
|
fi; \
|
|
fi'
|
|
ExecStart=/usr/sbin/dropbear -F -R
|
|
ExecReload=/bin/kill -HUP $MAINPID
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|