by printz » Sat May 21, 2016 13:55
I just tried opening a development build of Eternity for Mac, and I was promptly told by OSX to move it to trash (because it can't be opened), even when I fully disabled GateKeeper. I'm thinking that, ever since I enrolled in the Mac Developer Program and managed to code-sign all my Mac programs, the signature remained even in the builds maintained by Blzut3, but since he's a different user, he obtains invalidly signed programs. Maybe I'm totally wrong… In any case, I believe there's a need for the dev build maintainer to either (1) modify the code signature to his or her account (if he or she has anything of the sort) or (2) release totally unsigned builds, which will work anyway for any user who fully disables GateKeeper, or just bypasses security using the right click menu.
I just tried opening a development build of Eternity for Mac, and I was promptly told by OSX to move it to trash (because it can't be opened), even when I fully disabled GateKeeper. I'm thinking that, ever since I enrolled in the Mac Developer Program and managed to code-sign all my Mac programs, the signature remained even in the builds maintained by Blzut3, but since he's a different user, he obtains invalidly signed programs. Maybe I'm totally wrong… In any case, I believe there's a need for the dev build maintainer to either (1) modify the code signature to his or her account (if he or she has anything of the sort) or (2) release totally unsigned builds, which will work anyway for any user who fully disables GateKeeper, or just bypasses security using the right click menu.