View Full Version : Plimus & Armadillo & Key Gen Problem...
12-11-2007, 11:46 AM
Hey everyone, I'm using Plimus and Armadillo to generate keys for users. The system works pretty well, except that about 20% of the keys I generate with Plimus don't work. I had a chat with them about this, and they think that the problem is because of Unicode. They tell me I need to use UTF-8.
Does anyone know what this means exactly? I don't see a UTF-8 setting in either SoftwarePassport or on the Plimus site. Is this something I need to set up on my website? Has someone else had this problem and fixed it?
12-11-2007, 07:08 PM
I don't know about SoftwarePassport, but UTF-8 is a way to encode characters.
Probably you are getting, coping, passing or doing some process with the name/string in other charset encoding.
Most of the names use only the ASCII charset, and the ASCII charset is included in the UTF-8. So probably most English names work for you, but when someone introduces an special char it doesn't.
PHP is compatible with UTF-8, MySQL databases also can be set to work with UTF-8, but I'm not sure about how post commands and other stuff work.
Take a look at:
http://www.joelonsoftware.com/articles/Unicode.html <- This is obligatory!
And finally what's happened to me:
I solved the problem using the email only to generate the serial since it's always ASCII, min 7 bytes length, and unique.
12-12-2007, 12:35 AM
> Does anyone know what this means exactly?
Did you ask plimus support? They can probably quickly guide you to some ressources about it.
12-14-2007, 01:58 AM
I assume the keys that don't work via plimus work if you build them yourself ? I use plimus with keys but I don't use armadillo, so, my guess is, if it's the user name causing the hickups and depending on how you send your data to plimus, if using a http style link, it may be going belly up if you're passing it as unicode, if you allow unicode for usernames that is, but without more info it's kinda hard to tell.
12-16-2007, 01:21 AM
I think Plimus guided you to the correct issue when pointing to UTF8. When your user enters their order details over the web, Plimus takes it and stores it in UTF8 format. This same info is pushed into Armadillo to generate a key. Armadillo itself is not aware of any character encoding method, and merely reading a stream of bytes. In the Plimus case, Armadillo is fed with a UTF8 stream of bytes. Now when you go and decrypt the key at your end, you get the user info again, in UTF8 encoding. My guess is that your software tries to read it as ASCII, ANSI (or any other encoding other then UTF8) and fails. Luckily, UTF8 and ASCII are identical when it comes to English characters, but will fails with non-English characters (I'm not sure about Latin though).
Hope this helps...
Powered by vBulletin® Version 4.2.1 Copyright © 2015 vBulletin Solutions, Inc. All rights reserved.