Re: Problems with ssh after upgrade to F36

2022-05-12 Thread Jouk
Setting the crypto policies dis not help. So I will have to install the f35 version. Jouk ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: h

Re: Problems with ssh after upgrade to F36

2022-05-12 Thread stan via users
On Thu, 12 May 2022 08:43:39 +0200 (CEST) "Jouk Jansen" wrote: > L.S. > > After upgrading to F36 I have problems accessing the F36 server with > ssh form OpenVMS machines. The problem is probably (again) that > OpenVMS only supports "old" keys. In the past I added the following [snip] > This wor

Problems with ssh after upgrade to F36

2022-05-11 Thread Jouk Jansen
L.S. After upgrading to F36 I have problems accessing the F36 server with ssh form OpenVMS machines. The problem is probably (again) that OpenVMS only supports "old" keys. In the past I added the following to my sshd_config: Ciphers +aes128-cbc MACs umac-64-...@openssh.com,umac-128-...@openssh.c

Re: SSH after upgrade

2019-10-07 Thread Marko Vojinovic
On Mon, 07 Oct 2019 15:25:28 +0200 Jakub Jelen wrote: > On Mon, 2019-10-07 at 14:13 +0200, Marko Vojinovic wrote: > > On Mon, 07 Oct 2019 10:38:32 +0200 > > Can you please elaborate what were the "many practical reasons" that > > prevented this from being changed for the last 5 years? And why are

Re: SSH after upgrade

2019-10-07 Thread Jakub Jelen
On Mon, 2019-10-07 at 14:13 +0200, Marko Vojinovic wrote: > On Mon, 07 Oct 2019 10:38:32 +0200 > Jakub Jelen wrote: > > > On Mon, 2019-10-07 at 02:53 +0200, Marko Vojinovic wrote: > > > On Mon, 7 Oct 2019 10:21:03 +1100 > > > Cameron Simpson wrote: > > > > On 07Oct2019 01:00, Marko Vojinovic wr

Re: SSH after upgrade

2019-10-07 Thread Marko Vojinovic
On Mon, 07 Oct 2019 10:38:32 +0200 Jakub Jelen wrote: > On Mon, 2019-10-07 at 02:53 +0200, Marko Vojinovic wrote: > > On Mon, 7 Oct 2019 10:21:03 +1100 > > Cameron Simpson wrote: > > > On 07Oct2019 01:00, Marko Vojinovic wrote: > > > > On Sun, 06 Oct 2019 18:05:02 +0200 > > > > alcir...@gmail.c

Re: SSH after upgrade

2019-10-07 Thread Jakub Jelen
On Mon, 2019-10-07 at 02:53 +0200, Marko Vojinovic wrote: > On Mon, 7 Oct 2019 10:21:03 +1100 > Cameron Simpson wrote: > > > On 07Oct2019 01:00, Marko Vojinovic wrote: > > > On Sun, 06 Oct 2019 18:05:02 +0200 > > > alcir...@gmail.com wrote: > > > > It could it be related to this change: > > > >

Re: [SOLVED] SSH after upgrade

2019-10-07 Thread Earl A Ramirez
> > Please, do not advise this as a general solution. The correct solution > is to setup public key authentication or use different user > Isn't cockpit installed by default on servers since that is the future directive? > ___ users mailing list -- users

Re: [SOLVED] SSH after upgrade

2019-10-07 Thread Jakub Jelen
On Sun, 2019-10-06 at 11:15 -0500, Mike Chambers wrote: > On Sun, 2019-10-06 at 18:05 +0200, alcir...@gmail.com wrote: > > On Sun, 2019-10-06 at 10:46 -0500, Mike Chambers wrote: > > > Upgraded server from Fedora 30 to 31 (updated to present), and > > > ssh > > > into > > > that server works fine a

Re: SSH after upgrade

2019-10-06 Thread Marko Vojinovic
On Mon, 7 Oct 2019 10:21:03 +1100 Cameron Simpson wrote: > On 07Oct2019 01:00, Marko Vojinovic wrote: > >On Sun, 06 Oct 2019 18:05:02 +0200 > >alcir...@gmail.com wrote: > >> It could it be related to this change: > >> https://fedoraproject.org/wiki/Releases/31/ChangeSet#Disable_Root_Password_Log

Re: SSH after upgrade

2019-10-06 Thread Cameron Simpson
On 07Oct2019 01:00, Marko Vojinovic wrote: On Sun, 06 Oct 2019 18:05:02 +0200 alcir...@gmail.com wrote: It could it be related to this change: https://fedoraproject.org/wiki/Releases/31/ChangeSet#Disable_Root_Password_Login_in_SSH As a side question --- I remember that this was the default fo

Re: SSH after upgrade

2019-10-06 Thread Marko Vojinovic
On Sun, 06 Oct 2019 18:05:02 +0200 alcir...@gmail.com wrote: > On Sun, 2019-10-06 at 10:46 -0500, Mike Chambers wrote: > > Upgraded server from Fedora 30 to 31 (updated to present), and ssh > > into > > that server works fine as normal user, but no longer lets me login > > as root. I can login as

Re: SSH after upgrade

2019-10-06 Thread George N. White III
On Sun, 6 Oct 2019 at 13:05, wrote: > On Sun, 2019-10-06 at 10:46 -0500, Mike Chambers wrote: > > Upgraded server from Fedora 30 to 31 (updated to present), and ssh > > into > > that server works fine as normal user, but no longer lets me login as > > root. I can login as root from the server ma

Re: SSH after upgrade

2019-10-06 Thread Patrick O'Callaghan
On Sun, 2019-10-06 at 10:46 -0500, Mike Chambers wrote: > Upgraded server from Fedora 30 to 31 (updated to present), and ssh into > that server works fine as normal user, but no longer lets me login as > root. I can login as root from the server machine itself, and can > login via su - but just ca

Re: [SOLVED] SSH after upgrade

2019-10-06 Thread Mike Chambers
On Sun, 2019-10-06 at 18:05 +0200, alcir...@gmail.com wrote: > On Sun, 2019-10-06 at 10:46 -0500, Mike Chambers wrote: > > Upgraded server from Fedora 30 to 31 (updated to present), and ssh > > into > > that server works fine as normal user, but no longer lets me login > > as > > root. I can login

Re: SSH after upgrade

2019-10-06 Thread alciregi
On Sun, 2019-10-06 at 10:46 -0500, Mike Chambers wrote: > Upgraded server from Fedora 30 to 31 (updated to present), and ssh > into > that server works fine as normal user, but no longer lets me login as > root. I can login as root from the server machine itself, and can > login via su - but just

SSH after upgrade

2019-10-06 Thread Mike Chambers
Upgraded server from Fedora 30 to 31 (updated to present), and ssh into that server works fine as normal user, but no longer lets me login as root. I can login as root from the server machine itself, and can login via su - but just cant' from ssh. Any ideas what changed or got replaced so revert