[32260] in Kerberos
no renewable flag in krb5.conf ?
daemon@ATHENA.MIT.EDU (Guillaume Rousse)
Tue Apr 13 07:58:02 2010
Message-ID: <4BC45C3E.8010708@inria.fr>
Date: Tue, 13 Apr 2010 13:57:50 +0200
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
MIME-Version: 1.0
To: kerberos@mit.edu
Content-Type: multipart/mixed; boundary="===============0812221642=="
Errors-To: kerberos-bounces@mit.edu
This is a cryptographically signed message in MIME format.
--===============0812221642==
Content-Type: multipart/signed; protocol="application/pkcs7-signature";
micalg=sha1; boundary="------------ms060406070005020600010403"
This is a cryptographically signed message in MIME format.
--------------ms060406070005020600010403
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hello.
I just realized than it was possible to force forwardable tickets
through krb5.conf, but not renewable ones. Is it intentional ?
For instance, the following doesn't work as expected:
[appdefaults]
pam =3D {
forwardable =3D true
renewable =3D true
}
--=20
BOFH excuse #180:
ether leak
--------------ms060406070005020600010403--
--===============0812221642==
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
--===============0812221642==--
