8 ms·
> Every fresh server install, I have to make up a meaningless string called the 'login' If you are only doing the occasional install then this really shouldn't
by dspillett 15y ago
> Every fresh server install, I have to make up a meaningless string called the 'login'
If you are only doing the occasional install then this really shouldn't be a great hardship. If you are installing many servers you should have this part automated. And ti shouldn't be meaningless either. I think you are doing it wrong.
> Once upon a time, I could use the well known admin login 'root'.
You still can. root login can always be reenabled if you want it that badly. There is also "sudo su" (unless explicitly disabled by your admins) to avoid repeated invocations of sudo while you are performing a long admin task.
> - Here's a better way of doing it:
> Give me a server distro where I don't need a 'login'.
No, no, and thrice no. Far too many newbies will leave it in that state and get hacked to buggery in short order. Even if it is only for local console logins, I'd consider it a bad idea.
No matter how inconvenient it is, server install should default to an insecure state and allowing access without authentication is such a state.
Live CDs often do this, but they are not production systems.
> Meanwhile, why is apache pretending to be a 'user'
Well that much is a valid point. There has been work in this area but non of it has made its way to default setups of most unix-a-like systems.
- divtxt 15y agoHere's a simple thought experiment: Imagine a distro that changed the terms 'login/password' to 'password1/password2' No commands you type would change, but you'd wonder why the password is in 2 parts. That's how redundant user is!
- seabee 15y agoCute, except that password1 has to be unique. Hope you like confusing some of your users. You'd be better off getting rid of the login altogether and using a GUID. People still share computers, you know.
- divtxt 15y agoUniqueness is not an issue - see my original point - we only create one admin user on servers! Imagine a team of 3 people running a SaaS webapp on 3 web servers & 1 db server. I guarantee no one will waste their time creating 3 'users' on each server i.e. 3x4 = 12 'users' on that cluster.
- ebiester 15y agoIt's really nice having separate users in production for a server. That way, you log sudo and know who issued an admin command. But in a larger system, you don't worry about setting them up on each server; instead, you rely on LDAP. Unix is the LISP of server operating systems. It's a multiplier. In return, it demands much more from the operator. This is not ideal for a desktop system. It's amazing when you have an admin who knows his shit.
- divtxt 15y agoLDAP is a sensible suggestion. Why can't we still kill the local login i.e. directly map LDAP user -> permissions instead of LDAP user -> local 'user' -> permissions.
- ebiester 15y agoToday, it could probably be done. I'll have to think about the implications.
- bdunbar 15y agoWhy can't we still kill the local login If LDAP ever goes down you might want to retain the ability to login to your box. I ran into a problem similar to this on a recent DR exercise. Active Directory (an LDAPish service) was down. Was going to be down for a while. If I could get into my three Windows hosts I could re-jigger the service account for $APP from the AD user to a local account, start things up. I couldn't login to the servers: my .admin account was in AD. No one had any idea what the local administrator account could be. We were just .. stuck .. until AD came up. I could have booted the system a rescue disk (linux) and edited the SAM to change the password. Didn't happen then for complicated reasons. And one shouldn't have to resort to heroic methods to get local access back. And can you imagine doing that for hundreds of hosts?
- nupark2 15y agoAnd can you imagine doing that for hundreds of hosts? This is why you: - Always provide redundant, network-local LDAP servers so that LDAP doesn't go down. - Wire up remotely accessible serial consoles that provide emergency-level local root access. You can attach a modem to the serial console systems, or a hardline (which is what I did at a previous job) between your data center and offices. We had a fixed 'role' account for the serial console systems, but it existed only for the purpose of emergency access, could only be accessed from specific local networks (we divided different classes of employees into different VLANs), and the knowledge of the password could be constrained to those that needed rare "server fell over" access.
- drblast 15y agoThere's a security problem with that: $ chpasswd maybeUniqueString Error: maybeUniqueString already in use. $ su maybeUniqueString LOGIN OK, PROCEED TO EXPLOIT ME So username and login are not totally redundant.
- moultano 15y agoIsn't that exactly the amount of stuff they would already have to guess?
- xyzzyz 15y agoNo, you can have many users, and this way you try to guess everyone's password at the same time. Also, sadly, passwords tend to be repetitive, so now someone can accidentally guess someone else's password.
- burgerbrain 15y agoWell, as the old saying goes, those who do not know Unix are doomed to reinvent it.... poorly. I am rarely surprised anymore by the bad ideas I see people come up with.
- divtxt 15y agoSounds like you've misunderstood that either password1 or password2 will get you in! I didn't change any behavior - just the UI strings. So you need both! i.e: $ su maybeUniqueString1 Enter Password2:
- elehack 15y ago> There is also "sudo su" (unless explicitly disabled by your admins) to avoid repeated invocations of sudo while you are performing a long admin task. You can also do 'sudo -s', which keeps you in your normal user's shell. It's pretty slick.
- dspillett 15y agoYou learn something new every day. Thanks for the tip, I'll give that a try at some point.