[4587] in Moira
Re: pulling up moira-krb5 branch changes to mainline
daemon@ATHENA.MIT.EDU (Garry Zacheiss)
Fri Aug 25 15:52:38 2006
Message-Id: <200608251952.k7PJqNXG003118@sipb-office-escape-pod.mit.edu>
To: Garry Zacheiss <zacheiss@MIT.EDU>
cc: moiradev@MIT.EDU, moira-admin@MIT.EDU
In-Reply-To: Message from Garry Zacheiss <zacheiss@MIT.EDU>
of "Wed, 23 Aug 2006 15:52:02 EDT." <200608231952.k7NJq2SY011610@w92-spare-sunblade-100.mit.edu>
Date: Fri, 25 Aug 2006 15:52:23 -0400
From: Garry Zacheiss <zacheiss@MIT.EDU>
>> I've put builds of the new clients for sun4x_510 and i386_rhel4 in the
>> moiradev locker. These clients will do krb5 auth to the server running
>> on ttsp but will fall back to krb4 when talking to the production
>> server, so it should be safe to "add -f moiradev" and use them for
>> everything. If you do so, please report any problems you run into.
I've updated these builds with the handful of little changes:
- chfn: Implement -db command line option to specify alternate server,
for easier testing.
- mailmaint: Replace unnecessary use of krb4 tf_* APIs with a call to
mrcl_krb_user.
- mrtest: Include new "auth_krb4" / "4" command in usage message.
mrtest is the one app for which I didn't implement fallback to v4 auth
if the server doesn't support v5, because I wanted each command to
correspond to only one RPC to the server (for simplicity of testing)
so if you're using the new mrtest to talk to the production moira
server, "a" will fail, but "4" will succeed.
Garry
