You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Identify Java's core string encoding APIs, and test major Java versions to document:
best-fit mapping behavior - does the API best-fit characters by default?
override options - can default be overridden?
One way to test this might be to brute force a large set of Unicode characters by converting them to a target encoding and seeing if they convert to anything 128-bit ASCII.
// Loop through all available encodingsforeachavailableencoding{// Loop through first 65,535 code points, starting at 0x80 to avoid // using 128-bit ASCII as the source, because we want to test// if ASCII is the outcome!foreachUnicodecharacter0x080to0xffff{converttheUnicodecharacterfromUTF-8orUTF-16tothetargetencoding(e.g.shift_jis,ISO-8859-1,etc)testifthetargetcharacterisASCII0x00to0x80aftertheconversion}}
The text was updated successfully, but these errors were encountered:
See: http://websec.github.io/unicode-security-guide/character-transformations/#best-fit
Identify Java's core string encoding APIs, and test major Java versions to document:
One way to test this might be to brute force a large set of Unicode characters by converting them to a target encoding and seeing if they convert to anything 128-bit ASCII.
The text was updated successfully, but these errors were encountered: