zerotierone: 1.4.2 -> 1.4.4

[danielfullmer]

Motivation for this change

Update for latest version. See: https://github.com/zerotier/ZeroTierOne/releases/tag/1.4.4
Note the license change to BSL 1.1.

Tested working with my zerotier network.

Things done

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Ensured that relevant documentation is up to date
• Fits CONTRIBUTING.md.

Notify maintainers

cc @sjmackenzie @zimbatm @ehmry @obadz

[zimbatm]

it's a shame about BSL but nothing we can do about it

[fadenb]

I just noticed the license change when updating a test system using the unstable channel.

How do we usually handle such a change to an unfree license? Should this be added to the release notes that nobody is surprised that systems without nixpkgs.config.allowUnfree = true; no longer build?

[zimbatm]

Good question. It's a first for me too.

What happens is the user gets a breakage if allowUnfree is set to false. At that point I expect the user to look into the code. Is there anything we can do better?