On Sat, Aug 27, 2022 at 07:49:17AM +0100, Tim Woodall wrote: > On Sat, 27 Aug 2022, tomas@tuxteam.de wrote: > > > On Sat, Aug 27, 2022 at 11:22:09AM +1000, David wrote: > > > On Sat, 27 Aug 2022 at 10:27, Greg Wooledge <greg@wooledge.org> wrote: > > > > > > > Has anyone managed to reproduce the OP's results, either getting > > > > "interactive" from a bash -c call, or seeing *any* evidence that > > > > /etc/bash.bashrc or ~/.bashrc is sourced from a bash -c call? > > > > > > On Debian 11, when I create a test user, login on a console as that > > > user, and duplicate the recipe provided in the original message[1], > > > the reported problem does NOT occur: > > > > Aha... > > > > so main suspects are now ~/.bash_profile ~/.inputrc or some exported > > environment lying around... > > > > Cheers > > > > This just gets weirder and weirder. > > It looks like it's related to logging in with ssh: This could be a giveaway. I tried David's test from upthread [1] while logged in through SSH and the results are (still) the same as his. But... my SSH is vanilla Buster, not patched, so... [...] > Downgrading ssh back to the version from bullseye shows it's not my > local changes: ...but then, this makes it the more interesting :-) Have you tried David's test? Cheers [1] Message-ID: <[🔎] CAMPXz=pncfSExnKe7R7UaWVWK+0_BWzgioJyBZovFpBcp2cp_A@mail.gmail.com> -- t
Attachment:
signature.asc
Description: PGP signature