Firewall settings – antiX-22 Full

[Member Xunzi_23]

Helpful

Up

0

::

@ caprea, good point, thanks, UFW definitely needs activation in service manager.
Too used to sysv.

• This reply was modified 2 months, 2 weeks ago by Xunzi_23.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Installing gufw brings in elogind as well (on antiX-23 but not antiX-22) – culprit is dependency on pkexec

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Moderator caprea]

Helpful

Up

0

::

The script of PPC works nicely, it’s the better option in my opinion than gufw.

[Member PPC]

Helpful

Up

0

::

Partly off-topic:
From my long gone days as Windows user, I seem to recall that firewalls there allowed to cut access to the network to chosen applications (ex: if you want to play a game off-line and make sure it does not “phone home”).
It seems that we don’t need firewalls in Linux to do that, just the Terminal:

unshare -r -n [name_of_the_app_to_run_without_network_access]

Firejail can do the same.

An excellent guide about how to configure firewalls to block access on a per app basis is here (I did not test it):
https://unix.stackexchange.com/questions/68956/block-network-access-of-a-process , I think it’s the 4th answer (be careful, it referes to systemd, not sysv or runit, as init systems!).

P.

[Member olsztyn]

Helpful

Up

0

::

anticapitalista wrote:

Installing gufw brings in elogind as well (on antiX-23 but not antiX-22)

My understanding is this is the reason gufw is no longer included in antiX. Ufw on the other hand works nicely – set and forget…

• This reply was modified 2 months, 2 weeks ago by olsztyn.
• This reply was modified 2 months, 2 weeks ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Forum Admin anticapitalista]

Helpful

Up

0

::

PPC wrote:

@Techore – I respect your opinion, but I also think that basic management tasks any non geek user may want to perform: namely- set date and time, update the OS, install packages, enable/disable a firewall, add/remove icons the the toolbar or the menu, etc, should, by default have an easy to use GUI out of the box. It takes only some kb and one extra entry on the Control Center. If users don’t need it, they won’t notice any difference… but if users need that feature, they’ll be glad it’s there…

@anticapitalista and all- the script is ready (it requires some localization, but it’s already adapted for easy localization- the variables with the text are all on the start of the script…)
Please test the GUI:

Note and possible TO DO: on my system, after toggling on UFW, it was off after I rebooted… I think this was discussed before on the forum- if so, please point me to the how-to, so that feature can be added to the script- I’m too busy to search the forum for that, right now…

EDIT: I’m running antiX 22, 64bits, full, runnit

P.

I have added runit checks and if runit is detected, then it should autostart/disable the ufw runit sevice as well.
Should there be a .desktop file as well so it appears in the menu?

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member PPC]

Helpful

Up

0

::

anticapitalista wrote:

Should there be a .desktop file as well so it appears in the menu?

I think it should have a .desktop file, yes, something simple like:

[Desktop Entry]
Name=UFW Firewall
Exec=antix_firewall_toggle
Icon=/usr/share/icons/papirus-antix/48x48/apps/preferences-system-firewall.png
Categories=Network
Keywords=firewall,ufw
Terminal=false
Type=Application

This .desktop file won’t probably require much localization- “Firewall” does not require translation, in our alphabet (but it probably does in Cyrillic, asian languages, arabic, etc…)
Of course, please use the correct Exec field!

P.

• This reply was modified 2 months, 2 weeks ago by PPC.

[Member marcelocripe]

Helpful

Up

0

::

This .desktop file won’t probably require much localization- “Firewall” does not require translation, in our alphabet (but it probably does in Cyrillic, asian languages, arabic, etc…)
Of course, please use the correct Exec field!

We already have the .desktop file translated https://gitlab.com/antix-contribs/antix-desktop-files/-/blob/main/.desktop/gufw.desktop, just use what we have ready and translated.

What is the reason not to use the translated .desktop file?

– – – – –

This .desktop file won’t probably require much localization- “Firewall” does not require translation, in our alphabet (but it probably does in Cyrillic, asian languages, arabic, etc…)
Of course, please use the correct Exec field!

Nós já temos o arquivo .desktop traduzido https://gitlab.com/antix-contribs/antix-desktop-files/-/blob/main/.desktop/gufw.desktop, basta utilizar o que temos pronto e traduzido.

Qual é o motivo não utilizar o arquivo .desktop traduzido?

[Member marcelocripe]

Helpful

Up

0

::

I recommend searching the URL https://gitlab.com/antix-contribs/antix-desktop-files/-/tree/main/.desktop for the translated .desktop files and reusing them whenever possible. Otherwise, our volunteer translation work will be completely lost.

– – – – –

Eu recomendo pesquisar no URL https://gitlab.com/antix-contribs/antix-desktop-files/-/tree/main/.desktop os arquivos .desktop traduzidos e reutilizá-los sempre que for possível. Caso contrário, o nosso trabalho voluntário de tradução será totalmente perdido.

[Member PPC]

Helpful

Up

0

::

marcelocripe wrote:

What is the reason not to use the translated .desktop file?

Answer: simply because the .desktop file is for a program called GUFW, that, among other things is a GUI for UFW and allow to configure how the firewall works (what ports and IP’s are allowed or blocked, etc.)
This proposed script simply turns UFW on and off- it has zero to do with GUFW. The script does not allow users to “configure UFW”, like the .desktop file says. If we used that .desktop file, users would get the wrong idea about what the script does.

P.

[Member marcelocripe]

Helpful

Up

0

::

Answer: simply because the .desktop file is for a program called GUFW, that, among other things is a GUI for UFW and allow to configure how the firewall works (what ports and IP’s are allowed or blocked, etc.)
This proposed script simply turns UFW on and off- it has zero to do with GUFW. The script does not allow users to “configure UFW”, like the .desktop file says. If we used that .desktop file, users would get the wrong idea about what the script does.

So, if the other gufw.desktop file is not useful for this purpose, I leave the texts of the pt_BR translation here:

Name[pt_BR]=Ativar ou Desativar o UFW Firewall
Comment[pt_BR]=O UFW Firewall ou Uncomplicated Firewall ou Firewall Descomplicado é um programa de segurança que utiliza uma interface de linha de comandos e o iptables para a sua configuração

Note: Thank you PPC for your suggestions and indications for improvements in the pt_BR text.

– – – – –

Answer: simply because the .desktop file is for a program called GUFW, that, among other things is a GUI for UFW and allow to configure how the firewall works (what ports and IP’s are allowed or blocked, etc.)
This proposed script simply turns UFW on and off- it has zero to do with GUFW. The script does not allow users to “configure UFW”, like the .desktop file says. If we used that .desktop file, users would get the wrong idea about what the script does.

Então, se o outro arquivo gufw.desktop não serve para esta finalidade, eu deixo aqui os textos da tradução pt_BR:

Name[pt_BR]=Ativar ou Desativar o UFW Firewall
Comment[pt_BR]=O UFW Firewall ou Uncomplicated Firewall ou Firewall Descomplicado é um programa de segurança que utiliza uma interface de linha de comandos e o iptables para a sua configuração

Observação: Obrigado PPC por suas susgetões e indicações de melhorias no texto pt_BR.

[Author]

Posts