So reading through:
http://web.mit.edu/kerberos/www/krb5-1.4/krb5-1.4.1/doc/krb5-install/Upgrading-to-Triple-DES-and-RC4-Encryption-Keys.html#Upgrading%20to%20Triple-DES%20and%20RC4%20Encryption%20Keys
(the upgrading encryption types page)... regarding this sentence Because of
the way the MIT
On Friday, July 01, 2005 02:14:02 AM -0700 Phil Dibowitz [EMAIL PROTECTED]
wrote:
So reading through:
http://web.mit.edu/kerberos/www/krb5-1.4/krb5-1.4.1/doc/krb5-install/Upgr
ading-to-Triple-DES-and-RC4-Encryption-Keys.html#Upgrading%20to%20Triple-
DES%20and%20RC4%20Encryption%20Keys
On Thu, Jun 30, 2005 at 06:25:08PM -0500, Will Fiveash wrote:
On Thu, Jun 30, 2005 at 05:21:40PM -0400, Ken Hornstein wrote:
I created a presentation PDF a while back that I've placed on the Web
which goes into detail on Kerberos enctypes in terms of how they are
used, negotiated and
I symlinked /etc/v5srvtab to /etc/krb5/krb5.keytab - which is what seam
is looking for.
I looked at the server logs - it's issuing a ticket fine. I even
sniffed the traffic, the as request goes through fine.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf
On Fri, Jul 01, 2005 at 06:03:52AM -0400, Jeffrey Hutzelman wrote:
When responding to an initial ticket request, the KDC chooses three keys:
(1) The key in which the KDC's reply to the client will be encrypted.
This key will be of one of the enctypes the KDC supports.
This key will be
