Re: Upgrade from 13.0 to 13.1, sshd_config broken

On Mon, Sep 26, 2022 at 12:03 PM sake <sake@saketec.com> wrote:

> Hi,
>
> So I did the upgrade and everything is running good now. But I had to
> log in via console and repair the sshd_config file.
>
> --- snip sshd_config-broken ---
>
> # Set this to 'no' to disable PAM authentication, account processing,
> # and session processing. If this is enabled, PAM authentication will
> <<<<<<< current version
> # be allowed through the ChallengeResponseAuthentication and
> # PAM authentication via ChallengeResponseAuthentication may bypass
> =======
> # be allowed through the KbdInteractiveAuthentication and
> # PasswordAuthentication.  Depending on your PAM configuration,
> # PAM authentication via KbdInteractiveAuthentication may bypass
> # the setting of "PermitRootLogin without-password".
>  >>>>>>> 13.1-RELEASE
> # If you just want the PAM account and session checks to run without
> <<<<<<< current version
> # and ChallengeResponseAuthentication to 'no'.
> =======
> # PAM authentication, then enable this but set PasswordAuthentication
> # and KbdInteractiveAuthentication to 'no'.
>  >>>>>>> 13.1-RELEASE
>
> --- snip ---
>
> It looks like some comments haven't received the leading #  I haven't
> found any similar error in the internet regarding the upgrade process.
> Seems like I'm the only one having this issue.
>
> Can anyone explain to me why this happened and what I can do to prevent
> this the next time?
>
> Thanks in advance
> cheers
> sake.
>
>
This did bite me as well when I upgraded, but it only happened with the
sshd_config.
Please report this as a bug and it will be fixed.
I did not remember to report it. I was luck that I had a web-based SSH
setup on the server when this bit me else I'd have been locked out .


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)