In this situation, you can add an entry in the Services array that documents the fact that your app uses MapKit and Little Snitch can show this fact to the user. These kinds of connections can be documented in the Internet Access Policy using an entry in the Connections array, as shown above.īut what if you’re writing an app that shows a map using Apple’s MapKit framework? In that case, your app doesn’t establish any connection by itself, but instead a macOS daemon is responsible for loading the map data. Your app establishes connections using various means like a low-level socket up to high-level APIs like NSURLSession. … and back from a JSON IAP to a Property List IAP using this command: plutil -convert plist -e plist InternetAccessPolicy.json Connections and Services
You can convert from a Property List IAP to a JSON IAP using the following command: plutil -convert json -r -e json ist All information on this page is valid for both formats, even if they only mention one. They both have the same logical structure and you can use whichever one you prefer. Starting in Little Snitch 4.0.5, Little Snitch not only supports Internet Access Policies in Property List format ( ist), but also in JSON format ( InternetAccessPolicy.json). (Legacy) Support for XPC services before Little Snitch 4.4.Nested IAPs in XPC services, embedded frameworks, and other bundles.Which connection descriptions are shown.Here is an index of everything else you might find useful: Keep it simple: Keep your explanations short and simple.Wildcards: You can use wildcards at any position of the domain or host name, so myserver*.com will work for, etc.You can't have an entry for a directory on your server. Host: The Host field only accepts domains, subdomains, host names or IP addresses.Some of the frameworks have an IAP of their own. Don't forget those of system services and embedded frameworks. Be complete: You have to list all the connections your app initiates.Required fields are only ApplicationDescription and for every connection Host and Purpose, for every service Name and Purpose. Required fields: Most fields are optional.Code Signature: An IAP will only be displayed by Little Snitch and Internet Access Policy Viewer when it's part of a properly signed app bundle.
Still, don't skip the short information below: A few more things you should know These example files alone will probably be enough to create an IAP for your own app.
0 kommentar(er)
