Thank you again.
I am looking into this. So, as I understand, oclhashcat-plus is not BOM aware. I believe it could be made? For instance, if you encounter the bytes (EF BB FF) in the stream then ignore them and read the remaining, which would be your UTF-8 Encoded String.
Though Unicode itself suggests not to use BOM, so I guess it depends on the type of File Editor I have used for the dictionary.
@M@LIK: What file editor did you use for creating this dictionary? I used Notepad and saved it as UTF-8 Encoding, but I guess it prefixes all the strings with BOM due to which oclhashcat-plus does not work with it.
I could make your dictionary not work once again by just copying a BOM UTF-8 String to your dictionary.
For instance:
Without BOM,
It works.
Now, open it with notepad, copy 2 more words which have BOM and append them to above dictionary. It does not work then.
Also, is this documented somewhere that oclhashcat-plus expects the unicode strings to be without BOM or was it your own observation?
I am looking into this. So, as I understand, oclhashcat-plus is not BOM aware. I believe it could be made? For instance, if you encounter the bytes (EF BB FF) in the stream then ignore them and read the remaining, which would be your UTF-8 Encoded String.
Though Unicode itself suggests not to use BOM, so I guess it depends on the type of File Editor I have used for the dictionary.
@M@LIK: What file editor did you use for creating this dictionary? I used Notepad and saved it as UTF-8 Encoding, but I guess it prefixes all the strings with BOM due to which oclhashcat-plus does not work with it.
I could make your dictionary not work once again by just copying a BOM UTF-8 String to your dictionary.
For instance:
Without BOM,
Code:
ьфдщнIt works.
Now, open it with notepad, copy 2 more words which have BOM and append them to above dictionary. It does not work then.
Also, is this documented somewhere that oclhashcat-plus expects the unicode strings to be without BOM or was it your own observation?