[cvsnt] Unicode bug

[Hiroshi Kuribara]

Hi,

Tony has tested, and didn't see problem.
It seems that in his environment or in most of yours
this doesn't occur.

But, I'm watching cvsnt is doing wrong in step by step debugging mode.

Reliability of data is the most important thing
than the security or usability.

Everyone who use cvsnt as server should check this for your office.
Even bytes binary data that start with 0xff 0xfe might be affected.

Aside from binary problem, I found many bugs in -ku mode.
So I forbid -ku option in my office.

/Hiroshi


I add the comment for below.
* I tested with WinXP, Win2K.
* Protocol for client/server is pserver.

My last mail --->
> I checked again with cvsnt2.0.13 and cvs1.11.1p1.
> 
> cvs1.11.1p1 server  +  cvsnt2.0.13 client : OK
> cvsnt2.0.13 server  +  cvsnt2.0.13 client : NG
> cvsnt2.0.13 :local:                       : NG
> 
> My procedure is follow.
> 
> 1. Prepare Unicode file. Name is 'VideoSetup.txt'. (Real
> our file)
> 
> --- file contents is below ---
> [VideoControl Class]
> 0
> 4F800F8
> 0
> 0
> 0,0,608,384
> 16,46,608,384
> 4
> 0
> 4
> 0,191
> 1,95
> 2,0
> 3,107
> 255,255
> 1
> --- file end -----------------
> 
> Binary is
> 0000_0000  FF FE 5B 00 56 00 69 00 64 00 65 00 6F 00 43 00 ..[.V.i.d.e.o.C.
> 0000_0010  6F 00 6E 00 74 00 72 00 6F 00 6C 00 20 00 43 00 o.n.t.r.o.l. .C.
> 0000_0020  6C 00 61 00 73 00 73 00 5D 00 0D 00 0A 00 30 00 l.a.s.s.].....0.
> .....
> 
> 2. Add as binary
> 
> cvs add -kb VideoSetup.txt
> cvs commit -m aloha VideoSetup.txt
> 
> 3. Edit the VideoSetup.txt. 
>    For example, remove 6th line.
> 
> 4.
> cvs commit -m aloha2 VideoSetup.txt
> 
> 5. Take back first version 1.1
> 
> cvs update -r1.1 VideoSetup.txt
> 
> 
> Then, with cvsnt, if one has luck,
> he can get file, but the file is different from real first
> one.
> if one doesn't have luck, he can't get file.


__________________________________________________
Do You Yahoo!?
Yahoo! BB is Broadband by Yahoo!
http://bb.yahoo.co.jp/