Difference between revisions of "Projects/Improve GSSAPI mechanism configuration"
m (spell 'each' correctly) |
|||
| Line 6: | Line 6: | ||
The GSSAPI mechglue allows the installation of additional mechanisms, these mechanisms are currently sourced from the file /etc/gss/mech at library load time. |
The GSSAPI mechglue allows the installation of additional mechanisms, these mechanisms are currently sourced from the file /etc/gss/mech at library load time. |
||
| − | In order to improve management of additional mechanism as separate packages for distributions it would be easier if |
+ | In order to improve management of additional mechanism as separate packages for distributions it would be easier if each package could drop a configuration fragment in a separate file to activate a new installed plugin instead of changing a signle configuration file. |
==Design== |
==Design== |
||
Revision as of 15:44, 18 October 2013
Requirements and scope
The GSSAPI mechglue allows the installation of additional mechanisms, these mechanisms are currently sourced from the file /etc/gss/mech at library load time.
In order to improve management of additional mechanism as separate packages for distributions it would be easier if each package could drop a configuration fragment in a separate file to activate a new installed plugin instead of changing a signle configuration file.
Design
A new directory owned by the GSSAPI library is created in /etc/gss/mech.d In this directory packages can drop configuration fragments that use the exact same configuration format of the current /etc/gss/mech file.
After the main /etc/gss/mech file has been parsed, any file in this directory is opened and parsed to find additional mechanisms to load.
