From Fedora Project Wiki
(create)
 
 
(9 intermediate revisions by 2 users not shown)
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 "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
<!-- 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 -->
<!-- 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 -->


Line 13: Line 10:
* Name: [[User:rharwood| Robbie Harwood (rharwood)]]
* Name: [[User:rharwood| Robbie Harwood (rharwood)]]
<!-- 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: rharwood at
* Email: rharwood at f p dot o
* 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> -->[mailto:sclark@fedoraproject.org Simon Clark] ([[User:sclark|sclark]])
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCoshepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCoshepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 34: Line 31:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1474829 #1474829]


== Detailed Description ==
== Detailed Description ==
Line 47: Line 44:


== Scope ==
== Scope ==
* Proposal owners: rharwood
* Proposal owners: To implement this Change proposal.
<!-- 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?-->
<!-- 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)
* Other developers: N/A (not a System Wide Change)


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
* Release engineering: [https://pagure.io/releng/issue/6854 #6854] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
Line 78: Line 75:
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change), Yes/No
* Blocks release? N/A (not a System Wide Change)
* Blocks product? N/A
* Blocks product? N/A


Line 88: Line 85:
Both krb5-appl-clients and krb5-appl-servers have been removed from Fedora.  Users are suggested to move to better security tools, such as openssh.
Both krb5-appl-clients and krb5-appl-servers have been removed from Fedora.  Users are suggested to move to better security tools, such as openssh.


[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF27]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Latest revision as of 19:18, 3 November 2017


Remove krb5-appl

Summary

Remove src:krb5-appl (produces packages krb5-appl-clients and krb5-appl-servers) from the distribution.

Owner

Current status

Detailed Description

These packages will likely be officially deprecated upstream soon, and probably should not be used in most cases anyway. It contains legacy kerberized utilities, like rsh. There are no packages which depend them. There have been no changes to this package in Fedora since 2013, and no new capabilities upstream since 2010 when it branched from the mainline krb5 distribution.

Benefit to Fedora

Remove obsolete packages that no longer provide the level of security we would like.


Scope

  • Proposal owners: To implement this Change proposal.
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: #6854 (a check of an impact with Release Engineering is needed)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change)
  • Blocks product? N/A

Documentation

N/A (not a System Wide Change)

Release Notes

Both krb5-appl-clients and krb5-appl-servers have been removed from Fedora. Users are suggested to move to better security tools, such as openssh.