The .lsrules file format

Remote rule gropus use a .lsrules file, which is in JSON syntax as specified in this chapter. Such files can be exported using Little Snitch or created using a text editor or a script.

A simple example

Let’s start with a simple example that specifies a single rule for allowing software updates for LaunchBar:

{
  "name": "LaunchBar Software Update",
  "description": "This rule allows LaunchBar to check for updates.",
  "rules": [
    {
      "action": "allow",
      "process": "/Applications/LaunchBar.app/Contents/MacOS/LaunchBar",
      "remote-hosts": "sw-update.obdev.at"
    }
  ]
}

Blocklists

Before Little Snitch was able to read various blocklist formats, blocklists had to be represented as remote rule groups. The .lsrules file still supports shortcuts for this type of blocklist. Using the above syntax, you’d have to repeat "process": "any" and "action": "deny" for each domain, host, or IP address. For thousands of rules, that can lead to unnecessarily large files which in turn lead to unnecessarily large downloads for every single subscriber.

Starting in Little Snitch 4.2, you can use a more compact format that looks like this:

{
    "name": "Social Media Block List",
    "description": "Blocks access to popular social media sites.",
    "denied-remote-domains": ["facebook.com", "twitter.com", "youtube.com"]
}

Top-level keys

The top level of an .lsrules file is a JSON dictionary with the following keys:

To efficiently support blocklists, the following keys were added in Little Snitch 4.2:

Rule keys

Each rule defined in the file is a JSON dictionary with the following keys:

Specifying the process

To define which processes a rule should match, you specify the executable of the process using the following keys:

• To match any process, use:
  • "process": "any"
• To match a specific process, use:
  • "process" (String): A String containing the full path to the executable. For apps, this is path to the app’s executable, not the app wrapper. For example: /Applications/Safari.app/Contents/MacOS/Safari
  • "via" (String, optional): If the rule should only match if the executable uses a specific helper tool, you can specify its path. For example, you could create a rule that matches “Terminal via ping” by setting "path" to Terminal’s path and "via" to ping’s path. Note that a rule for Terminal that has no "via" will also match connections of “Terminal via ping”.

Processes can be specified by their absolute path (path based rules) or by their code ID. Code IDs are given as identifier.DEV_TEAM_ID/IDENTIFIER. For Little Snitch, that would be identifier.MLZF7K7B5R/at.obdev.littlesnitch.

Specifying the remote

The remote for the rule can be specified in multiple ways. You can only provide one of the following keys:

• "remote-addresses": A String containing one or more IP addresses or ranges.
• "remote-hosts": Either a String with a hostname, or an Array of Strings of hostnames.
• "remote-domains": Either a String with a domain name, or an Array of Strings of domain names.
• "remote": A String with exactly one of the following values.
  • "any"
  • "local-net"
  • "multicast"
  • "broadcast"
  • "bonjour"
  • "dns-servers"
  • "bpf" (Berkeley Packet Filter, available starting in Little Snitch 4.4.3)

Other keys

War dieser Eintrag hilfreich? Hinterlass uns Feedback.
© 2016-2024 Objective Development Software GmbH