[38559] in Kerberos

home help back first fref pref prev next nref lref last post

Relation between krb5_creds and krb5_context

daemon@ATHENA.MIT.EDU (Philipp Gesang)
Tue Jul 16 10:29:42 2019

Date: Tue, 16 Jul 2019 16:23:24 +0200
From: Philipp Gesang <philipp.gesang@intra2net.com>
To: <kerberos@mit.edu>
Message-ID: <20190716142324.GB14090@drift.m.i2n>
Mail-Followup-To: kerberos@mit.edu
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1169871703034174309=="
Errors-To: kerberos-bounces@mit.edu

--===============1169871703034174309==
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="LyciRD1jyfeSSjG0"
Content-Disposition: inline

--LyciRD1jyfeSSjG0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi,

what is the significance of the krb5_context that
krb5_free_creds() takes as its first argument? As far as I can
see none of the functions down the call graph do anything with it
nor is the context stored in krb5_creds and its members.
Nevertheless, the API expects non-const pointer to be passed.

My reflex is to simply pass NULL instead of the context. I am
wondering though how future-proof this will be. Are credentials
somehow tied to the context they were obtained with?

FWIW the question came up in the context (n. p. i.) of keeping
credentials around in memory and accessing them from threads that
each have their own krb5_context.

Thanks,
Philipp


--LyciRD1jyfeSSjG0
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEc8fuSIDXOZ07wD2Q8S2brBeKCUwFAl0t3dgACgkQ8S2brBeK
CUwL7xAAjWoF8ur5uWI4RCWBNSf9FIyLqHs59AT5sCVsofeBtn0xi0ofwYon1qFZ
LppfoLpyd+Q6kJnLvNrKeulwwwTGnEOG9UYbwzKLzCKigxjsfHCAictDIds97je+
ZviNsl5gl/oC4kxZBGU8reL57xyPguVKsgocak7UOOf1sDri2GdePOY0lf8ELvmp
SkeAV+OVmwHsUPZH9S+tVc3BvH6UUHjoQihtOpnrwBMv1gSt+mE+vX6jGIU8fJrG
1ewjc+YiAf8PhpD0nRVUr0HkLlqn6ZgRM6WDQ2gvBXTSKwKnNpYc3nDHf4VUgLcs
zEMDqzp5VdWvrWOhE/e7OCX/4GJESaXMkTq61dr3rhyzShX0eY2eTlvk4jAXBeF7
YZIRqupoiXDpvYJF3lF7jATyBGBn9WuuzLXuxawY6DEeV80XrC5tvHEkrbKyuvna
ZLCewcf6m4E/EQonTZIwGfNlzKLFPIG+aAnwXwMw6Eb5ry4oftD8kPiJCDYBKBHs
zbX5I14BOGMUjIKmmAP5fpkE2mr+bLI8/4DBVPJr3Us8O+5wlS3lxTSYe/eKtYho
DUmFUYJomRnGKEbqXsQ9wMKfoN5qmaguf5ng0V0WEeYyd37ZnvMQ8lAYuw6a/vvV
YmPF9GgkluTidbAK4nVFpjdK3K9S3neeVv7GaQ79UspJJxR0MdI=
=RrAM
-----END PGP SIGNATURE-----

--LyciRD1jyfeSSjG0--

--===============1169871703034174309==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

--===============1169871703034174309==--

home help back first fref pref prev next nref lref last post