Mercurial > dropbear
view debian/README.runit @ 1921:284c3837891c
Allow user space file locations (rootless support)
Why:
Running dropbear as a user (rootless) is aided if
files and programs can be saved/removed without
needing sudo.
What:
Use the same convention as DROPBEAR_DEFAULT_CLI_AUTHKEY;
if not starting with '/', then is relative to hedge's /home/hedge:
*_PRIV_FILENAME
DROPBEAR_PIDFILE
SFTPSERVER_PATH
default_options.h commentary added.
Changes kept to a minimum, so log entry in svr_kex.c#163
is refactored.
From:
Generated hostkey is <path> ... <finger-print>
to:
Generated hostkey path is <path>
Generated hostkey fingerprint is <fp>
Otherwise the unexpanded path was reported.
Patch modified by Matt Johnston
Signed-off-by: Begley Brothers Inc <[email protected]>
author | Begley Brothers Inc <begleybrothers@gmail.com> |
---|---|
date | Thu, 09 Jul 2020 17:47:58 +1000 |
parents | 8c2d2edadf2a |
children |
line wrap: on
line source
Using the dropbear SSH server with runit's services supervision --------------------------------------------------------------- The dropbear SSH server is perfectly suited to be run under runit's service supervision, and this package already has prepared an adequate service directory. Follow these steps to enable the dropbear service using the runit package. If not yet installed on your system, install the runit package, and make sure its service supervision is enabled (it's by default) # apt-get install runit Make sure the dropbear service normally handled through the sysv init script is stopped # /etc/init.d/dropbear stop Create the system user ``dropbearlog'' which will run the logger service, and own the logs # adduser --system --home /var/log/dropbear --no-create-home dropbearlog Create the log directory and make the newly created system user the owner of this directory # mkdir -p /var/log/dropbear && chown dropbearlog /var/log/dropbear Optionally adjust the configuration of the dropbear service by editing the run script # vi /etc/dropbear/run Finally enable the service through runit's update-service(8) program, the service will be started within five seconds, and automatically at boot time, and the sysv init script will automatically be disabled; see the sv(8) program for information on how to control services handled by runit. See the svlogd(8) program on how to configure the log service. # update-service --add /etc/dropbear Optionally check the status of the service a few seconds later # sv status dropbear -- Gerrit Pape <[email protected]>, Fri, 02 Mar 2007 20:41:08 +0000