Coda File System

updateclient/updateserver endian problem??

From: Troy Benjegerdes <hozer_at_drgw.net>
Date: Mon, 28 Jun 1999 19:30:53 -0500 (CDT)
It appear that updateclient and updateserver can't talk between my PPC and
x86 boxes.

I was planning on setting up coda servers on a PPC box and an AMD K6
machine, after building coda-5.2.7 with kerberos support, I can't get
either machine to successfully updated from the other.

I always get a 19:24:07 Bind failed with RPC2_NOBINDING (F) .

I ran updateclient on a second PPC and second x86 box, and each can talk
to machines of similiar endianness correctly. So, where do I go to try and
fix this.

Also, something else I noticed.. Does updateclient have any access control
at all, or does it let anything update all of the files (inlude auth2.tk
and volutil.tk) This would seem to me to be a rather large security hole.

(Along those lines, what would it take to use Kerberos's
encryption/authentication routines in the RPC2 code?)

--------------------------------------------------------------------------
| Troy Benjegerdes    |       troy_at_microux.com     |    hozer_at_drgw.net   |
|    Unix is user friendly... You just have to be friendly to it first.  |
| This message composed with 100% free software.    http://www.gnu.org   |
--------------------------------------------------------------------------
Received on 1999-06-28 20:29:40