Projects/Improve GSSAPI mechanism configuration - Revision history

Ghudson: /* Commits */

2014-08-12T17:57:38Z

‎Commits

Ghudson at 17:51, 12 August 2014

2014-08-12T17:51:59Z

Ghudson at 16:35, 12 August 2014

2014-08-12T16:35:16Z

BenKaduk: spell 'each' correctly

2013-10-18T19:44:30Z

spell 'each' correctly

Simo at 18:16, 18 October 2013

2013-10-18T18:16:05Z

Simo: New page: ==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. ...

2013-10-18T18:15:36Z

New page: ==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. ...

New page

==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 ech 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.

@@ Line 23: / Line 23: @@
 ==Commits==
-* 123c14fd8862ee8f11f6084d25958cb380655f35 Remove dead code from the mechglue initialization
+c14fd8862ee8f11f6084d25958cb380655f35 Remove dead code from the mechglue initialization
-* 05cbef80d53f49d30a5d0563501226dc173734d4 Load mechglue config files from /etc/gss/mech.d
+cbef80d53f49d30a5d0563501226dc173734d4 Load mechglue config files from /etc/gss/mech.d
-* 406f273e373014edc0ec31995dc82d6b7a5d73f8 Document /etc/gss/mech.d/*.conf
+f273e373014edc0ec31995dc82d6b7a5d73f8 Document /etc/gss/mech.d/*.conf
 ==Release notes==

← Older revision		Revision as of 17:51, 12 August 2014
Line 20:		Line 20:

	host_config.rst and gssapi.rst will be updated to document /etc/gss/mech.d.		host_config.rst and gssapi.rst will be updated to document /etc/gss/mech.d.
		+
		+	==Commits==
		+
		+	* 123c14fd8862ee8f11f6084d25958cb380655f35 Remove dead code from the mechglue initialization
		+	* 05cbef80d53f49d30a5d0563501226dc173734d4 Load mechglue config files from /etc/gss/mech.d
		+	* 406f273e373014edc0ec31995dc82d6b7a5d73f8 Document /etc/gss/mech.d/*.conf

	==Release notes==		==Release notes==

@@ Line 1: / Line 1: @@
-{{project-early}}
+{{project-rel|1.13}}
 ==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.
+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.
+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 single configuration file.
 ==Design==
-A new directory owned by the GSSAPI library is created in /etc/gss/mech.d
+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.
+After the main /etc/gss/mech file has been parsed, any file in this directory with a name ending in ".conf" is opened and parsed to find additional mechanisms to load.

← Older revision		Revision as of 18:16, 18 October 2013
Line 1:		Line 1:
		+	{{project-early}}
		+	{{project-target\|1.13}}

	==Requirements and scope==		==Requirements and scope==