Features/network-zones

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Current status)
(Current status)
 
Line 17: Line 17:
  
 
* Targeted release: [[Releases/17|Fedora 17]]  
 
* Targeted release: [[Releases/17|Fedora 17]]  
* Last updated: 2012-03-13
+
* Last updated: 2012-03-19
* Percentage of completion: 95%
+
* Percentage of completion: 100%
  
 
== Detailed Description ==
 
== Detailed Description ==

Latest revision as of 19:54, 19 March 2012

Contents

[edit] Network Zones

[edit] Summary

The purpose of this feature request is to be able to classify network connections according to their trust level. A public WIFI network connection for example should be untrusted, a wired home network connection should be fairly trusted.

Please also have a look at this additional feature:

[edit] Owner

[edit] Current status

  • Targeted release: Fedora 17
  • Last updated: 2012-03-19
  • Percentage of completion: 100%

[edit] Detailed Description

A network zone describes the trust level of a network connection. Important here is that there is a big difference between a network connection and a network interface. A network interface can be used for many different connections, but a connection is most likely bound to a special network interface.

Currently network connections are unclassified. The user or administrator can not set the trust level of a connection. Additionally the netfilter based firewall in Linux does not know anything about connections - it can only handle network interfaces.

The current firewall solution in Fedora is static and can not enable firewall features for special connections. Either all interfaces are handled in the same way or the user or administrator has to write a complex firewall setup on his own.

The initial network zones:

trusted Fully trusted connections. All incoming traffic is allowed.
home Partly trusted connections. User/administrator defines the the open services.
work
internal
dmz Mostly untrusted connections, the demilitarized zone.
public Mostly untrusted connections. User/administrator defines the the open services.
external
block Fully untrusted connections. No incoming traffic is allowed.
drop Fully untrusted connections. All packets are dropped immediately.

[edit] Benefit to Fedora

The classification of network connections will make it possible to have different firewall configurations for different connections. For example a public WIFI connection should be fairly untrusted and there should at best be no accessible service. The home connection on the other hand should be fairly or fully trusted.

If services are running on a machine, these are only visible for connections that are trusted or that are part of zones, that allow the external access. Having several connections at a time with different trust zones is also possible.

[edit] Scope

Changes to NetworkManager and the D-BUS interface are needed for this. Altogether with extensions of the NM UIs.

[edit] How To Test

  • Install NetworkManager packages with the feature enabled.
  • Set and reset zones for connections.
  • D-BUS messages are generated with information of the connection, interface and zone.

[edit] User Experience

The user can set the trust level of connections ans also the default zone for new connections.

[edit] Dependencies

  • firewalld (changes in the works)

[edit] Contingency Plan

Rebuild of NetworkManager or disabling the feature in the configuration should be enough.

[edit] Documentation

See FirewallD

The fedorahosted site is here: https://fedorahosted.org/firewalld/

[edit] Release Notes

Fedora 17 adds support for the network zones model that provides a way to classify network connections according to their trust level.

The classification of network connections will make it possible to have different firewall configurations for different connections. For example a public WIFI connection should be fairly untrusted and there should at best be no accessible service. The home connection on the other hand should be fairly or fully trusted.