Firewall for APT and Mirrors #122

New issue

Open

opened 2022-05-16 11:44:23 +00:00 by rafael · 2 comments

rafael commented

2022-05-16 11:44:23 +00:00

(Migrated from gitlab.privaz.io)

Currently ACS is configured with a too thin grained firewall.

every single communication type has to be granted explicitly.

this is a problem in particular for package installation, as package managers rely on multiple mirrors that change often of have multiple IPs, etc.

A compromise would be to allow the APT user to use the internet on ports 80, 443

Currently ACS is configured with a too thin grained firewall. every single communication type has to be granted explicitly. this is a problem in particular for package installation, as package managers rely on multiple mirrors that change often of have multiple IPs, etc. A compromise would be to allow the APT user to use the internet on ports 80, 443

rafael commented

2022-05-16 11:57:12 +00:00

(Migrated from gitlab.privaz.io)

mentioned in commit 088a755e04

mentioned in commit 088a755e047175c82c95db1112735a72b82acc9a

rafael commented

2022-05-17 11:23:38 +00:00

(Migrated from gitlab.privaz.io)

A patch has been implemented in which processes by the _apt user are allowed to go out on ports 80,443 and the mirror subsystem is therefore left alone.