Changes/EmptyTemplate

From FedoraProject

< Changes(Difference between revisions)
Jump to: navigation, search
m (typo)
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
+
= Workstation: Disable firewall =
  
<!-- Self Contained or System Wide Change Proposal?
+
== Summary ==
Use this guide to determine to which category your proposed change belongs to.
+
  
Self Contained Changes are:
+
The firewalld service will not be enabled by default in the workstation product.
* changes to isolated/leaf package without the impact on other packages/rest of the distribution
+
* limited scope changes without the impact on other packages/rest of the distribution
+
* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
+
 
+
System Wide Changes are:
+
* changes that does not fit Self Contained Changes category touching
+
* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
+
* changing system defaults
+
 
+
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is
+
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies). 
+
 
+
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
+
-->
+
 
+
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
+
 
+
= Change Proposal Name <!-- The name of your change proposal --> =
+
 
+
== Summary ==
+
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
+
  
 
== Owner ==
 
== Owner ==
<!--
+
* Name: [[User:mclasen| Matthias Clasen]]
For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
+
This should link to your home wiki page so we know who you are.
+
-->
+
* Name: [[User:FASAcountName| Your Name]]
+
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
 
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: <your email address so we can contact you, invite you to meetings, etc.>
+
* Email: mclasen@redhat.com
 
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
 
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
 
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
 
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
 
-->
 
-->
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
+
* Product: Workstation
* Product:
+
* Responsible WG: Workstation
* Responsible WG:
+
-->
+
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
+
* Targeted release: [[Releases/21 | Fedora 21 ]]  
* Last updated: (DATE)
+
* Last updated: 2014-04-03
 
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
 
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
 
Bugzilla states meaning as usual:
 
Bugzilla states meaning as usual:
Line 58: Line 30:
  
 
== Detailed Description ==
 
== Detailed Description ==
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+
The current level of integration into the desktop and applications does not justify enabling the firewalld service by default. Additionally, the set of
 +
zones that it offers is excessive and not user-friendly. Therefore, we will disable the firewall service while we are working on a more user-friendly way
 +
to deal with network-related privacy issues.
 +
 
 +
It will of course still be possible to enable the firewall manually.
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
+
The Workstation will boot faster, and the firewall will not interfere with sharing protocols such as DAAP, UPnP and others.
  
 
== Scope ==
 
== Scope ==
<!-- What work do the developers have to accomplish to complete the change in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
  
* Proposal owners:
+
* Proposal owners:  
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+
  
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Other developers: Add a Workstation-specific service configuration (preset ?) to the firewalld package that disables firewalld for the Workstation product
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+
  
* Release engineering: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Release engineering: No action required
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
+
  
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Policies and guidelines: No action required
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
+
  
 
== Upgrade/compatibility impact ==
 
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
+
Existing systems will keep their service configuration, including the enabled-by-default firewall.
 
+
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
N/A (not a System Wide Change)
+
  
 
== How To Test ==
 
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  
+
# Install the Workstation.
 
+
# Log in
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
+
# run systemctl status firewalld.service
 
+
# expected result: the service is not active
A good "how to test" should answer these four questions:
+
 
+
0. What special hardware / data / etc. is needed (if any)?
+
1. How do I prepare my system to test this change? What packages
+
need to be installed, config files edited, etc.?
+
2. What specific actions do I perform to check that the change is
+
working like it's supposed to?
+
3. What are the expected results of those actions?
+
-->
+
 
+
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
N/A (not a System Wide Change)
+
  
 
== User Experience ==
 
== User Experience ==
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
+
Applications that are using sharing protocols such as DAAP or UPnP will work out of the box, without the need to tweak or disable the firewall service.  
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
N/A (not a System Wide Change)
+
  
 
== Dependencies ==
 
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
+
No dependencies.
 
+
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
N/A (not a System Wide Change)
+
  
 
== Contingency Plan ==
 
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
+
* Contingency mechanism: If the firewalld service can not be disabled, install a simplified set of firewall zones, ideally just 'Home', 'Public' and 'Unknown', and ensure that networks are placed into the 'Home' zone by default
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Contingency deadline: F21 beta
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
+
* Blocks release? No
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Blocks product? Workstation
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
+
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
+
  
 
== Documentation ==
 
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+
This upstream [https://bugzilla.gnome.org/show_bug.cgi?id=727580 bug] discusses improved network privacy handling.
 
+
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
N/A (not a System Wide Change)
+
  
 
== Release Notes ==
 
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
 
  
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
+
The firewalld service is not enabled by default for the Workstation product. To enable it, run systemctl enable firewalld.service.
-->
+
  
[[Category:ChangePageIncomplete]]
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
 
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
 
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
 
  
<!-- Select proper category, default is Self Contained Change -->
+
[[Category:ChangeReadyForWrangler]]
[[Category:SelfContainedChange]]
+
[[Category:SystemWideChange]]
<!-- [[Category:SystemWideChange]] -->
+

Revision as of 04:08, 4 April 2014

Contents

Workstation: Disable firewall

Summary

The firewalld service will not be enabled by default in the workstation product.

Owner

  • Name: Matthias Clasen
  • Email: mclasen@redhat.com
  • Release notes owner:
  • Product: Workstation
  • Responsible WG: Workstation

Current status

  • Targeted release: Fedora 21
  • Last updated: 2014-04-03
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The current level of integration into the desktop and applications does not justify enabling the firewalld service by default. Additionally, the set of zones that it offers is excessive and not user-friendly. Therefore, we will disable the firewall service while we are working on a more user-friendly way to deal with network-related privacy issues.

It will of course still be possible to enable the firewall manually.

Benefit to Fedora

The Workstation will boot faster, and the firewall will not interfere with sharing protocols such as DAAP, UPnP and others.

Scope

  • Proposal owners:
  • Other developers: Add a Workstation-specific service configuration (preset ?) to the firewalld package that disables firewalld for the Workstation product
  • Release engineering: No action required
  • Policies and guidelines: No action required

Upgrade/compatibility impact

Existing systems will keep their service configuration, including the enabled-by-default firewall.

How To Test

  1. Install the Workstation.
  2. Log in
  3. run systemctl status firewalld.service
  4. expected result: the service is not active

User Experience

Applications that are using sharing protocols such as DAAP or UPnP will work out of the box, without the need to tweak or disable the firewall service.

Dependencies

No dependencies.

Contingency Plan

  • Contingency mechanism: If the firewalld service can not be disabled, install a simplified set of firewall zones, ideally just 'Home', 'Public' and 'Unknown', and ensure that networks are placed into the 'Home' zone by default
  • Contingency deadline: F21 beta
  • Blocks release? No
  • Blocks product? Workstation

Documentation

This upstream bug discusses improved network privacy handling.

Release Notes

The firewalld service is not enabled by default for the Workstation product. To enable it, run systemctl enable firewalld.service.