public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OpenSSH upgrade warning
Date: Tue, 10 Nov 2015 23:51:57 -0500	[thread overview]
Message-ID: <20151111045157.GA11729@waltdnes.org> (raw)
In-Reply-To: <56414A8C.1080701@gentoo.org>

On Mon, Nov 09, 2015 at 08:38:20PM -0500, Michael Orlitzky wrote
> A major upgrade to OpenSSH is being stabilized:
> 
>   https://bugs.gentoo.org/show_bug.cgi?id=555518
> 
> The default of PermitRootLogin for sshd in the new version is
> "prohibit-password". If you typically log in to the root account over
> SSH using a password, **IT'S GONNA BREAK**, and you won't be able to fix
> it remotely unless you have an account that can sudo to root.
> 
> To maintain the current behavior, set PermitRootLogin to "yes" before
> you upgrade, and then be careful not to wipe out sshd_config.

  Thanks for the info.  I'd doing an install on a machine at home, and I
ran into that.  Since I hadn't yet created a local user, there was
nowhere to sudo from.  Fortunately, it's all in one room, and a few
clicks of the KVM remote-switcher brought me to the actual machine,
where I could log in directly.  I now have my key on the installed
machine and can ssh in from my current machine.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications


  parent reply	other threads:[~2015-11-11  4:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10  1:38 [gentoo-user] OpenSSH upgrade warning Michael Orlitzky
2015-11-10  3:26 ` Jeff Smelser
2015-11-10  9:53   ` Alan Mackenzie
2015-11-10 10:02     ` Neil Bothwick
2015-11-10 10:05     ` Alan McKinnon
2015-11-10 14:47   ` Michael Orlitzky
2015-11-10 15:30     ` Alan McKinnon
2015-11-10 15:58       ` Michael Orlitzky
2015-11-10 16:13         ` J. Roeleveld
2015-11-10 16:26           ` Michael Orlitzky
2015-11-10 17:17             ` Michael Orlitzky
2015-11-10 20:52             ` wabenbau
2015-11-10 21:00               ` Michael Orlitzky
2015-11-10 21:11                 ` wabenbau
2015-11-10 21:23                   ` Michael Orlitzky
2015-11-10 21:48                     ` Dale
2015-11-10 23:22                       ` wabenbau
2015-11-10 18:26         ` Alan McKinnon
2015-11-10 18:55           ` Michael Orlitzky
2015-11-10 19:00             ` Jeff Smelser
2015-11-10 19:17               ` Michael Orlitzky
2015-11-10 19:20                 ` Jeff Smelser
2015-11-10 19:23                 ` Stanislav Nikolov
2015-11-10 19:25                   ` Michael Orlitzky
2015-11-10 19:32                     ` Stanislav Nikolov
2015-11-10 19:38                       ` Michael Orlitzky
2015-11-10 19:31                   ` Michael Orlitzky
2015-11-10 19:37                     ` Stanislav Nikolov
2015-11-10 19:37                     ` Jeff Smelser
2015-11-11  4:51 ` Walter Dnes [this message]
2015-11-12 12:05 ` Rich Freeman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151111045157.GA11729@waltdnes.org \
    --to=waltdnes@waltdnes.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox