Discussion:
gss_store_cred and the gss_krb5_ccache_name
Sorin Manolache
2016-12-03 09:46:50 UTC
Permalink
Hello,

It seems that gss_store_cred does not store the credentials in the
ccache whose name was previously set by gss_krb5_ccache_name as the
default ccache.

Could you please confirm that that is the case?

Is it an intentional design decision or an omission?

And an unrelated question: is there a way to determine at application
compilation time the major/minor/revision numbers of the krb5 library
the application is linked with? Some macro for example, such that the
application contain #ifdefs with branches specific to each library version?

Thank you,
Sorin
_______________________________________________
krbdev mailing list ***@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
Greg Hudson
2016-12-05 17:05:51 UTC
Permalink
Post by Sorin Manolache
It seems that gss_store_cred does not store the credentials in the
ccache whose name was previously set by gss_krb5_ccache_name as the
default ccache.
Could you please confirm that that is the case?
Is it an intentional design decision or an omission?
That is the case. gss_store_cred() needs a lot of attention; this and
other problems are noted in
http://krbdev.mit.edu/rt/Ticket/Display.html?id=8010 .
Post by Sorin Manolache
And an unrelated question: is there a way to determine at application
compilation time the major/minor/revision numbers of the krb5 library
the application is linked with? Some macro for example, such that the
application contain #ifdefs with branches specific to each library version?
There is not. Every time we have talked about it, we have decided not
to do it. One potential issue is that downstream distributions of MIT
krb5 sometimes backport changes to earlier releases when we do not.
_______________________________________________
krbdev mailing list ***@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev

Loading...