Better handling of desired_mechs
authorSimo Sorce <simo@redhat.com>
Tue, 16 Jun 2015 19:07:37 +0000 (15:07 -0400)
committerSimo Sorce <simo@redhat.com>
Fri, 19 Jun 2015 20:42:29 +0000 (16:42 -0400)
commit6e4513dc0ebe5ff6643223d35b509464d451b230
tree9b98f07c0ed50ea884702a7c60e8f2f530cadc29
parentd0732a69720d78a24d1565a38403c12d273d4ac9
Better handling of desired_mechs

If no explicit allowed mechanism is set in configuration just ask
GSSAPI for a list of known mechanisms and use that. Do not try to
artificially acquire credentials as ultimatily all that does is
just call gss_inidicate_mechs() internally.

Do not store the result of gss_inidicate_mechs() on cfg->allowed_mechs
as that would lead to a leak given that cfg->allowed_mechs is allocated
on a memory pool, while gss_inidate_mechs()s results are not.

Closes #44

Signed-off-by: Simo Sorce <simo@redhat.com>
src/mod_auth_gssapi.c