[473] in Kerberos

home help back first fref pref prev next nref lref last post

Re: valid names

daemon@TELECOM.MIT.EDU (jb%cs.brown.edu@RELAY.CS.NET)
Fri Jul 29 19:55:19 1988

From: jb%cs.brown.edu@RELAY.CS.NET
To: "Jerome H. Saltzer" <Saltzer@ATHENA.MIT.EDU>
Cc: kerberos@ATHENA.MIT.EDU
In-Reply-To: Your message of "Fri, 29 Jul 88 12:49:23 EDT."

I think even limiting the character set to printable ascii is overly
restrictive.  If at all possible, the protocol should be able to
handle any character set using 8-bit bytes.  Anything more restrictive
than forbidding NULL might interfere with users tring to use international
character sets.  (Anyone know how kanji works?)  Most people don't
even consider the international character sets.  It would look good
if we had thought about the issue and tried to be compatible with
the internation character sets.

At the application level, it is reasonable to be more restrictive.
If at all possible, the library routines should accept any null
teminated string of bytes for the principal, instance, and realm
identifiers.  The server should be as general as possible too.

				Jim

home help back first fref pref prev next nref lref last post