4 ms·
Lol there is a technology called LDAP, avoiding storing passwords anywhere on the server. Don't go and reinvent the wheel if there are far better technologies
by mschuster91 11y ago
Lol there is a technology called LDAP, avoiding storing passwords anywhere on the server.
Don't go and reinvent the wheel if there are far better technologies widely adopted!
- seletskiy 11y agoLDAP is a remote login provider, works through PAM-module and is nowhere near "lightweight" as it supposed to be. Also, it stores only one hash for original password, not many. If you do not have cached version of auth info on the server and remote login provider is offline, you have big problems. I can't imagine a single reason why I will do remote login service for the root user on the front-end load balancing server of a high load project. shadowd is not remote login provider, it only serves /etc/shadow hashes for local and possibly offline use.
- KaiserPro 11y agoSorry but no, this is just not the right way to do it. with SSSD there is no excuse for not using AD/LDAP. Having done both, shipping /etc/passwd and using AD, its far more effective, secure, and crucially stable to have LDAP/AD as the single source of truth. Its not like its difficult anymore, you can even buy in AD from AWS. (just don't try and do machine accounts, you're better off using puppet/ansible for that sort of thing.) Think about it, you wouldn't ship /etc/hosts anymore would you? why do the same with user accounts.
- seletskiy 11y agoI guess, you didn't address any single issue I mentioned. I don't see, why it's far more effective, secure and stable to have proposed stack as the single source of truth. Given the example, that we do not have LDAP stack already integrated into dev/ops process, it's seems like an overblow for me to integrate it from scratch because of it's massive configuration, maintenance and ugly design. The right way to do for me is simplicity and using tools, that offers solution for small problems; using overcomplicated bloatware doesn't seems to be right way to do, especially now, when we have that rapid growth in software development. I would ship /etc/hosts if there will be major performance impact of doing millions of DNS queries across network under high load. It depends on the concrete case.
- KaiserPro 11y agoSSSD cache for as long as you need. If you don't have an auth server or network then you are in deeper trouble. (even AD can be n-tier active active) AD/LDAP allows SSO for everything ssh, bash, gmail, AWS console, etc. Because its a centralised, when someone leaves, or their account is compromised then its one place to change it. Crucially its one source of truth across the entire estate, not just for "servers" or "desktops" As for "massive configuration, maintenance and ugly design." Its really not. Also purity of design is not getting the job done. Your approach is ok if you only have a few servers and a handful of users. The point of ansible/puppet/salt/$other playbooks is that 90% of the work is done for you. All you have to do is input your users, and roll out the SSSD conf (after testing) Even by hand openLDAP isn't that hard. As for the rhetorical question about /etc/hosts you wouldn't because thats what nslcd/sssd/Program caches are for.
- brazzledazzle 11y agoI think a LDAP/LDAP+Kerberos backend is more secure for user accounts but I'd agree that the root password doesn't belong in it. But personally I think disabling the root account (like OS X or Ubuntu) makes the most security sense. You can always get into the account in single user mode.
- tptacek 11y agoThe rules for "Show HN's" aren't the same as for the rest of the site, and a negative comment staring with "Lol" probably wouldn't clear the civility bar even for a normal thread. https://news.ycombinator.com/showhn.html https://news.ycombinator.com/showhn.html
- striking 11y agoI'm not certain that I'd agree with you about this comment. Which rule does it break? The poster believes this technology already exists and started a relevant discussion about the pros and cons of the existing implementations. I don't think you could consider "Lol" so offensive that the post should disappear.
- morganvachon 11y agoI didn't find it offensive, but it did come across as childish and ignorant, and therefore I stopped reading at that first word. Opening a discussion by laughing in the face of the other person (or group of people in this case) reeks of ignorance, even if the person doing so is actually an expert.
- striking 11y agoIf the poster wants to be taken seriously, that's his or her choice. But however ignorant and childish it is, it's still something someone could say "in a face-to-face conversation" as per the rules. I'm not arguing this was a nice thing to say, I'm arguing it shouldn't disappear. We have the power to downvote people when they say things that don't fit in the community but pass a very basic civility guideline. Comments that aren't substantive should disappear. Comments potentially with some meat but offensively presented should just be downvoted, in my opinion.
- tptacek 11y agoThis is normally the case on HN, but it isn't the case on "Show HN's". The special "Show HN" guidelines were introduced by 'dang in a thread about a year ago; you should track that thread down and read the whole thing for context, or just take my word for it. :) I don't generally want to be the HN rules police, but this particular rule is a very good one, which took the site some time to be adopted, and I think it's worth speaking up for.
- mrmondo 11y agoWhile I agree with no reinventing the wheel unless there's good reason to do so, LDAP is a bloated, over complicated piece of $#!£¥.
- KaiserPro 11y agoI'm not saying that LDAP is simple, but compared to jenkins, its a delight to setup (although openLDAP is just stupid, why keep the config inside the LDAP instance it's self(and yes I know the justification....))
- STRML 11y agoAgreed, dealing with LDAP would be far, far easier if there were a single monolithic config file (or hell, even a folder full of config files) instead of the unbelievably complex LDIF process. LDAP, or LDAP + Radius (for integration with a second factor) is still a dynamite technology and pretty much required once a network / team reaches a certain size. There's definitely demand for an "EasyLDAP" or the like that offers sane defaults and easy config for deployment in a cloud environment.
- stephenr 11y agoYou can use the config file option - it's just not the default anymore in openldap. Also, having config in the db means you can make online configuration changes that take effect instantly and are replicated to all other replicas.
- rgbrenner 11y agoThe author put a lot of work into this (I assume). "Lol" and then dismissing their work isn't very nice. You should ask yourself if this is the type of comment you would say in person (because the author is likely reading these comments). Perhaps a more productive comment would ask "what advantages this has over LDAP"
- Galanwe 11y agoThat is not a really wise strategy. LDAP is fine for general user accounts when you need to give access to employees on some shared hosts. For production hosts, you often don't want a SPOF such as LDAP for accounts. And I promise you this, the day your LDAP or network will go down, if you don't have at least a single local user to ssh with, you'll regret it.