Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Length: 987

<div dir="ltr">Hello,<div><br></div><div>Iv&#39;e noticed 2 issues regarding the way GSSAPI is loading external mech library, while testing the gss-ntlmssp extrenal mechanism library.</div><div><br></div><div>1. When GSSAPI is fails to load an external mechanism library ponted in /etc/gss/mech.d/some_mech.conf, it doesn&#39;t throw any indicative error when the library file doesn&#39;t exists or dlopen() fails.</div><div><br></div><div><div>2. GSSAPI says it recognizes the external mechanism as supported by using<span class="inbox-inbox-Apple-converted-space"> </span><b>gss_indicate_mechs()<span class="inbox-inbox-Apple-converted-space"> </span></b>even if the mech library doesn&#39;t really exist or dlopen() fails. means it only looking for the mech OID in external mech .conf file in /etc/gss/mech.d/. </div><div><br></div></div><div>Those 2 issues can make a  confusion for users/developers.</div><div><br></div><div>Thanks for your efforts,</div><div>Idan.</div></div>