Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #263300

Re: upgrade to bookworm broke ssh x11 forwarding

From fxkl47BF@protonmail.com
Newsgroups linux.debian.user
Subject Re: upgrade to bookworm broke ssh x11 forwarding
Date 2023-11-09 19:40 +0100
Message-ID <Hyi6B-4hN1-3@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

Show all headers | View raw


On Thu, 9 Nov 2023, Greg Wooledge wrote:

> On Thu, Nov 09, 2023 at 04:59:32PM +0000, fxkl47BF@protonmail.com wrote:
>> now it makes a bit more sense
>> sshd isn't running
>> for some reason the upgrade switched to dropbear
>> is this a new thing for bookworm
>> is there a reason i shouldn't disable dropbear and use sshd
>
> No, this is not a normal phenomenon for bookworm upgrades.  I've never
> heard of it happening to anyone before.
>
> You should be able to reinstall openssh-server and remove dropbear
> and get back to normal, unless there's something else unusual in
> your package set.  As this situation is (AFAIK) unique to your system,
> you'll have to be the one to try it and see what happens.
>

openssh was installed just not running
i stopped and disabled dropbear and started sshd
all is right for now
thanks

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


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