Your message dated Sun, 7 Jul 2024 19:41:49 +0200
with message-id <[email protected]>
and subject line Re: Bug#1075907: dropbear starts despite NO_START=1
has caused the Debian Bug report #1075907,
regarding dropbear starts despite NO_START=1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1075907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075907
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dropbear
Version: 2022.83-1+deb12u1
I am using dropbear to remotely unlock encrypted disks
(https://github.com/ceremcem/unlock-luks-partition) in debian 11. I
want to use openssh-server once the system has started. It has
previously worked well.
I have now upgraded to debian 12 bookworm. Now dropbear keeps restarting
and blocks port 22. I cant succeed to disable it.
/etc/default/dropbear
# disabled because OpenSSH is installed
# change to NO_START=0 to enable Dropbear
NO_START=1
# the TCP port that Dropbear listens on
DROPBEAR_PORT=22
# any additional arguments for Dropbear
DROPBEAR_EXTRA_ARGS=
# specify an optional banner file containing a message to be
# sent to clients before they connect, such as "/etc/issue.net"
DROPBEAR_BANNER=""
# RSA hostkey file (default: /etc/dropbear/dropbear_rsa_host_key)
#DROPBEAR_RSAKEY="/etc/dropbear/dropbear_rsa_host_key"
# DSS hostkey file (default: /etc/dropbear/dropbear_dss_host_key)
#DROPBEAR_DSSKEY="/etc/dropbear/dropbear_dss_host_key"
# ECDSA hostkey file (default: /etc/dropbear/dropbear_ecdsa_host_key)
#DROPBEAR_ECDSAKEY="/etc/dropbear/dropbear_ecdsa_host_key"
# Receive window size - this is a tradeoff between memory and
# network performance
DROPBEAR_RECEIVE_WINDOW=65536
I have tried reinstalling dropbear.
I have tried changing port during boot/unlock which changed the port I
had to use to unlock. This makes me think its not during the
unlock-process something goes wrong. Dropbear keeps starting at port 22
once the system is booted.
....
root 1472 0.0 0.0 4524 1344 ? Ss 17:41 0:00 /usr/sbin/dropbear -EF -p 22
-W 65536
...
root 1933 0.0 0.0 4524 3180 ? Ss 17:41 0:00 /usr/sbin/dropbear -EF -p 22
-W 65536 -2 8
...
...
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1472/dropbear
...
tcp 0 208 192.168.119.24:22 192.168.119.23:62197 ESTABLISHED 1933/dropbear
tcp6 0 0 :::22 :::* LISTEN 1472/dropbear
...
--- End Message ---
--- Begin Message ---
From the NEWS file:
| dropbear (2022.82-1) unstable; urgency=medium
|
| Setting NO_START=1 in /etc/default/dropbear in order to avoid
automatically
| starting dropbear(8) is no longer honored. Use your service manager
| instead, for instance run `systemctl disable --now dropbear`.
| Alternatively, you can run `apt remove dropbear` to remove startup scripts
| and service files (you'll still be able to start dropbear(8) manually if
| the 'dropbear-bin' package is installed, and use the initramfs integration
| if the 'dropbear-initramfs' package is installed.)
|
| In addition, /etc/default/dropbear settings DROPBEAR_*KEY and
| DROPBEAR_BANNER are subsumed by DROPBEAR_EXTRA_ARGS are no longer honored.
| See /etc/default/dropbear for examples.
|
| -- Guilhem Moulin <[email protected]> Sat, 02 Apr 2022 15:51:17 +0200
--
Guilhem.
signature.asc
Description: PGP signature
--- End Message ---
