Also, < in [ .. ] is nonstandard, but in the funny way that Ksh and Zsh don't seem to support it, while Dash, Yash and Busybox seem to do(?) And while Bash has it, test from GNU coreutils doesn't.
Modifying most of the files in /etc leaves you open to them being replaced during OS updates. That's why most of the ones you usually need to change have the facility to add files to a directory instead.
If you look in /etc you will see a directory called sudoers.d and the last line of the sudoer...
I just don't like the things macos does to mess with standard unix-y things. RABBLE RABBLE RABBLE
I don't want to have to disable sip to perform a basic function of unix
The reason people prefer mac is because it's a well (debatable) developed desktop operating system with unix under the hood, but the more of that unix they take away the less incentive to use it
I'm trying to add a new word file to /usr/share/dict/ on macOS Catalina v 10.15.1 and I'm getting:
$ sudo touch /usr/share/dict/mywords
touch: /usr/share/dict/mywords: Operation not permitted
# touch /usr/share/dict/mywords
touch: /usr/share/dict/mywords: Operation not permitted
I've read some...
Other BSDs, like OpenBSD, have elaborate merging tools to handle locally modified files when the system is updated. Sometimes, updates conflict with local changes, and a manual fix has to be made.
I want to be the owner of /usr/local or at least have write permissions to it. I can make those changes but they are automatically reverted every time I reboot
I own all my sudirectories under /usr/local, and can write to them. This is on both Catalina and Big Sur. I don't see the ownership or permissions change on reboots or updates.
I actually do own most of the directories under /usr/local though now that I'm looking at it, it's just /usr/local/bin that keeps reverting for some reason
I'm definitely not the only person with that problem though because when you google it you find a lot of people complaining about it because it breaks homebrew
and people recommend changing the directory where homebrew installs to ~/usr/local/bin but just thinking about having a ~/usr/local/bin makes me throw up in my mouth a bit
and again I don't want my operating system to "protect" me. I want to do dangerous stuff
I hmmm i now dont know what to do after the threat of ban if i post more questions. do all the stack exchange communities socially interact? i feel like if its based on what people have said i said in other communities that i specifically joined to make fun of when im drunk shouldnt affect my access here
i just wanna know how you can retrive information about the nature of how ports are filtered and for which services they are used if it is possible with nmap
@jesse_b A good system will be designed to allow you to do what you want, while still providing protection (e.g. mandatory access controls). But an unprotected system is bad.
@AdamL A service can listen to any port. There are a number of port numbers that are associated with particular services though, like SSH on port 22 and DNS on port 53. Have a look at your /etc/services file for a fuller list.
Also, although in theory you could use port 0, in practice that's used to mean "any port" by OS' network API, so no one actually listens on port 0. But it may be useful for covert comms. :P
@AdamL You can find out which ports are open generally, but you can't always find out what service is running unless you can talk to it (although you can guess what's running behind it if it's a common port). But port 1234 with an HTTP server that only allows certain IPs to connect won't be shown to you as HTTP by nmap.
@AdamL Not all SE communities interact with each other, at least not often.
Oh, MacOS... Yeah, that's not well protected. :P
@Kusalananda OpenBSD is great at that! Gentoo also handles merging configs well.