| 1 |
This little document is about the current behavior of the GSSProxy and the |
| 2 |
libgssapi interposer plugin. |
| 3 |
Each is documented separately. |
| 4 |
|
| 5 |
Note that the GSSProxy act as server not only for the interposer plugin but |
| 6 |
also directly for the kernel and potentially for other clients, so the proxy |
| 7 |
behavior may include additional behaviors not directly available to the |
| 8 |
libgssapi interposer plugin. |
| 9 |
|
| 10 |
NOTE: |
| 11 |
This document should be upgraded every time we change the proxy or the plugin |
| 12 |
behavior, however it is my experience that developers forget to do so, so here |
| 13 |
we have also a timestamp from the last update: |
| 14 |
20120910 |
| 15 |
|
| 16 |
If it is way too much in the past then something in the actual code may not |
| 17 |
reflect this document anymore, and please yell at the current maintainer to |
| 18 |
bring it up to date :-) |
| 19 |
|
| 20 |
|
| 21 |
GSS Proxy |
| 22 |
----------------------------------------------------------------------------- |
| 23 |
|
| 24 |
|
| 25 |
Application based behavior: |
| 26 |
Currently GSS Proxy can be configure to behave differently for each 'user' |
| 27 |
connecting to it. By user here we really mean euid at this point (we are |
| 28 |
planning to make it possible to act on a per-application basis provided SELinux |
| 29 |
is used and each application has a different label that can be trasmitted via |
| 30 |
SM Rights like calls). |
| 31 |
|
| 32 |
The euid is obtained through a SCM Rigths call on the Unix Socket used to talk |
| 33 |
to the proxy. |
| 34 |
|
| 35 |
Each euid can have a config entry which can specify whether the euid is trusted |
| 36 |
or not and based on specific mechanism some options. The currently only |
| 37 |
supported mechanism is krb5. For this mechanism a euid specific keytab and |
| 38 |
ccache can be specified. |
| 39 |
|
| 40 |
When a 'user' is considered trusted it means it is allowed to command gss-proxy |
| 41 |
to act on behalf of another user (for example init a context as a user |
| 42 |
specified in an optional field in the protocol). |
| 43 |
|
| 44 |
The following table represent the current thinking around default/allowed |
| 45 |
behavior depending on the connecting peer: |
| 46 |
|
| 47 |
-------------------------------------------------------------------- |
| 48 |
| Operation | Initiate | Accept | |
| 49 |
|Peer | | | |
| 50 |
-------------------------------------------------------------------- |
| 51 |
| |With ccache available | Never allow to accept for | |
| 52 |
|euid not |always try to init | unconfigured euids | |
| 53 |
|explicitly | | | |
| 54 |
|configured in |Use default ccache | | |
| 55 |
|gssproxy.conf |defined in [global] | | |
| 56 |
| | | | |
| 57 |
| |Never use keytab | | |
| 58 |
---------------|----------------------|----------------------------- |
| 59 |
| |With ccache available | If keytab is explicitly | |
| 60 |
|euid X |always try to init | configured always allow to | |
| 61 |
|(referenced | | try to accept via proxy | |
| 62 |
| explicitly |When keytab available | | |
| 63 |
| in a config |init with keytab only | | |
| 64 |
| section) |if following option | | |
| 65 |
| |is set to True: | | |
| 66 |
| |krb5_init_with_keytab | | |
| 67 |
| |defaults to False | | |
| 68 |
---------------|----------------------|----------------------------- |
| 69 |
| | | If keytab is explicitly | |
| 70 |
|euid 0 | | configured always allow to | |
| 71 |
| | | try to accept via proxy | |
| 72 |
| | | | |
| 73 |
| | | Allow to fallback to host | |
| 74 |
| | | keytab if not configured ? | |
| 75 |
-------------------------------------------------------------------- |
| 76 |
|
| 77 |
|
| 78 |
|
| 79 |
Credentials: |
| 80 |
At the moment the GSS Proxy cannot be fully stateless due to limitations in |
| 81 |
GSSAPI (they are being addressed in MIT 1.11). The gss-proxy keeps a list of |
| 82 |
credential structs in a ring buffer and sends applications an encrypted token to |
| 83 |
reference them when the same credential needs to be used across multiple calls. |
| 84 |
|
| 85 |
Contexts: |
| 86 |
Context are always exported to the clients once obtained. |
| 87 |
Currently both lucid-type contexts and native MIT format contexts are |
| 88 |
supported. |
| 89 |
|
| 90 |
|
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
libgssapi Interposer Plugin |
| 97 |
----------------------------------------------------------------------------- |
| 98 |
|
| 99 |
The Interposer plugin currently tries to perform local only operations first |
| 100 |
and falls back to try proxy communication if it can't obtain |
| 101 |
contexts/credentials using local calls. |
| 102 |
Also an environment variable can be used to change this behavior somewhat |
| 103 |
(NOTE: still inconsistent while developing the feature). The variable is |
| 104 |
called: GSSPROXY_BEHAVIOR and allowed values are: LOCAL_ONLY, LOCAL_FIRST, |
| 105 |
REMOTE_ONLY, REMOTE_FIRST. |
| 106 |
|
| 107 |
Currently only a hardcoded set of mechanism is supported, however in future it |
| 108 |
is planned that the supported set of mechanism to be queried from the gssproxy |
| 109 |
and/or the configuration file instead. |
| 110 |
|
| 111 |
|