(Redirected from Peer Block)
Auto tune learning curve. Little Snitch is a firewall application that monitors and controls outbound internet traffic. If you're looking for more info about Little Snitch like screenshots, reviews and comments you should visit our info page about it. Below you find the best alternatives. Apr 22, 2015 I have AdBlock Edge, the huge hosts file I recently described creating, and Little Snitch, with an ever growing additional set of permanent blocks. Ghostery continues to report blocking trackers. Just opened a popular site, and Ghostery reported blocking 13 trackers. If I had more time, I'd add those blocked to hosts.
Developer(s) | Mark Bulas, 'night_stalker_z', 'XhmikosR' |
---|---|
Initial release | September 27, 2009; 10 years ago |
Final release | 1.2[1] / January 14, 2014; 6 years ago |
Repository | |
Written in | C++ |
Operating system | Microsoft Windows |
Available in | English |
Type | Firewall |
License | GPL or zlib License |
Website | peerblock.com |
Usage |
Part of a series on |
File sharing |
---|
Technologies |
Video sharing sites |
BitTorrent sites |
Academic/scholarly |
File sharing networks |
P2P clients |
Streaming programs |
Anonymous file sharing |
Development and societal aspects |
By country or region |
Comparisons |
PeerBlock is a free and open-sourcepersonal firewall that blocks packets coming from, or going to, a maintained list of black listed hosts.[2] PeerBlock is the Windows successor to the software PeerGuardian (which is currently maintained only for Linux).[3] It blocks incoming and outgoing connections to IP addresses that are included on blacklists (made available on the Internet), and to addresses specified by the user.[3] PeerBlock mainly uses blacklists provided by iblocklist.com.
Development[edit]
PeerBlock 1.0 is based on the same code as PeerGuardian 2 RC1 Test3 Vista version.[3] It adds support for 32- and 64-bit Windows Vista, Windows 7, and Windows 8. When the PeerGuardian project ended, its developer Phoenix Labs encouraged current PeerGuardian users to migrate to PeerBlock.[4]
PeerBlock is under development by a small team of developers led by Mark Bulas.[5] Hosting, as well as the signed driver, is funded by donations from the public. Future donations are intended to contribute to future signed drivers, hosting and to possibly rent a virtual private server on which the team should be able to build a 'real' online-update feature for future releases of PeerBlock.
Introduced in 2017, Peerblocklist.com offers modern blocklists in p2p format that are compatible with Peerblock
Features[edit]
PeerBlock has multiple features in the latest version of the program. These include a constantly updating blocklist managed by the home site and a manager that lets you choose which lists to include in the block. The program allows for a user to turn on and off both IP and HTTP trackers as well as including a log showing the time, source, IP address, destination, and protocol of the tracker. A list of settings allows users to both customize their program's interface as well as its operations.[citation needed]
Until September 2013, I-Blocklist, the supplier of the blocking lists PeerBlock uses, supported unlimited free list updating. Since September 2013 updates were limited to once weekly, except to paid subscribers. PeerBlock is hard-coded to use I-Blocklist lists and has entered into a revenue-sharing agreement with I-Blocklist.[6] In late 2015 blocklists were no longer available without payment of a subscription.[7]
In late 2017, peerblocklist.com began offering free blocklists against malicious hosts and ad-servers to Peerblock and Peerguardian users.[8] However, as of late 2019, the site charges a monthly subscription fee for access to all lists.
References[edit]
- ^Peerblock, LLC. 'PeerBlock 1.2 – Peerblock Site'. Archived from the original on 2014-01-16.
- ^Harac, Ian (November 5, 2009). 'PeerBlock Helps You Surf the Web in Secret'. PCWorld. Retrieved 29 March 2018.
- ^ abc'What is PeerBlock's relationship with the old PeerGuardian program?'. Archived from the original on February 8, 2010. Retrieved July 18, 2010.
- ^'Phoenix Labs – Powered by vBulletin'.
- ^Peerblock, LLC. 'About Us – Peerblock Site'. Archived from the original on 2009-10-02.
- ^Peerblock, LLC. 'PeerBlock / IBlockList Partnership – Peerblock Site'. Archived from the original on 2013-10-14.
- ^'List Update Error: Subscription required – Peerblock Site'. Peerblock.com. Archived from the original on 26 December 2015. Retrieved 31 December 2015.
- ^'Blocklists for Peerblock & Peerguardian'. peerblocklist.com. Retrieved 3 December 2017.
External links[edit]
- Official website
- #peerblockconnect on freenode
- PeerBlock Helps You Surf the Web in Secret, PC World, 6 November 2009
- P2Partisan – peerblock style script running on routers with tomato firmware
- PeerBlock-Setup_v1.2_r693.exe - PeerBlock v1.2 r693
Retrieved from 'https://en.wikipedia.org/w/index.php?title=PeerBlock&oldid=929595879'
Little Snitch Block Lists 2017
Rule group subscriptions use a
.lsrules
file, which is a JSON format specified in this chapter. Such files can be exported using Little Snitch Configuration 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:
Blocklists
A common use case for rule group subscriptions are blocklists that contain a lot of domains, hosts, or IP addresses for which access should be flat out denied. 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 that 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:
Top-level keys
The top level of an
.lsrules
file is a JSON dictionary with the following keys:Key | Type | Description |
---|---|---|
name | String | The name of the group. |
description | String | A description of the rule grouop. |
rules | Array of Dictionaries | The list of rules. See below for rule-level keys. |
To efficiently support blocklists, the following keys were added in Little Snitch 4.2:
Key | Type | Description |
---|---|---|
denied-remote-domains | Array of Strings | A list of domain names. |
denied-remote-hosts | Array of Strings | A list of hostnames. |
denied-remote-addresses | Array of Strings | A list of IP addresses. See Anatomy of a rule > Server (remote computer) for supported syntax. |
denied-remote-notes | String | The notes that should be repeated for each rule. The placeholder %REMOTE% will be replaced with the respective domain, host, or IP-address for each rule. |
You can mix all of these keys in a single
.lsrules
file, i.e. you can define arbitrary rules in a rules
array next to a list of domains in denied-remote-domains
and a list of IP addresses in denied-remote-addresses
.Rule keys
Each rule defined in the file is a JSON dictionary with the following keys:
Little Snitch Block Lists List
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”.
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 in the format described in Anatomy of a rule > Server (remote computer).'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. For a description of each of these values, see Anatomy of a rule > Server (remote computer).'any'
'local-net'
'multicast'
'broadcast'
'bonjour'
'dns-servers'
'bpf'
(Berkeley Packet Filter, available starting in Little Sntich 4.4.3)
Other keys
Key | Type | Description |
---|---|---|
direction | String, optional | The connection direction. 'incoming' or 'outgoing' , defaults to 'outgoing' . |
action | String, optional | The rule action. 'allow' , 'deny' , or 'ask' . Defaults to 'ask' . |
priority | String, optional | The rule priority. 'regular' or 'high' . Defaults to 'regular' . |
disabled | Boolean, optional | Whether or not the rule is disabled by default. Defaults to false . |
ports | String, optional | The ports the rule matches. Can be 'any' for any port (the default), a single port (e.g. '443' ), or a range of ports (e.g. '123-456' ). |
protocol | String, optional | The protocol the rule matches. Can be a numeric value as defined in /etc/protocols , like '6' for TCP, or the actual protocol name, like 'tcp' . Defaults to any protocol. |
notes | String, optional | The notes for the rule. |
Was this help page useful? Send feedback.
© 2016-2020 by Objective Development Software GmbH
© 2016-2020 by Objective Development Software GmbH