Hi all,
Into a fresh installation of the latest OpenAFS for Windows, with the
kernel module and without the loopback adapter, when i contact the AFS
(\\afs), soon the explorer.exe closes and restart.
Into Event Log i have only this:
La shell si è arrestata in maniera non prevista. Explorer.exe
Please send bug reports to openafs-b...@openafs.org.
For an explorer shell abnormal termination information which is useful
includes:
1. A description of the OS version, machine vendor, etc.
2. any minidumps collected by Dr.Watson
3. a list of all explorer shell extensions installed on the mach
I've the same problem. I've already sent a bug report [rt.central.org
#130343].
But I didn't include the infos mentioned by Jeffrey... tomorrow.
Mit freundlichen Grüßen
Michael Richter
schrieb Claudio Prono:
Hi all,
Into a fresh installation of the latest OpenAFS for Windows, with the
kernel
I'm a little confused. I just had to turn on
allow_weak_crypto in a RHEL6 kerberos client's
/etc/krb5.conf to be able to aklog.
My understanding was that this setting was only
needed on the KDCs, which until now, has been
working fine since we upgraded our KDCs to 1.9.
Is that just because our
On 11/22/2011 3:28 PM, Jeff Blaine wrote:
> Is that just because our other clients are (they
> are) running sub-1.9 MIT Kerberos so we didn't hit
> this?
Yes.
signature.asc
Description: OpenPGP digital signature
On 22 Nov 2011, at 20:28, Jeff Blaine wrote:
> I'm a little confused. I just had to turn on
> allow_weak_crypto in a RHEL6 kerberos client's
> /etc/krb5.conf to be able to aklog.
>
> My understanding was that this setting was only
> needed on the KDCs, which until now, has been
> working fine s
In later versions of OpenAFS we work round this by having aklog use a krb5
function to enable weak crypto for that specific context, but I guess you
aren't using that version of OpenAFS yet.
We're using 1.4.14.1
___
OpenAFS-info mailing list
OpenAFS-
An aside...
Simon Wilkinson wrote:
> You need the setting on the KDCs, because otherwise they won't issue any
> single DES tickets, regardless of the encryption types set for the afs/
> principal. But ...
>
> You also need this setting on all of your clients, because otherwise you
> won't be
On Tue, Nov 22, 2011 at 23:35, Atro Tossavainen
wrote:
> If OpenAFS with Kerberos 5 still uses single DES only, how is it
> fundamentally better security-wise than using kaserver...?
>
The Kerberos 4 protocol (including the ancient variant used by kaserver)
has significant *structural* security f
