Apps / Blighter Restrictor: technical information

Blighter Restrictor: technical information

Version 1.2.5 · for technically confident readers

How it works

The parent app connects to each child PC over SSH with a password, as a dedicated blighter account. On the child PC, Squid listens on 127.0.0.1:3128 and filters by domain name. A firewall limits the child's account to Squid, DNS and UDP 50000-65535 (Discord voice and video).

  • HTTPS is not decrypted, so the log shows domains, not pages.
  • Two modes: allow all and block some, or block all and allow some. Both lists are kept.
  • On Windows the firewall applies to the whole PC, because Windows can't reliably filter outgoing traffic per account.
  • Home-network (private range) traffic is not filtered when Allow home network access is on.
  • Opera downloads are blocked by default, because Opera's built-in VPN can't be switched off.

Release files

FileForSize
BlighterRestrictor-Setup-1.2.5.exeParent, Windows35 MB
blighter-restrictor_1.2.5_all.debParent, Linux32 KB
BlighterChild-Setup-1.2.5.exeChild, Windows 10/1113 MB
blighter-child_1.2.5_all.debChild, Ubuntu21 KB

The Windows installers are not code-signed yet.

Command-line install (Linux)

sudo apt install ./blighter-child_1.2.5_all.deb      # child PC
sudo apt install ./blighter-restrictor_1.2.5_all.deb # parent PC

Limitations

  • Designed for a home network behind a router: password authentication only, no MFA.
  • Tested on x86/x64 only; not tested on ARM or tablets.
  • A child with administrator rights can undo the restrictions.
  • Paid VPNs are not specially blocked.

Source code

Blighter Restrictor is open source under the GPL-3.0-or-later licence. Source code on GitHub.