![]() ![]() Developer submits program and signature to Apple's notarising serviceĤ. Developer signs program to provide evidence to end-user that program has not been tampered withģ. Here's a grossly simplified version of what happens with Apple's notary service:Ģ. Notarising is only the act of a trusted third party verifying that the signature on a document is valid. But toasting the sandwich provided by the customer doesn’t mean you actually like it. You might reject a sandwich which isn’t built properly (eg: has mismatched bread slices, is missing contents or smells of dynamite). ![]() It’s like claiming that the outcome of toasting a sandwich is approval or rejection, no the outcome of toasting a sandwich is you have a sandwich that is toasted, aka “toasted sandwich.” The outcome of notarisation is that the app has been notarised. Scanning for malware is simply to avoid embarrassing situations me an author/publisher finding they’ve been compromised by some well known malware. There’s no attempt by Apple to claim that the application is safe or does what it says on the tin. ![]() Notarisation for macOS similarly only means, “the developer presented us with their application and their certificate of authenticity and we signed it with the certificate that allows macOS to run it without complaining.” When a Justice of the Peace notarises a piece of documentation, they are not vouching for authenticity they are only voicing for certain claims made: the document was presented on a certain date, and/or that this copy is an accurate facsimile of the provided original. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |