Apple will start requiring having apps notarized
lazarus / 33-macOS - Mac OS X
----------------------------------------------------------------------
MISV · 2018-10-21 10:21
Does anyone here fully understand the requirements? I know it is
optionally for now, but in an year it will be a requirement?
I am already signing my apps.
My current Info.plist
Code: Pascal [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i CFBundleDevelopmentRegion
English CFBundleExecutable
XXXXXX CFBundleName
XXX LSApplicationCategoryType
CFBundleIdentifier
com.example.XXXXXX
CFBundleInfoDictionaryVersion 6.0
CFBundlePackageType APPL
CFBundleSignature XXX
CFBundleShortVersionString 1.0
CFBundleVersion 1
CFBundleIconFile XXXXXX.icns
CSResourcesFileMapped
NSAllowsArbitraryLoads
CFBundleDocumentTypes
CFBundleTypeRole
Viewer
CFBundleTypeExtensions
*
CFBundleTypeOSTypes
fold
disk
****
NSHighResolutionCapable
I need to allow users to make both http and https requests to any
websiteI need to allow users to save their data to non-user locations
(albeit app defaults to MacOS designated applicable user paths)
----------------------------------------------------------------------
Hansaplast · 2018-10-21 12:26
Not sure if this even still works, but there used to be this trick for
the plist:
Code: [Select]NSAppTransportSecurity
NSExceptionDomains
example.com
NSIncludesSubdomains
NSTemporaryExceptionAllowsInsecureHTTPLoads
NSTemporaryExceptionMinimumTLSVersion
TLSv1.1
(source)
On that note, I was looking in the Notarizing process as well (thanks
Apple for yet another hurdle) and am curious about the steps to take
to do this with an application developed with Lazarus Pascal. This is
what I found what Xojo users seem to be succesfull with, but may not
fully applicable for Lazarus apps - I have not tested this yet.
Quote1. Open the Application Loader developer tool in Xcode. Log in to
your developer account and check the box to remember the login so a
keychain entry is created. This allows you to skip entering your
password in subsequent steps.
2. Code sign your app with the hardened runtime option (you may need
entitlements if you are accessing any protected resources). For
example:
$ codesign --force --options runtime --deep --sign "Developer ID
Application: COMPANYNAME" MYAPP.app
3. Bundle the app into a signed DMG for distribution. Steps omitted.
4. Upload the signed DMG for notarization:
$ xcrun altool --notarize-app -f MYAPP.dmg --primary-bundle-id
MYBUNDLEID -u MYAPPLEID -p @keychain:"Application Loader: MYAPPLEID"
5. A RequestUUID is returned. Periodically check the status of the
notarization until it has completed:
$ xcrun altool --notarization-info REQUESTUUID -u MYAPPLEID -p
@keychain:"Application Loader: MYAPPLEID"
6. When the notarization is complete, staple the ticket to the DMG:
$ xcrun stapler staple -v MYAPP.dmg
7. After installing your app, verify that it is notarized:
$ spctl -a -v /Applications/MYAPP.app
MYAPP.app: accepted
source=Notarized Developer ID