Features/gss-proxy

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Feature gss-proxy has been accepted for F18 by FESCo on the Jul 16 meeting (ticket #893))
(Dependencies)
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
<!-- {{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}-->
 
<!-- {{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}-->
 
 
 
<!-- All fields on this form are required to be accepted by FESCo.
 
<!-- All fields on this form are required to be accepted by FESCo.
 
  We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
 
  We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
 
 
<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name.  This keeps all features in the same namespace -->
 
<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name.  This keeps all features in the same namespace -->
 
 
= GSS Proxy <!-- The name of your feature --> =
 
= GSS Proxy <!-- The name of your feature --> =
  
Line 26: Line 22:
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/18 | Fedora 18 ]]  
+
* Targeted release: [[Releases/19 | Fedora 19 ]]  
* Last updated: 2012/06/30
+
* Last updated: 2013-05-14
* Percentage of completion: 90%
+
* Percentage of completion: 100%
  
 
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
 
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
Line 39: Line 35:
 
are several motivations for this some of which are:
 
are several motivations for this some of which are:
  
- Kernel-mode GSS-API applications (CIFS, NFS, AFS, ...) need to be
+
* Kernel-mode GSS-API applications (CIFS, NFS, AFS, ...) need to be able to leave all complexity of GSS_Init/Accept_sec_context() out of the kernel by upcalling to a daemon that does all the dirty work.
  able to leave all complexity of GSS_Init/Accept_sec_context() out of
+
* Isolation and privilege separation for user-mode applications. For example: letting HTTP servers use but not see the keytab entries for HTTP/* principals for accepting security contexts.
  the kernel by upcalling to a daemon that does all the dirty work.
+
* Possibly an ssh-agent-like SSH agent for GSS credentials -- a gss-agent.
 
+
- Isolation and privilege separation for user-mode applications. For
+
  example: letting HTTP servers use but not see the keytabe entries for
+
  HTTP/* principals for accepting security contexts.
+
 
+
- Possibly an ssh-agent-like SSH agent for GSS credentials -- a
+
  gss-agent.
+
  
 
In order to use the gssproxy only the gssproxy daemon has to be started at boottime. Once this is done, the GSSAPI mechglue library will make sure all GSSAPI calls issued by an application are directed to the gssproxy service transparently. Depending on the configuration of the system, the gssproxy daemon will then allow or disallow access to cryptographic keys stored in keytabs on the system.
 
In order to use the gssproxy only the gssproxy daemon has to be started at boottime. Once this is done, the GSSAPI mechglue library will make sure all GSSAPI calls issued by an application are directed to the gssproxy service transparently. Depending on the configuration of the system, the gssproxy daemon will then allow or disallow access to cryptographic keys stored in keytabs on the system.
  
 +
Two major features that are planned to be achieved for Fedora19:
 +
* rpc.gssd, the NFS client application, should be enabled to use the gssproxy. It will be possible to aquire tickets for kerberized NFS mounts given user keytabs.
 +
* gssproxy will offer Kerberos ticket renewal when user keytabs are available
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
Line 57: Line 49:
  
 
The key benefit for Fedora will be that we can provide more fine grained control over controlling access of applications to highly sensible cryptographic key material (keytabs). This in general improves security on the system.
 
The key benefit for Fedora will be that we can provide more fine grained control over controlling access of applications to highly sensible cryptographic key material (keytabs). This in general improves security on the system.
 
 
== Scope ==
 
== Scope ==
 
<!-- What work do the 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?-->
 
<!-- What work do the 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?-->
  
Work on the GSSAPI mechglue library is in progress but is currently not finished.
+
Gssproxy and all depending components are appropriately changed, all changes are part of the upstream projects and integrated in Fedora to provide a proxy infrastructure for GSSAPI. The gssproxy mechglue library is packaged and can be loaded from the GSSAPI version shipped on Fedora 19.
 
+
In order to properly load our mechglue library, some modifications to the system GSSAPI/Kerberos library (MIT) are required. Work on this has well progressed and is coordinated with upstream (MIT).
+
  
 
== How To Test ==
 
== How To Test ==
Line 80: Line 69:
 
-->
 
-->
  
Currently we use a test program (shipped with the main tarball) in order to do basic testing of our implementation. Once the mechglue interface is in place, any tests done for the GSSAPI interface itself would allow to test the gssproxy as well.  
+
Currently we use two test programs (shipped with the main tarball) in order to do basic testing of our implementation. With the mechglue interface is in place, any tests done for the GSSAPI interface itself allow to test the gssproxy as well.  
  
 
For the current testing you need to have a working KDC, one needs to create a keytab and gssproxy needs to be properly installed and configured.
 
For the current testing you need to have a working KDC, one needs to create a keytab and gssproxy needs to be properly installed and configured.
Line 92: Line 81:
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature 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 feature)? -->
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature 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 feature)? -->
  
The kernel will use the gssproxy interface.
+
The kernel nfs server can benefit from the gssproxy interface in version 3.10.
 
+
  
 
== Contingency Plan ==
 
== Contingency Plan ==
Line 105: Line 93:
 
* The gssproxy project wiki page of the MIT Consortium: [http://k5wiki.kerberos.org/wiki/Projects/ProxyGSSAPI]
 
* The gssproxy project wiki page of the MIT Consortium: [http://k5wiki.kerberos.org/wiki/Projects/ProxyGSSAPI]
 
* Protocol Documentation is available online as well: [https://fedorahosted.org/gss-proxy/].
 
* Protocol Documentation is available online as well: [https://fedorahosted.org/gss-proxy/].
 
  
 
== Release Notes ==
 
== Release Notes ==
Line 116: Line 103:
  
  
[[Category:FeatureAcceptedF18]]
+
[[Category:FeatureAcceptedF19]]
 
<!-- When your feature page is completed and ready for review -->
 
<!-- When your feature page is completed and ready for review -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Latest revision as of 14:53, 14 May 2013

Contents

[edit] GSS Proxy

[edit] Summary

The main purpose of this project is to replace rpc.svcgssd(8), the server-side rpcsec_gss daemon.

The gss-proxy consists of a standardized RPC protocol, a client and server implementation with other future components. The gss-proxy protocol allows proxying of GSSAPI initiation and authentication.

[edit] Owner

  • Email: <ssorce@redhat.com>

[edit] Current status

  • Targeted release: Fedora 19
  • Last updated: 2013-05-14
  • Percentage of completion: 100%


[edit] Detailed Description

The goal is to have a GSS-API proxy, with standardizable protocol and a [somewhat portable] reference client and server implementation. There are several motivations for this some of which are:

  • Kernel-mode GSS-API applications (CIFS, NFS, AFS, ...) need to be able to leave all complexity of GSS_Init/Accept_sec_context() out of the kernel by upcalling to a daemon that does all the dirty work.
  • Isolation and privilege separation for user-mode applications. For example: letting HTTP servers use but not see the keytab entries for HTTP/* principals for accepting security contexts.
  • Possibly an ssh-agent-like SSH agent for GSS credentials -- a gss-agent.

In order to use the gssproxy only the gssproxy daemon has to be started at boottime. Once this is done, the GSSAPI mechglue library will make sure all GSSAPI calls issued by an application are directed to the gssproxy service transparently. Depending on the configuration of the system, the gssproxy daemon will then allow or disallow access to cryptographic keys stored in keytabs on the system.

Two major features that are planned to be achieved for Fedora19:

  • rpc.gssd, the NFS client application, should be enabled to use the gssproxy. It will be possible to aquire tickets for kerberized NFS mounts given user keytabs.
  • gssproxy will offer Kerberos ticket renewal when user keytabs are available

[edit] Benefit to Fedora

The key benefit for Fedora will be that we can provide more fine grained control over controlling access of applications to highly sensible cryptographic key material (keytabs). This in general improves security on the system.

[edit] Scope

Gssproxy and all depending components are appropriately changed, all changes are part of the upstream projects and integrated in Fedora to provide a proxy infrastructure for GSSAPI. The gssproxy mechglue library is packaged and can be loaded from the GSSAPI version shipped on Fedora 19.

[edit] How To Test

Currently we use two test programs (shipped with the main tarball) in order to do basic testing of our implementation. With the mechglue interface is in place, any tests done for the GSSAPI interface itself allow to test the gssproxy as well.

For the current testing you need to have a working KDC, one needs to create a keytab and gssproxy needs to be properly installed and configured.

[edit] User Experience

The usage of the gssproxy protocol and implementation is completely transparent for the user. Also applications do not need to be modified in order to benefit from the gssproxy.

[edit] Dependencies

The kernel nfs server can benefit from the gssproxy interface in version 3.10.

[edit] Contingency Plan

In case the gssproxy is not complete by the end of the final development freeze, Fedora can just decide to not ship it.

[edit] Documentation

  • The gssproxy project wiki page of the MIT Consortium: [1]
  • Protocol Documentation is available online as well: [2].

[edit] Release Notes

  • gssproxy is an opensource project that aims to improve GSSAPI usage from both the kernel (for authenticating remote file system access) as well as user-space applications. It does provide fine-grained access control on Kerberos keytab access and it overcomes various limitations the kernel had when dealing with Kerberos tickets.

[edit] Comments and Discussion