Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #263327
| From | Michael <ml@hemathor.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: upgrade to bookworm broke ssh x11 forwarding |
| Date | 2023-11-10 11:10 +0100 |
| Message-ID | <HywCB-4qPH-5@gated-at.bofh.it> (permalink) |
| References | <HyePn-4fZl-1@gated-at.bofh.it> <Hygo9-4gJ5-3@gated-at.bofh.it> <Hygo9-4gJ5-9@gated-at.bofh.it> <HygHv-4h4N-3@gated-at.bofh.it> <HyhDA-4hCV-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > No, this is not a normal phenomenon for bookworm upgrades. I've never > heard of it happening to anyone before. i disagree. i had the same problem b/c i also had dropbear installed. for some reason the dropbear daemon is started first in bookworm, so port 22 was already in use when sshd was started. reading the log file (aka systemd-journal) was very enlightening. a simple systemctl stop dropbear.service systemctl disable dropbear.service systemctl start ssh.service was enough to solve the problem. of course, one needs access to the console... greetings...
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
upgrade to bookworm broke ssh x11 forwarding fxkl47BF@protonmail.com - 2023-11-09 16:10 +0100
Re: upgrade to bookworm broke ssh x11 forwarding Greg Wooledge <greg@wooledge.org> - 2023-11-09 17:50 +0100
Re: upgrade to bookworm broke ssh x11 forwarding fxkl47BF@protonmail.com - 2023-11-09 17:50 +0100
Re: upgrade to bookworm broke ssh x11 forwarding fxkl47BF@protonmail.com - 2023-11-09 18:10 +0100
Re: upgrade to bookworm broke ssh x11 forwarding Greg Wooledge <greg@wooledge.org> - 2023-11-09 19:10 +0100
Re: upgrade to bookworm broke ssh x11 forwarding fxkl47BF@protonmail.com - 2023-11-09 19:40 +0100
Re: upgrade to bookworm broke ssh x11 forwarding Michael <ml@hemathor.de> - 2023-11-10 11:10 +0100
Re: upgrade to bookworm broke ssh x11 forwarding Vincent Lefevre <vincent@vinc17.net> - 2023-11-10 15:50 +0100
Re: upgrade to bookworm broke ssh x11 forwarding fxkl47BF@protonmail.com - 2023-11-10 16:40 +0100
Re: upgrade to bookworm broke ssh x11 forwarding David Wright <deblis@lionunicorn.co.uk> - 2023-11-10 17:20 +0100
Re: upgrade to bookworm broke ssh x11 forwarding <tomas@tuxteam.de> - 2023-11-10 18:50 +0100
Re: upgrade to bookworm broke ssh x11 forwarding tomas@tuxteam.de - 2023-11-10 19:30 +0100
Re: upgrade to bookworm broke ssh x11 forwarding Dan Ritter <dsr@randomstring.org> - 2023-11-10 19:30 +0100
Re: upgrade to bookworm broke ssh x11 forwarding Vincent Lefevre <vincent@vinc17.net> - 2023-11-13 11:20 +0100
Re: upgrade to bookworm broke ssh x11 forwarding <tomas@tuxteam.de> - 2023-11-13 11:20 +0100
Re: upgrade to bookworm broke ssh x11 forwarding Jeffrey Walton <noloader@gmail.com> - 2023-11-09 19:30 +0100
Re: upgrade to bookworm broke ssh x11 forwarding fxkl47BF@protonmail.com - 2023-11-09 19:40 +0100
Re: upgrade to bookworm broke ssh x11 forwarding Jeffrey Walton <noloader@gmail.com> - 2023-11-10 01:00 +0100
csiph-web