[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-cifs
Subject:    Re: CIFS Authentication Protocol Review
From:       "Russ, Craig F" <Craig.Russ () UNISYS ! COM>
Date:       1997-04-09 12:50:19
[Download RAW message or body]


I have a question about 1.3.1 of draft 4 of "CIFS Authentication
Protocols Specification".

What does U(x) do on non ISO LATIN1 based versions of Windows NT and
Windows 95?

Some examples:

*       Does the Japanese version do a ShiftJIS to Unicode translation, or
simply pad every other byte with zero?

*       Does the Russian version translate code page 866 to Unicode or
translate code page 1251 to Unicode or simply pad every other byte with
zero?

Could this be clarified in the specification?

Actually, I guess I have the same question for ISO LATIN1 based
versions.  For example:

*       Does the French version translate code page 850 to Unicode or simply
pad every other byte with zero (which I think is equivalent to translate
ISO LATIN1 to Unicode).

Another issue.  I assume "Unicode" means Unicode stored little-endian.
This should be explicitly stated.

I just thought of another issue. What does "upper cased" mean in 1.3.2.
I hope that the French version upper cases assuming code page 850, the
Russian version upper cases assuming code page 866, the Japanese version
upper cases assuming ShiftJIS, etc.  Is this true?

Craig

>----------
>From:  Paul Leach[SMTP:paulle@MICROSOFT.COM]
>Sent:  Tuesday, March 25, 1997 5:18 PM
>To:    CIFS@LISTSERV.MSN.COM
>Subject:       CIFS Authentication Protocol Review
>
>We are releasing preliminary drafts of the proposed fixes to the
>CIFS/SMB authentication protocols for widespread public review. If they
>pass review, they will be in Service Pack 3 for NT 4.0.
>
>The original protocol from which the new version descends was designed
>more than a decade ago; recently, quite a few weaknesses have been
>found
>in those previous versions. This latest revision is an attempt to
>repair
>those weaknesses with as small a change to the protocol as possible, so
>that it can be incrementally and rapidly deployed.
>
>All three documents are available in .doc, .txt and postscript.
>
>Information on how to get them is available from:
>ftp://ftp.microsoft.com/developr/drg/cifs/sec.htm
>
>All followup discussion should be on the CIFS mailing list at
>CIFS@listserv.msn.com.
>
>Your comments are actively solicited.
>------------------------------
>Paul J. Leach
>paulle@microsoft.com
>

[prev in list] [next in list] [prev in thread] [next in thread]