What Not Notarizing looks like

Das Goravani das at Goravani.com
Wed Sep 18 17:58:44 EDT 2019


I agree with all you say, it’s quite a heavy tech note. The good news is that you only need to do it to Omnis, and then you have it.. you can upgrade your library without having to redo all this stuff, it only affects Omnis.  

I’ve read it over a number of times and each time it got simpler to me in my mind. The way the tech note is written doesn’t help but if you read it over and over it becomes clear that it’s just a bunch of commands, that are pretty straightforward, although each is a long string to type, and it’s dealing with getting a password, putting that in keychain, XCODE the omnis app to apple and wait for emails. 

I do the commands in a text editor and save them so that if I have to redo them I dont have to retype them. To get the paths I drag the app into the terminal window which gives you the path string with escapes. Copying out of that window works, so I can grab the paths and paste them into my textedit document.  

I might end up remaking the document when I actually do it soon, because I dont think the document was fleshed out all that well by whomever made it. 



> On Sep 18, 2019, at 8:42 AM, Alain Stouder Omnis <omnis at smartway.ch> wrote:
> 
> I agree with you Das.
> 
> That’s a tough technote to swallow !
> 
> Code signing and certificates are hidden behind complex command lines and repositories and users only see a small certificate icon on your installer or your executable.
> 
> There is no need for such complexity but Apple and Microsoft have not made it simple (and Xcode is a work in progress).
> 
> Apple's new requirements add new steps to codesigning, because we used to ship signed components from Omnis and we only needed to sign our installer. Now, we need to codesign everything we ship and notarize it.
> 
> 
>> On 12 Sep 2019, at 23:49, Das Goravani <das at goravani.com> wrote:
>> 
>> 
>> The Omnis tech note on Notarizing is formidable to me. I don’t know Xcode at all, dont have it, have barely used the command line interface before. The instructions are long with many steps, each one daunting. 
>> 
>> It says that if you dont notarize you get a Malware Warning. Does it stop there? It says you have a more streamlined gatekeeper experience. What does that mean? I dont even know what Gatekeeper is. What is a more streamlined experience? Or rather, what happens if you dont have that? 
>> 
>> I’ve heard you can right click on the App and select Open and it will work. Is this true? It will install? 
>> 
>> I’m surprised they didn’t write the tech note with PACKAGES in mind, since most Mac developers use it. I use it. 
>> 
>> This tech note, and what it contains, is a huge break from the “anybody can do this” days of Omnis and Mac. It is a foray into DOS and UNIX, technical details that are barely explained. I’m not even sure where to put those plists that are described at the outset of the note though I think I can trace where from the command line commands given later in the note. They are put in the Omnis install locations on the machine. 
>> 
>> I’m a bit peeved at this. It’s very complex and probably means my installer will act second class as I dont think I can do this. 
>> 
>> 
>> _____________________________________________________________
>> Manage your list subscriptions at http://lists.omnis-dev.com
>> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com 
>> 
> 
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com 




More information about the omnisdev-en mailing list