this post was submitted on 12 Apr 2025
102 points (97.2% liked)

Linux

53468 readers
787 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

On a server I have a public key auth only for root account. Is there any point of logging in with a different account?

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 2 points 1 week ago

It's rarely a good idea to log in as root, doubly so if it's a system with sensitive data or services that could easily be disrupted accidentally. And even more important if multiple users log in. How will you know who broke things to teach them if they don't log in first. The only time I log in to any system as root other than a test system is when I need to sftp to access files or some other system that doesn't have a way to elevate permissions.

[–] [email protected] 9 points 1 week ago

It's a bad practice to log in as root even for administrative tasks. You need to run numerous commands, some of hem can be potentially dangerous while not requiring root privileges. So normally you have an admin user in the sudo/wheel group and need to login to this account. Also, this adds some protection in case your key has leaked.

[–] [email protected] 3 points 1 week ago (1 children)

Is there any point of logging in with a different account?

When you edit & save a file as root, root takes ownership of that file. I personally don’t like having to run chmod or chown every time I make minor changes to something.

[–] [email protected] 7 points 1 week ago

No, that's not correct. If you create a new file as root, it will own that file. But editing an existing file doesn't change the owner or group of that file.

[–] [email protected] 18 points 1 week ago* (last edited 1 week ago)

A door with the best lock possible is still not as secure as no door at all

[–] [email protected] 13 points 1 week ago (1 children)

It's just another way of minimizing your attack surface. It's pretty much the same as hiding behind a barrier when being shot at, you stick yourself out as little as possible.

In the same way it also helps to change your SSH port to somewhere in the high numbers like 38265. This is anecdotal of course, but the amount of attacks on SSH went down by literally 99% by just changing the port like that

Then you accept only keys, you lock down root (so the username must be guessed as well) and yeah, you're safe.

[–] [email protected] 5 points 1 week ago

This is anecdotal

Not just anecdotal. The default SSH port gets hit by ridiculous numbers of bots because a lot of people don't bother to change it. This will be true no matter what machine you're on. Hell, your desktop at home has probably been scanned quite a few times even if all you do is watch porn on it

[–] [email protected] 21 points 1 week ago (1 children)

That server's root access is now vulnerable to a compromise of the systems that have the private key.

[–] [email protected] -1 points 1 week ago (1 children)

Only the server should have the private key. Why would other systems have the private key?

[–] [email protected] 10 points 1 week ago (2 children)

The client has the private key, the server has the corresponding public key in its authorized keys file.

The server is vulnerable to the private key getting stolen from the client.

[–] [email protected] 1 points 1 week ago

For ssh they both have private and public keys. The server could be at risk of having it's own private key compromised if somebody breaks in, and vice versa a compromised client can lose its private key. The original wording made it sound like a compromised server would steal client keys.

Also passworded keys are recommended

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago) (1 children)

it is also vulnerable to whatever ssh exploits that can bypass the key

[–] [email protected] 2 points 1 week ago (1 children)

Finding an exploit in ssh is worth more than whatever your server has to offer though.

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago)

thats a good point. unless you forget to update it in a timely manner.

that includes most servers out there ime, so

[–] [email protected] 29 points 1 week ago

Zero-day exploits are security holes that exist and are used by bad actors, but aren't yet known to you, or anyone capable of closing the hole. The clock to patch the hole doesn't start running until the exploit is known: it stands at zero days until the good guys know it exists.

What zero-day exploits exist for ssh?

By definition, you don't know. So, you block root login, and hope the bad actor doesn't also know a zero-day for sudo.

[–] [email protected] -1 points 1 week ago

Well, with root enabled, the SSH server at least need to verify the key, no? It's wasting CPU power albeit tiny amount.

load more comments
view more: next ›