Tails

#1 Updated by intrigeri 2017-02-01 22:36:25

Feb 01 22:33:15 localhost.localdomain ferm[366]: Starting Firewall: fermiptables-restore v1.6.0: owner: Bad value for "--uid-owner" option: "amnesia"
Feb 01 22:33:15 localhost.localdomain ferm[366]: Error occurred at line: 35
Feb 01 22:33:15 localhost.localdomain ferm[366]: Try `iptables-restore -h' or 'iptables-restore --help' for more information.
Feb 01 22:33:15 localhost.localdomain ferm[366]: Failed to run /sbin/iptables-restore
Feb 01 22:33:15 localhost.localdomain ferm[366]: Firewall rules rolled back.
Feb 01 22:33:15 localhost.localdomain ferm[366]:  failed!
Feb 01 22:33:15 localhost.localdomain systemd[1]: ferm.service: Main process exited, code=exited, status=1/FAILURE
Feb 01 22:33:15 localhost.localdomain systemd[1]: Failed to start ferm firewall configuration.
Feb 01 22:33:15 localhost.localdomain systemd[1]: ferm.service: Unit entered failed state.
Feb 01 22:33:15 localhost.localdomain systemd[1]: ferm.service: Failed with result 'exit-code'.

That’s because ferm.service starts before live-config.service is done.

#2 Updated by intrigeri 2017-02-01 23:13:53

No, that’s because of:

                daddr 127.0.0.1 proto tcp syn dport 17600:17650 {
                    mod owner uid-owner amnesia ACCEPT;
                }

It should be “$amnesia_uid” like everywhere else.

This probably affects 2.10 too.