So what is the alternative? Having rm ignore all files and directories starting with a dash?
There is no alternative right now because too much software depends on this behavior, unfortunately (the bane of software).. Preferably, programs should be responsible for expanding wildcards themselves, which can be a function provided by the operating system via a function call. This has other repurcussions, like that some programs will accept wildcards and others won't, but it will at least be correct.
Every proper Unix environment has LDAP servers providing globally unique IDs for users and groups for this reason, just like every proper Windows environment has a domain controller.
Yep, but this means creating user accounts which are machine-local, but linked to a central server which introduces a huge number of unnecessary steps - especially when we take shared network resources into account.
How so? They're hashed and salted, what more do you want?
For one, people could stop using shadow-files and instead go with more standardized modern approach which is available on *nix, except people don't use them because it's more complicated than just using htpasswd. I don't think people use this system because it's smart or secure, it's a choice of simplicity.
That's not true, passwd will give you a list of algorithms to choose from but plain passwords are not supported.
Passwd is for local system user accounts. You're right, plain text is not supported there. But a very commonly used method for programs to store their own users (like a server application) is htpasswd which does support plain text. Its default is also MD5 which is well known to be too easy for GPU's to bruteforce to be considered secure.
Yes, NTLM was a security nightmare.. Which is why it was replaced in 2001 :P The bug was discovered essentially 9 years after NTLM was officially replaced with Kerberos (of course, Windows is largely bound to a corporate culture, so replacing it takes a long long time)
Unix has had the same system calls for authentication and authorisation for ages. Not sure how it could be any easier. Also see PAM vs. no chance to ever customise the authentication and authorisation on Windows ever.
Windows uses standardized authentication methods; Kerberos and LDAP. There are many alternatives to authentication for Windows, Citrix being one of the more popular.
Not really. iOS yes, it doesn't really allow access to the filesystem. On OSX, the filesystem is perfectly accessible by the user. Open a terminal on OSX and look around.
The finder will not show you the entire file system unless you basically wring its arms behind its back. The terminal is only used by people with non-Mac backgrounds. I have an example here from a personal experience actually.. I was going to demo a site for a customer, and we used all internal IP's for our demonstration (we had actually arranged a meeting for them to come look at it, but they suddenly said they hadn't time), so I had to get them to add a line in the hosts file. So they said I could talk to their "Mac and network expert". He didn't know what the hosts file was, and he most certainly had no idea that there was a root directory on the computer that contained the /etc folder. He had no idea. You can access the entire filesystem on a Mac, but it actively hides most of it. And for good reason.. How would a non-techie have any idea what /opt, /etc, /proc, /bin, /sbin and /var are? I've heard multiple stories of people deleting the /bin folder because they think it's the recycling bin (yes, seriously).
Personal preference I guess. I much prefer ls | grep to get-system-files-of-current-directory-cmdlet | search-for-pattern-cmdlet --from-property system.files.filename or whatever it is.
Yeah, well now that you're used to it and you on beforehand know what you need to type, it's fine. I also prefer the short-hands (which is why Powershell conveniently has aliases for them). But I don't think it's a good idea generally to create systems where you have to know things purely by means of repetition. There might be some middle-ground between Unix and Powershell in this instance..
By the way, thank you for taking the time to respond in detail. I enjoy discussions like this.
Yep, but this means creating user accounts which are machine-local, but linked to a central server which introduces a huge number of unnecessary steps
No, that's not correct. Of course LDAP accounts are never created locally, that would be stupid. If anybody does that, punch them. LDAP accounts are pulled from the LDAP upon request (logins etc) and are cached (on RHEL, sssd is responsible for that).
stop using shadow-files and instead go with more standardized modern approach which is available on *nix, except people don't use them because it's more complicated than just using htpasswd
htpasswd is not the same as shadow, just so you know. Again, any proper Unix environment would use a directory service such as LDAP with optional Kerberos. For example, when our users access a web interface running on an Unix server they'll authenticate themselves using the same Kerberos credentials that they are using on their Windows clients and authorise themselves by having the server query the LDAP for their roles and memberships.
Its default is also MD5 which is well known to be too easy for GPU's to bruteforce to be considered secure
Yes, MD5 is too fast to be a good algorithm (also collisions have been demonstrated) - however, they are always salted which will seriously annoy any attacker. Also, all modern Linuxes I know of use SHA1, not MD5.
Yes, NTLM was a security nightmare.. Which is why it was replaced in 2001 :P
Yes, and if used in their default fashion they work very well. If customisation is needed, it's a medium level nightmare. If you've only ever worked in windows based environments you probably don't know what I mean by that because you (and software vendors) haven't ever thought about expanding or customising this part of the operating system because it mostly can't be done. It's AD with LDAP + Kerberos and nothing else (not that AD is bad, quite the contrary, it's pretty good).
Compared with PAM however (which is a combination of authentication and authorisation modules hence its name "Pluggable Authentication Modules" ) it's very inflexible and static. But don't think that customising PAM will result in massive amounts of pain for the developers, because their system calls remain the same. The accounts can be local, they can be on LDAP, they can be on NIS (don't do that though) or they can be engraved on a tree stem in a garden and read by an OCR capable webcam accessed over a REST interface over any network, it mostly doesn't matter from the point of view of the developer. If applications roll their own home made authentication/authorisation software you should punch them in the face.
The finder will not show you the entire file system unless you basically wring its arms behind its back
Yes, that is true. I can only guess why Apple does this, perhaps it's because they think it's better for usability. I've always hated this (I don't have a mac, but many of my colleagues do). If finder can find your files it works well, but god forbid you never actually need to find your files where they really are, you're lost.
He didn't know what the hosts file was, and he most certainly had no idea that there was a root directory on the computer that contained the /etc folder. He had no idea.
Understandable. I'd be very surprised if the local "knows a bit about computers" guy of a random company knew of any operating system's hosts file (or even what DNS is).
heard multiple stories of people deleting the /bin folder because they think it's the recycling bin
Oh god. Perhaps that's why Apple is trying to hide the filesystem from the users.
2
u/Cuddlefluff_Grim Dec 07 '15
There is no alternative right now because too much software depends on this behavior, unfortunately (the bane of software).. Preferably, programs should be responsible for expanding wildcards themselves, which can be a function provided by the operating system via a function call. This has other repurcussions, like that some programs will accept wildcards and others won't, but it will at least be correct.
Yep, but this means creating user accounts which are machine-local, but linked to a central server which introduces a huge number of unnecessary steps - especially when we take shared network resources into account.
For one, people could stop using shadow-files and instead go with more standardized modern approach which is available on *nix, except people don't use them because it's more complicated than just using htpasswd. I don't think people use this system because it's smart or secure, it's a choice of simplicity.
Passwd is for local system user accounts. You're right, plain text is not supported there. But a very commonly used method for programs to store their own users (like a server application) is
htpasswdwhich does support plain text. Its default is also MD5 which is well known to be too easy for GPU's to bruteforce to be considered secure.Yes, NTLM was a security nightmare.. Which is why it was replaced in 2001 :P The bug was discovered essentially 9 years after NTLM was officially replaced with Kerberos (of course, Windows is largely bound to a corporate culture, so replacing it takes a long long time)
Windows uses standardized authentication methods; Kerberos and LDAP. There are many alternatives to authentication for Windows, Citrix being one of the more popular.
The finder will not show you the entire file system unless you basically wring its arms behind its back. The terminal is only used by people with non-Mac backgrounds. I have an example here from a personal experience actually.. I was going to demo a site for a customer, and we used all internal IP's for our demonstration (we had actually arranged a meeting for them to come look at it, but they suddenly said they hadn't time), so I had to get them to add a line in the
hostsfile. So they said I could talk to their "Mac and network expert". He didn't know what thehostsfile was, and he most certainly had no idea that there was a root directory on the computer that contained the/etcfolder. He had no idea. You can access the entire filesystem on a Mac, but it actively hides most of it. And for good reason.. How would a non-techie have any idea what/opt,/etc,/proc,/bin,/sbinand/varare? I've heard multiple stories of people deleting the/binfolder because they think it's the recycling bin (yes, seriously).Yeah, well now that you're used to it and you on beforehand know what you need to type, it's fine. I also prefer the short-hands (which is why Powershell conveniently has aliases for them). But I don't think it's a good idea generally to create systems where you have to know things purely by means of repetition. There might be some middle-ground between Unix and Powershell in this instance..
Likewise :)