CKB:SSH Root Access Restriction openSUSE Leap 16.0: Unterschied zwischen den Versionen
(Creating ssh root access issue page) |
K (Changing reference to problem statement.) |
||
| (3 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt) | |||
| Zeile 1: | Zeile 1: | ||
==Applies To== | ==Applies To== | ||
OpenSUSE upgrade performing from version Leap 15.6 to Leap 16.0 | OpenSUSE upgrade performing from version Leap 15.6 to Leap 16.0. | ||
==Problem== | ==Problem== | ||
After upgrading to openSUSE Leap 16.0, SSH root login with a password no longer works. Customers who previously accessed their systems remotely as root via password authentication will be locked out after the upgrade. | After upgrading to openSUSE Leap 16.0, SSH root login with a password no longer works. Customers who previously accessed their systems remotely as root via password authentication will be locked out after the upgrade. | ||
'''Reference:''' [https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/16.0/html/release-notes-leap-160/index.html#jsc-PED-4965 openSUSE Leap 16.0 Release Notes – JSC-PED-4965] | |||
==Cause== | ==Cause== | ||
| Zeile 28: | Zeile 30: | ||
## <code>usermod -a -G wheel testuser</code> | ## <code>usermod -a -G wheel testuser</code> | ||
# Verify the user can log in via SSH and run <code>sudo</code> commands before upgrading. | # Verify the user can log in via SSH and run <code>sudo</code> commands before upgrading. | ||
Aktuelle Version vom 19. Februar 2026, 15:45 Uhr
Applies To
OpenSUSE upgrade performing from version Leap 15.6 to Leap 16.0.
Problem
After upgrading to openSUSE Leap 16.0, SSH root login with a password no longer works. Customers who previously accessed their systems remotely as root via password authentication will be locked out after the upgrade.
Reference: openSUSE Leap 16.0 Release Notes – JSC-PED-4965
Cause
openSUSE Leap 16.0 disables password-based SSH root login by default, in line with modern Linux security standards. This change reduces the risk of brute-force attacks targeting the root account.
Solution/Workaround
One of the following must be configured before performing the upgrade:
Option 1 — SSH Key Authentication for Root (Recommended) Replace password login with key-based authentication for the root user.
- On the client machine, generate an SSH key pair (if not already available):
ssh-keygen -t ed25519
- Copy the public key to the target server:
ssh-copy-id root@<server-ip>
- Verify key-based login works before upgrading:
ssh root@<server-ip>
Option 2 — Create a Non-Root User with sudo Privileges Use a non-root account for remote access post-upgrade.
- Create a new user:
useradd -m -s /bin/bash -c "Test User" testusersudo passwd testuser
- Grant sudo privileges:
usermod -a -G wheel testuser
- Verify the user can log in via SSH and run
sudocommands before upgrading.