Re: code signing and the future of MacPorts

2022-03-13 Thread Rainer Müller
Hello, here is an older concept from 2016 I had written for gdb/lldb as Apple began to require code-signing for debuggers. This applies to more actions by now, but with the same requirements. The replies are also relevant and discuss alternatives.

Re: code signing and the future of MacPorts

2022-03-11 Thread Gerben Wierda via macports-dev
Additionally, I was thinking that the binary downloads of ports might be codesigned. That would prevent people from all having to buy a certificate themselves (and self-signed is not really an option, these are generally ignored, maybe not if you mark them as trusted). You can of course also

code signing and the future of MacPorts

2022-03-11 Thread Gerben Wierda via macports-dev
I’ve recently moved from macOS Mojave with MacPorts to macOS Monterey with MacPorts I’ve had serious trouble with the application level firewall (alf/socketfilterfw). I now suspect that one reason is that Apple is getting stricter and stricter about only allowing binaries that have been code