Changes between Initial Version and Version 4 of Ticket #6308


Ignore:
Timestamp:
Mar 29, 2008, 1:32:03 PM (13 years ago)
Author:
Tom Trenka
Comment:

Understood; I will see what I can do.

BTW, you do realize that MD5 has been brute-forced, right?

Replying to guest:

Replying to ttrenka:

The main issue is that if one gets updated to use double-byte character sets, all must be updated and I'm not entirely sure I want to support that yet.

The issue we encountered was with high order ASCII (above 128). Our backend is all utf8 (MySQL / PHP) and the forms are all utf8 but when the JS layer encodes the high order ascii the UTF8 != UCS2 encoding.

For example "§": ASCII: 0xA7 (167) UCS2: 00A7 UTF8: C2A7

Each of these results in a different MD5 being generated and makes digest comparison quite difficult.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6308

    • Property Owner changed from anonymous to Tom Trenka
    • Property Status changed from new to assigned
    • Property Component changed from General to Dojox
    • Property Milestone changed from to 1.3