2010-01-19, 04:35 AM
MysticHLE Wrote:I think he means only 1 single special character is needed along with the minimum requirement length.
There is one thing I'm skeptical though about this method...and that's how the server translates/encodes and stores these special characters. It's quite possible that these special characters that we're entering ends up getting turned into arbitrary regular characters upon storage. I'm not sure what kind of input templates Nexon server accepts/stores with...but take URL character codes for example...a %20 actually denotes a regular space character. So it may very well be possible that we enter our password as "©password" but it ends up being stored as "$2Dpassword" or some other sort, which would of course, prevent us from accessing our account from both the game and website since we wouldn't know that © gets turned into $2D upon encoding and storage. And of course at the same time, it might be entirely hashable still.
Just putting this out here for the possibility of this occuring. It may not be as fail-proof as we think - but let's hope it is.
(Disclaimer: I don't really know what I'm talking about.)
Well, that's an issue with character encoding. I doubt that Nexon's site transforms ©password into anything else, since © is in the default "Western" character codepage (ISO-8859-1). For one thing, posting to Southperry doesn't do anything with it either; it shows up as a literal © in the source code.
However, if passwords don't handle Unicode (which is probably true), then Japanese characters or anything else not on the codepage will be turned into a sequence of other symbols, probably something like ÆÕ¼. Chances are, though, that this still produces an unusable password.
And in any case, entering in the same password with the same special characters and the same codepage in use should convert to the same other symbols and be accepted as a password, so if it doesn't, then you're probably safe.