For all forms of hacking services, talk to darkcracker@protonmail.com
Use zsh as the default shell on your Mac
71–80 of 252 posts
Re: Use zsh as the default shell on your Mac
#72For those wondering why Apple is allergic to GPLv3 code: there is a clause in the license requiring you provide a way to run modified version of the software which would require Apple to let users self sign executables.
> let users self sign executables
Which is to say, "let users run their own software". There's value in formal authentication of third party software as a default configuration, but let's not pretend that's what lockdown is about.
Re: Use zsh as the default shell on your Mac
#73For those wondering why Apple is allergic to GPLv3 code: there is a clause in the license requiring you provide a way to run modified version of the software which would require Apple to let users self sign executables.
> let users self sign executables Which is to say, "let users run their own software". There's value in formal authentication of third party software as a default configuration, but let's not pretend that's what lockdown is about.
Not at all. You've always been able to run your own software. At worst, it's toggling one option off in preferences that stays off forever thereafter.
Re: Use zsh as the default shell on your Mac
#74Ooh, and they're throwing in dash too!
> To test script compatibility with Bourne-compatible shells in macOS Catalina, you can change /var/select/sh to /bin/bash, /bin/dash, or /bin/zsh. If you change /var/select/sh to a shell other than bash, be aware that scripts that make use of bashisms may not work properly.
Re: Use zsh as the default shell on your Mac
#75Earlier quoted context omitted.
So, Homebrew? You can't tell me that Microsoft is able to ship entire distribution's userlands (Debian, Ubuntu, SUSE, and more) through the Windows Store, including all their GPL3 components, and Apple can't figure out how to ship an updated version of base64. If I'm grumbling, it's just because making devops/CI scripts work on Windows and Linux is easier than MacOS and Linux these days because my colleagues run into…
How's using homebrew any of this different than being able to run "base64" and "uuidgen" on Windows? It's not like either of those applications are part of a Windows installation anyway.
That's my point. Why can't Apple ship an updated userland built in, through the Store, or as a download triggered by a command line (like XCode is).
Re: Use zsh as the default shell on your Mac
#76Earlier quoted context omitted.
So, Homebrew? You can't tell me that Microsoft is able to ship entire distribution's userlands (Debian, Ubuntu, SUSE, and more) through the Windows Store, including all their GPL3 components, and Apple can't figure out how to ship an updated version of base64. If I'm grumbling, it's just because making devops/CI scripts work on Windows and Linux is easier than MacOS and Linux these days because my colleagues run into…
That’s probably more a BSD vs GNU issue, to be fair. Mac is based on FreeBSD. GNU/Linux, well... :)
Bash is GNU and so is much of the dated MacOS userland.
Re: Use zsh as the default shell on your Mac
#77Earlier quoted context omitted.
> let users self sign executables Which is to say, "let users run their own software". There's value in formal authentication of third party software as a default configuration, but let's not pretend that's what lockdown is about.
Not at all. You've always been able to run your own software. At worst, it's toggling one option off in preferences that stays off forever thereafter.
Not anymore. Since 10.12 Sierra the GUI option to turn off Gatekeeper is gone, you have to use command line to turn it off. And now App Notarization is making it harder still to run your own software.
Re: Use zsh as the default shell on your Mac
#78Earlier quoted context omitted.
The "You must release changes"-clause and anti-tivoization clause might be not be enough individually to switch to MIT zsh but probably were together good enough reasons for Apple to switch.
Why? How does this affect them on macOS at all? If Bash were also being used on iOS that would be different, but I'm quite confident that will never happen.
Again, perhaps it is because Apple is planning for a future where SIP and Gatekeeper cannot be turned off. A future where macOS is basically reduced/merged to iPadOS. Time will tell.
Re: Use zsh as the default shell on your Mac
#79Earlier quoted context omitted.
That’s probably more a BSD vs GNU issue, to be fair. Mac is based on FreeBSD. GNU/Linux, well... :)
Bash is GNU and so is much of the dated MacOS userland.
If I recall correctly, much of the MacOS userland is dated because it uses the last GPLv2 releases of various packages before a move to GPLv3.
Re: Use zsh as the default shell on your Mac
#80For those wondering why Apple is allergic to GPLv3 code: there is a clause in the license requiring you provide a way to run modified version of the software which would require Apple to let users self sign executables.
I've been building software with Homebrew for ages, where does signing come in?