While testing gssproxy in conjunction with libssh and it's examples I have discovered 2 glaring issues in the interposer.
1. We were 'forgetting' to send to the gssproxy the requested flags and lifetime when initializing a context ... oops!
2. We passed an internal special oid to client mechglue functions that should only see real oids, this cause gss_inquire_creds_by_mech to fail as internally the mechanism wouldn't match and we'd return an error.
Simo.
Hi Simo,
these look fine, reviewed and pushed to master. They address tickets #106 and #107 AFAICT.
Thanks!
Guenther
On 14/11/13 01:19, Simo Sorce wrote:
While testing gssproxy in conjunction with libssh and it's examples I have discovered 2 glaring issues in the interposer.
- We were 'forgetting' to send to the gssproxy the requested flags and
lifetime when initializing a context ... oops!
- We passed an internal special oid to client mechglue functions that
should only see real oids, this cause gss_inquire_creds_by_mech to fail as internally the mechanism wouldn't match and we'd return an error.
Simo.
gss-proxy mailing list gss-proxy@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/gss-proxy
On Tue, 2013-11-19 at 14:07 +0100, Günther Deschner wrote:
Hi Simo,
these look fine, reviewed and pushed to master. They address tickets #106 and #107 AFAICT.
Yes indeed, thanks! Simo.
Thanks!
Guenther
On 14/11/13 01:19, Simo Sorce wrote:
While testing gssproxy in conjunction with libssh and it's examples I have discovered 2 glaring issues in the interposer.
- We were 'forgetting' to send to the gssproxy the requested flags and
lifetime when initializing a context ... oops!
- We passed an internal special oid to client mechglue functions that
should only see real oids, this cause gss_inquire_creds_by_mech to fail as internally the mechanism wouldn't match and we'd return an error.
Simo.
gss-proxy mailing list gss-proxy@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/gss-proxy
gss-proxy@lists.fedorahosted.org