Re: upgrade to bookworm broke ssh x11 forwarding

From	Dan Ritter <dsr@randomstring.org>
Newsgroups	linux.debian.user
Subject	Re: upgrade to bookworm broke ssh x11 forwarding
Date	2023-11-10 19:30 +0100
Message-ID	<HyEqt-4vln-7@gated-at.bofh.it> (permalink)
References	(4 earlier) <HyhDA-4hCV-5@gated-at.bofh.it> <HywCB-4qPH-5@gated-at.bofh.it> <HyAZz-4teJ-5@gated-at.bofh.it> <HyBLX-4tJT-1@gated-at.bofh.it> <HyDNL-4uTF-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

tomas@tuxteam.de wrote: 
> On Fri, Nov 10, 2023 at 03:32:53PM +0000, fxkl47BF@protonmail.com wrote:
> > On Fri, 10 Nov 2023, Vincent Lefevre wrote:
> > 
> > > On 2023-11-10 10:57:21 +0100, Michael wrote:
> > >> 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.
> > >
> > > It would be interesting to know why dropbear got installed
> > 
> > at sometime in the distance past i thought it would be handy
> > my initial ramdisk is set up so i can remotely unlock the filesystems
> 
> Wait a minute: dropbear is supposed to run in the initramfs, while
> sshd will be active afterwards, after pivot-root and all that, right?
> 
> Then I don't quite get why they should collide at all.

Because dropbear *can* be run as an ordinary sshd, and some
people do.

-dsr-

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