[9fans] AuthInfo.cuid and suid

[9fans] AuthInfo.cuid and suid

[YAMANASHI Takeshi]

My old 4th ed. has the line:

  % nashi@valinore grep -n mkcap /sys/src/cmd/auth/factotum/rpc.c
  329: 		fss->ai.cap = mkcap(r->fid->uid, fss->ai.cuid);

  % nashi@valinore ls -l /sys/src/cmd/auth/factotum/rpc.c
  --rw-rw-r-- M 9 sys sys 10229 Jun 29  2002 /sys/src/cmd/auth/factotum/rpc.c

On the other hand, the recent factotum has the line:

  cpu% grep -n mkcap  /sys/src/cmd/auth/factotum/rpc.c
  341: 		fss->ai.cap = mkcap(r->fid->uid, fss->ai.suid);

Why cuid was changed to suid while cuid remains in many places like
cpu.c?  What is the difference between them?

The following description in auth(2) did't clear my confusion...

          The fields cuid and suid point to the authenticated ids of
          the client and server.  Cap is a capability returned only to
          the server.
-- 

Re: [9fans] AuthInfo.cuid and suid

[Russ Cox]

At one point there was a notion that ai.cuid would be
the name the user used on the client, while ai.suid would
be the name on the server.  Since the client name isn't
authenticated at all, suid == cuid.  The right one to use
is suid but it doesn't matter.

Russ

Re: [9fans] AuthInfo.cuid and suid

[YAMANASHI Takeshi]

On Tue Jul  5 03:19:09 JST 2005, Russ Cox wrote:
> Since the client name isn't
> authenticated at all, suid == cuid.

I see.  tickauthreply() in auth/authsrv.c has the following lines:

	safecpy(t.cuid, tr->uid, sizeof t.cuid);
	safecpy(t.suid, tr->uid, sizeof t.suid);

Thanks.
--