2008-04-09 09:35:12 +02:00
|
|
|
#!/bin/sh
|
|
|
|
#
|
|
|
|
# Starts dropbear sshd.
|
|
|
|
#
|
|
|
|
|
dropbear: add support for custom arguments through config file
The default port 22 used by dropbear for its SSH connections is not always
desired. Dropbear accepts an option '-p' to set the port, but doing this was
not possible from the buildroot-provided init script.
One way to fix this is by adding a custom S50dropbear in a project-specific
rootfs overlay. However, this approach has the big disadvantage that bug
fixes or improvements in the default init script (i.e. in newer buildroot
releases) are not available (unless you manually port these changes each
time you upgrade buildroot).
Another solution is to modify the default init script from a
project-specific post-build script. However, this is fragile because you'd
have to sed some line but this line may change in later buildroot releases.
Yet another solution is to change the default port at build time, by
patching the options.h header file in the dropbear sources. This was
proposed with a patch [1] before, but not accepted.
This patch implements another solution, hinted from the discussion in [1]:
the default init script now sources a config file /etc/default/dropbear, in
which the user can set the variable DROPBEAR_ARGS. This is similar to the
S81named init script in the bind package. The config file would be added to
a project-specific rootfs overlay, a custom skeleton, or created from a
post-build script.
This approach has the advantage of being simple and non-intrusive, without
any code duplication or fragile script modifications.
[1] http://lists.busybox.net/pipermail/buildroot/2013-November/083165.html
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-01-02 13:34:42 +01:00
|
|
|
# Allow a few customizations from a config file
|
|
|
|
test -r /etc/default/dropbear && . /etc/default/dropbear
|
|
|
|
|
2008-04-09 09:35:12 +02:00
|
|
|
start() {
|
dropbear: add support for custom arguments through config file
The default port 22 used by dropbear for its SSH connections is not always
desired. Dropbear accepts an option '-p' to set the port, but doing this was
not possible from the buildroot-provided init script.
One way to fix this is by adding a custom S50dropbear in a project-specific
rootfs overlay. However, this approach has the big disadvantage that bug
fixes or improvements in the default init script (i.e. in newer buildroot
releases) are not available (unless you manually port these changes each
time you upgrade buildroot).
Another solution is to modify the default init script from a
project-specific post-build script. However, this is fragile because you'd
have to sed some line but this line may change in later buildroot releases.
Yet another solution is to change the default port at build time, by
patching the options.h header file in the dropbear sources. This was
proposed with a patch [1] before, but not accepted.
This patch implements another solution, hinted from the discussion in [1]:
the default init script now sources a config file /etc/default/dropbear, in
which the user can set the variable DROPBEAR_ARGS. This is similar to the
S81named init script in the bind package. The config file would be added to
a project-specific rootfs overlay, a custom skeleton, or created from a
post-build script.
This approach has the advantage of being simple and non-intrusive, without
any code duplication or fragile script modifications.
[1] http://lists.busybox.net/pipermail/buildroot/2013-November/083165.html
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-01-02 13:34:42 +01:00
|
|
|
DROPBEAR_ARGS="$DROPBEAR_ARGS -R"
|
|
|
|
|
2015-07-28 10:21:31 +02:00
|
|
|
# If /etc/dropbear is a symlink to /var/run/dropbear, and
|
2015-07-14 00:44:01 +02:00
|
|
|
# - 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
|
2015-07-28 10:21:31 +02:00
|
|
|
if [ -L /etc/dropbear \
|
2015-08-18 21:25:53 +02:00
|
|
|
-a "$(readlink /etc/dropbear)" = "/var/run/dropbear" ]
|
2015-07-28 10:21:31 +02:00
|
|
|
then
|
2015-08-25 23:43:33 +02:00
|
|
|
if rm -f /etc/dropbear >/dev/null 2>&1; then
|
2015-07-14 00:44:01 +02:00
|
|
|
mkdir -p /etc/dropbear
|
|
|
|
else
|
2015-08-25 23:43:33 +02:00
|
|
|
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)"
|
2015-07-14 00:44:01 +02:00
|
|
|
fi
|
|
|
|
fi
|
|
|
|
|
2015-10-03 23:29:57 +02:00
|
|
|
printf "Starting dropbear sshd: "
|
2015-08-25 23:43:33 +02:00
|
|
|
umask 077
|
|
|
|
|
dropbear: add support for custom arguments through config file
The default port 22 used by dropbear for its SSH connections is not always
desired. Dropbear accepts an option '-p' to set the port, but doing this was
not possible from the buildroot-provided init script.
One way to fix this is by adding a custom S50dropbear in a project-specific
rootfs overlay. However, this approach has the big disadvantage that bug
fixes or improvements in the default init script (i.e. in newer buildroot
releases) are not available (unless you manually port these changes each
time you upgrade buildroot).
Another solution is to modify the default init script from a
project-specific post-build script. However, this is fragile because you'd
have to sed some line but this line may change in later buildroot releases.
Yet another solution is to change the default port at build time, by
patching the options.h header file in the dropbear sources. This was
proposed with a patch [1] before, but not accepted.
This patch implements another solution, hinted from the discussion in [1]:
the default init script now sources a config file /etc/default/dropbear, in
which the user can set the variable DROPBEAR_ARGS. This is similar to the
S81named init script in the bind package. The config file would be added to
a project-specific rootfs overlay, a custom skeleton, or created from a
post-build script.
This approach has the advantage of being simple and non-intrusive, without
any code duplication or fragile script modifications.
[1] http://lists.busybox.net/pipermail/buildroot/2013-November/083165.html
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-01-02 13:34:42 +01:00
|
|
|
start-stop-daemon -S -q -p /var/run/dropbear.pid \
|
|
|
|
--exec /usr/sbin/dropbear -- $DROPBEAR_ARGS
|
2014-10-26 18:41:43 +01:00
|
|
|
[ $? = 0 ] && echo "OK" || echo "FAIL"
|
2008-04-09 09:35:12 +02:00
|
|
|
}
|
|
|
|
stop() {
|
2015-10-03 23:29:57 +02:00
|
|
|
printf "Stopping dropbear sshd: "
|
2008-04-09 09:35:12 +02:00
|
|
|
start-stop-daemon -K -q -p /var/run/dropbear.pid
|
2014-10-26 18:41:43 +01:00
|
|
|
[ $? = 0 ] && echo "OK" || echo "FAIL"
|
2008-04-09 09:35:12 +02:00
|
|
|
}
|
|
|
|
restart() {
|
|
|
|
stop
|
|
|
|
start
|
|
|
|
}
|
|
|
|
|
|
|
|
case "$1" in
|
|
|
|
start)
|
|
|
|
start
|
|
|
|
;;
|
|
|
|
stop)
|
|
|
|
stop
|
|
|
|
;;
|
|
|
|
restart|reload)
|
|
|
|
restart
|
|
|
|
;;
|
|
|
|
*)
|
2012-03-15 22:08:09 +01:00
|
|
|
echo "Usage: $0 {start|stop|restart}"
|
2008-04-09 09:35:12 +02:00
|
|
|
exit 1
|
|
|
|
esac
|
|
|
|
|
|
|
|
exit $?
|