SyndicateVotes
For: 0 (0%)
Against: 0 (0%)
Total: 0
May 4, 2020 07:47 PM
Robert
MacGDBp is not code signed, which is unfortunate because it means:
1) It is not protected by macOS runtime enforcement
2) The Application Firewall flags its listening port on every connection
There are reasons for it to be unsigned (see https://www.bluestatic.org/blog/2020/01/04/macgdbp-2.0-beta-1-released/ ), but it would be nice to figure out a way around Apple's annoying custom two-factor requirements.
1) It is not protected by macOS runtime enforcement
2) The Application Firewall flags its listening port on every connection
There are reasons for it to be unsigned (see https://www.bluestatic.org/blog/2020/01/04/macgdbp-2.0-beta-1-released/ ), but it would be nice to figure out a way around Apple's annoying custom two-factor requirements.
On May 16, 2020 05:09 PM, Robert changed:
- Comment #996 Comment from "MacGDBp is not code signed, which is unfortunate because it means: 1) It is not protected by macOS runtime enforcement 2) The Application Firewall flags its listening port on every connection There are reasons for it to be unsigned (see https://www.bluestatic.org/blog/2020/01/04/macgdbp-2.0-beta-1-released/), but it would be nice to figure out a way around Apple's annoying custom two-factor requirements." to "MacGDBp is not code signed, which is unfortunate because it means: 1) It is not protected by macOS runtime enforcement 2) The Application Firewall flags its listening port on every connection There are reasons for it to be unsigned (see https://www.bluestatic.org/blog/2020/01/04/macgdbp-2.0-beta-1-released/ ), but it would be nice to figure out a way around Apple's annoying custom two-factor requirements."