* The feature is limited to milestone 1 (base): configuration with files, no cli and no D-Bus interface

* The feature is limited to milestone 1 (base): configuration with files, no cli and no D-Bus interface

−

* Firewalld milestones for rich language and lockdown features, the milestones 1 and 2 (base and cli) a planned for F-19. Milestone 3 (gui) is planned for F-20.

+

* Milestone 2 (D-BUS, command line client) has been added to Fedora 19 with version 0.3.3.

+

Milestone 3 (GUI) has been added to Fedora 19 with version 0.3.4 (as an update)

+

* Firewalld milestones for rich language and lockdown features, the milestones 1 is part of Fedora 19, milestone 2 (base and cli) will be provided as an update for F-19. Milestone 3 (gui) is planned for F-20.

** Milestone 2: New config language via D-BUS interfaces with command line client ~ end of May

** Milestone 2: New config language via D-BUS interfaces with command line client ~ end of May

Line 19:

Line 21:

== Detailed Description ==

== Detailed Description ==

−

Local applications or services are able to change the firewall configuration if they are running as root (example: libvirt). With this feature the administator can lock the firewall configuration so that either none or only applications that are in the allowed list are able to request firewall changes.

+

Local applications or services are able to change the firewall configuration if they are running as root (example: libvirt). With this feature the administrator can lock the firewall configuration so that either none or only applications that are in the allowed list are able to request firewall changes.

The lockdown feature is a very light version of user and application policies for firewalld and is turned off by default. Comprehensive user and application policies will be added later on.

The lockdown feature is a very light version of user and application policies for firewalld and is turned off by default. Comprehensive user and application policies will be added later on.

Line 30:

Line 32:

== How To Test ==

== How To Test ==

−

1) Set Lockdown=yes in /ec/firewalld/firewalld.conf

+

1) Set Lockdown=yes in /etc/firewalld/firewalld.conf

−

2) Try to enable the service imaps in the default zone:

+

2) Reload firewalld

+

firewall-cmd --reload

+

+

3) Try to enable the service imaps in the default zone:

firewall-cmd --add-service=imaps

firewall-cmd --add-service=imaps

Results in: Error: ACCESS_DENIED: lockdown is enabled

Results in: Error: ACCESS_DENIED: lockdown is enabled

−

3) Add this to /etc/firewalld/lockdown-whitelist.xml to the whitelist element:

Or add this to /etc/firewalld/lockdown-whitelist.xml to the whitelist element:

<command name="/usr/bin/python /usr/bin/firewall-cmd*"/>

<command name="/usr/bin/python /usr/bin/firewall-cmd*"/>

−

4) Reload firewalld

+

5) Reload firewalld

firewall-cmd --reload

firewall-cmd --reload

−

5) Try to enable service imaps again in the default zone:

+

6) Try to enable service imaps again in the default zone:

firewall-cmd --add-service=imaps

firewall-cmd --add-service=imaps

No error

No error

Line 56:

Line 64:

== Documentation ==

== Documentation ==

−

With the lockdown feature changes to the firewall configutaion can be blocked or limited to a white list. The white list is empty by default and can contain commands, users, user ids and selinux contexts. The lockdown access check is limited to D-Bus methods that are chainging firewall rules. Query, list and get methods are not limited

+

With the lockdown feature changes to the firewall configuration can be blocked or limited to a white list. The white list is empty by default and can contain commands, users, user ids and selinux contexts. The lockdown access check is limited to D-Bus methods that are changing firewall rules. Query, list and get methods are not limited

+

+

=== Handle lockdown with the command line client ===

+

+

==== Lockdown Options ====

+

Local applications or services are able to change the firewall configuration if they are running as root (example: libvirt) or are authenticated using PolicyKit. With this feature the administrator can lock the firewall configuration so that only applications on the lockdown whitelist are able to request firewall changes.

+

+

The lockdown access check limits D-Bus methods that are changing firewall rules. Query, list and get methods are not limited.

+

+

The lockdown feature is a very light version of user and application policies for firewalld and is turned off by default.

If a command entry on the whitelist ends with an asterisk '*', then all command lines starting with the command will match. If the '*' is not there the absolute command inclusive arguments must match.

+

+

Commands for user root and others is not always the same. Example: As root, /bin/firewall-cmd is used, as a normal user, /usr/bin/firewall-cmd is used on Fedora.

+

+

The context is the security (SELinux) context of a running application or service. To get the context of a running application use

+

+

ps -e --context

+

+

Warning: If the context is unconfined, then this will open access for more than the desired application.

+

+

firewall-cmd --list-lockdown-whitelist-commands

+

List all command lines that are on the whitelist.

+

+

firewall-cmd --add-lockdown-whitelist-command=<command>

+

Add the command <command> to the whitelist.

+

+

firewall-cmd --remove-lockdown-whitelist-command=<command>

+

Remove the command <command> from the whitelist.

+

+

firewall-cmd --query-lockdown-whitelist-command=<command>

+

Query whether the command <command> is on the whitelist. Returns 0 if true, 1 otherwise.

+

+

firewall-cmd --list-lockdown-whitelist-contexts

+

List all contexts that are on the whitelist.

+

+

firewall-cmd --add-lockdown-whitelist-context=<context>

+

Add the context <context> to the whitelist.

+

+

firewall-cmd --remove-lockdown-whitelist-context=<context>

+

Remove the context <context> from the whitelist.

+

+

firewall-cmd --query-lockdown-whitelist-context=<context>

+

Query whether the context <context> is on the whitelist. Returns 0 if true, 1 otherwise.

+

+

firewall-cmd --list-lockdown-whitelist-uids

+

List all user ids that are on the whitelist.

+

+

firewall-cmd --add-lockdown-whitelist-uid=<uid>

+

Add the user id <uid> to the whitelist.

+

+

firewall-cmd --remove-lockdown-whitelist-uid=<uid>

+

Remove the user id <uid> from the whitelist.

+

+

firewall-cmd --query-lockdown-whitelist-uid=<uid>

+

Query whether the user id <uid> is on the whitelist. Returns 0 if true, 1 otherwise.

+

+

firewall-cmd --list-lockdown-whitelist-users

+

List all user names that are on the whitelist.

+

+

firewall-cmd --add-lockdown-whitelist-user=<user>

+

Add the user name <user> to the whitelist.

+

+

firewall-cmd --remove-lockdown-whitelist-user=<user>

+

Remove the user name <user> from the whitelist.

+

+

firewall-cmd --query-lockdown-whitelist-user=<user>

+

Query whether the user name <user> is on the whitelist. Returns 0 if true, 1 otherwise.

+

+

=== With configuration files ===

Example:

Example:

Line 68:

Line 157:

</whitelist>

</whitelist>

−

Importand for the command tag is the path. As root /bin/firewall-cmd is used, as a normal user /usr/bin/firewall-cmd will be used. The '*' at the end of the name attribute of command means that all matches, that start with this string. If the '*' is not there the absolute command inclusive arguments must match.

+

Important for the command tag is the path. As root, /bin/firewall-cmd is used, as a normal user, /usr/bin/firewall-cmd will be used. The '*' at the end of the name attribute of command means that all matches, that start with this string. If the '*' is not there the absolute command inclusive arguments must match.

+

+

To get the context of a running application use

+

ps -e --context

+

Then add the context of the application with <selinux context="<context>"/> to the white list to white list this application. '''Warning:''' If the context is unconfined, then this will open access for more than the desired application.

+

+

=== The Default whitelist configuration ===

+

+

The default whitelist contains the NetworkManager context and the default context of libvirt. Also the user id 0 is in the list.

Owner

Current status

The feature is limited to milestone 1 (base): configuration with files, no cli and no D-Bus interface

Milestone 2 (D-BUS, command line client) has been added to Fedora 19 with version 0.3.3.

Milestone 3 (GUI) has been added to Fedora 19 with version 0.3.4 (as an update)

Firewalld milestones for rich language and lockdown features, the milestones 1 is part of Fedora 19, milestone 2 (base and cli) will be provided as an update for F-19. Milestone 3 (gui) is planned for F-20.

Milestone 2: New config language via D-BUS interfaces with command line client ~ end of May

Milestone 3: GUI early to mid July

Detailed Description

Local applications or services are able to change the firewall configuration if they are running as root (example: libvirt). With this feature the administrator can lock the firewall configuration so that either none or only applications that are in the allowed list are able to request firewall changes.

The lockdown feature is a very light version of user and application policies for firewalld and is turned off by default. Comprehensive user and application policies will be added later on.

Benefit to Fedora

An easy way to lock the firewall configuration for local applications.

Or add this to /etc/firewalld/lockdown-whitelist.xml to the whitelist element:

<command name="/usr/bin/python /usr/bin/firewall-cmd*"/>

5) Reload firewalld

firewall-cmd --reload

6) Try to enable service imaps again in the default zone:

firewall-cmd --add-service=imaps

No error

User Experience

The lock down settings defaults to disabled. If enabled the user can be sure that there are no unwanted configuration changes for the firewall from local applications or services.

Dependencies

None.

Contingency Plan

This is a simple firewalld setting, which can be enabled or dropped easily.

Documentation

With the lockdown feature changes to the firewall configuration can be blocked or limited to a white list. The white list is empty by default and can contain commands, users, user ids and selinux contexts. The lockdown access check is limited to D-Bus methods that are changing firewall rules. Query, list and get methods are not limited

Handle lockdown with the command line client

Lockdown Options

Local applications or services are able to change the firewall configuration if they are running as root (example: libvirt) or are authenticated using PolicyKit. With this feature the administrator can lock the firewall configuration so that only applications on the lockdown whitelist are able to request firewall changes.

The lockdown access check limits D-Bus methods that are changing firewall rules. Query, list and get methods are not limited.

The lockdown feature is a very light version of user and application policies for firewalld and is turned off by default.

Important for the command tag is the path. As root, /bin/firewall-cmd is used, as a normal user, /usr/bin/firewall-cmd will be used. The '*' at the end of the name attribute of command means that all matches, that start with this string. If the '*' is not there the absolute command inclusive arguments must match.

To get the context of a running application use

ps -e --context

Then add the context of the application with <selinux context="<context>"/> to the white list to white list this application. Warning: If the context is unconfined, then this will open access for more than the desired application.

The Default whitelist configuration

The default whitelist contains the NetworkManager context and the default context of libvirt. Also the user id 0 is in the list.