vladimir konrad <[EMAIL PROTECTED]> writes:
> oops
> the aklog -524 succeeds, so it is something to do with our kerberos
> configuration...
> strange that the sarge doesn not need -524 option though...
The sarge version of aklog predates the native K5 support in AFS and
therefore does -524 by d
Begin forwarded message:
Date: Fri, 27 Oct 2006 15:36:10 +0100
From: vladimir konrad <[EMAIL PROTECTED]>
To: Sam Hartman <[EMAIL PROTECTED]>
Subject: Re: Bug#395015: openafs-krb5: kinit + aklog succeeds but the /afs
access does not work (works with afslog from heimdal-clients)
> Make sure your openafs kernel module and openafs-client package are
> both upgraded to 1.4.2-2
one of the things i noticed, in our kerberos database there is a principal
afs@ but no principal afs/@.
also, the aklog produces different log entries on the krb5kdc:
aklog from sarge - afs@
aklog fr
severity 395015 normal
thanks
Other people are not seeing this; I seriously doubt it is grave.
Make sure your openafs kernel module and openafs-client package are
both upgraded to 1.4.2-2
Try that.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contac
Package: openafs-krb5
Version: 1.4.2~fc4-3
Severity: grave
Justification: renders package unusable
doing a test configuration of debian etch, i found that openafs-krb5:aklog
does something wrong (this is using debian etch as client and debian woody
as kerberos and openafs server).
the kinit + ak
5 matches
Mail list logo
