As a followup to my last post, I attach a proposed change
the Kerberos section of the Windows installation web page:
Kerberos (MIT or Heimdal)
OpenAFS for Windows depends on
a third party Kerberos 5 implementation for network authentication. There
are two supported options:
MIT
Kerberos for Win
Dear OpenAFS community,
OK. I understand that Heimdal doesn't want to make
"allow_weak_crypto = true" be the default. And that due to
the work of dedicated volunteers, later versions of OpenAFS 1.7.X
won't require it, but for now since this will affect EVERYONE
who installs the recommended v
On 1/27/2012 7:42 AM, Harald Barth wrote:
(http://msu.edu/service/afs/AFS-tutorial-Windows7.pdf)
[libdefaults]
default_realm = MSU.EDU
clockskew = 300
300 is default, isn't it?
allow_weak_crypto =3D true
3D is some kind of typo
v4_instance_resolve = false
dns_lookup_kdc= t
> (http://msu.edu/service/afs/AFS-tutorial-Windows7.pdf)
[libdefaults]
default_realm = MSU.EDU
clockskew = 300
300 is default, isn't it?
allow_weak_crypto =3D true
3D is some kind of typo
v4_instance_resolve = false
dns_lookup_kdc= true
The dns option is MIT krb only, isn't it?
Oddly enough I just wrote this today
(http://msu.edu/service/afs/AFS-tutorial-Windows7.pdf) . If its of any
value to anyone let me know and I'll see if I can make it more generic.
Should work if you change the references to MSU.EDU.
I did not need to install the Network Manager software BTW.
On Thu, 26 Jan 2012 13:26:28 -0600
John Tang Boyland wrote:
> (3) If we're stuck with (1) and can't do (2), would anyone like me to
> write up the installation sequence required on the Wiki? And maybe
> the download page could point to it so poor lusers could find it?
> And maybe for
