Yes, this is the auto-key variant of vigenere cipher, and is a lot stronger than the basic one.

Interesting stuff. Perhaps I should try to make a new version (still: keeping it simple!) that is a bit stronger.

If you do, I’d be tempted to use something like RC4 which while not perfect, is very simple to implement.

Andre I think you did a great job, at documenting not only usage but also the algorithm. I wish all of Qt’s examples were so well thought out ;)

Great job, easy to use. One question, I tested my app on Debian and Mint and no problem, but on Fedora 17 and Arch
I get “Invalid version or not a cyphertext.”

Sorry, no idea. I did not test on these sytems, but I have no clue why it would go wrong on a different linux system. That seems unlikely somehow. Perhaps the data you feed into SimpleCrypt is corrupted somehow?

Yes, sorry something else went wrong on those systems and indeed corrupted the settings string.
My Bad.

SimpleCrypt works perfectly.

Hi,

Andre wrote:

I have just added a page [developer.qt.nokia.com] in the Snippets category

Thanks for this class. I am invoking it’s constructor with my predefined key (my secret) and I am wondering why qsrand() is initialized with currentTimeMillis or similar (in the constructor code)? I don’t get the same encryption results on multiple invocations so I used my quint64 key to initialize qsrand (in the constructor), then it works..

Output

Just wondering :)

Why would you want to have the same cypher text when using the same clear text and key? As long as the decrypted plain text from these cypher texts is the same, what is the problem with having different cypher texts? The algorithm uses a randomization of the string on purpose. It makes it much harder to leak part of the key because analysis is much harder this way.

An explanation is in the details page that has more on the idea of using a random number as a leading byte.

You replacing that they way you did partly negates this, and thus makes the cypher weaker by a couple of bits. Note that even with your change, encrypting the same plain text using the same SimpleCrypt instance twice will result in different cypher texts.

Hi Andre,

Thanks for answering; I wasn’t looking for reasonably strong encryption – I just wanted to always get the same encrypted string for the same input (private key+string_to_be_encrypted); its just for private use anyway, and non-critical.

I am using QCryptographicHash for that now, it solves my problem

Eh, no, that class does not solve your problem, if you are indeed looking for encryption rather than hashing. There is a big difference between the two…

Andre wrote:

Eh, no, that class does not solve your problem, if you are indeed looking for encryption rather than hashing. There is a big difference between the two…

That’s a chicken and egg problem: I don’t want to elaborate on “my problem” and hence prove that I am fine with hashing because of concerns of privacy. Please understand that and thank you for your help.

worked in QT 5?

good thing I changed was this:

there will be well done this.

I was getting SIGABRT’s when attempting to decrypt an empty string with a Qt with debugging enabled. So I’ve added a little check. Doesn’t seem possible to link to wiki history diffs, but you can see it there.