We have a MacOS version of Cwtch now available! Which is huge and a lot of people have been asking for. It's still early, rough, needs more work, but it also does just work! This work has been hard and still has more to go so if you like it please donate!
openprivacy.ca/donate/
Conversation
Great to see!
Would be nice if it was signed instead of having to YOLO run it, though. If you push past this one, it complains about another relating to a disk image which you also have to YOLO again, which is confusing since the messaging is nearly identical.
1
1
1
Thanks! this is a very early first attempt and I'm also new to Mac dev. Since I built it and ran on the same machine, didn't see these either :/. Signing is definitely something we want to get to as we also move to automating Mac builds but that's a pile more work still :)
1
1
Our first windows builds also had this -_-, actually still have a bit of it since the cheap windows certificates don't entirely seem to solve this problem. Software publishing is an extremely frustrating ecosystem
2
1
1
Yeah, Windows starts off giving the warnings for normal code signing certificates. Once your software starts being used by people it stops treating your certificate as explicitly untrusted. EV certificates start off in the trusted state so you have to pay to avoid that early on.
You'll encounter the same thing when moving to a new code signing certificate, although if you have enough users it can be dealt with via a few releases with the new signing certificate through Beta / Alpha release channels. The only other option is giving in and paying for EV.
1
You probably don't have enough users to avoid the warnings naturally. It's difficult for most software to avoid them completely for regular users without EV since at some point they need to switch certificates and the reputation from signing is completely reset back to zero.