New SimpleCrypt page

andre

Thanks for your effort, I really appreciate it. If you want, you're welcome to update it yourself in the wiki article :-)

giesbert

Hi Andre,

one suggestion to the wiki page:
In the section SimpleCrypt in use it would be nice to have a list of the encryp/decrypt functions. You state thete are two times 4, but not the names :-)
this means searching inside the code :-)

The rest sound really god. Thanks for the article.

andre

[quote author="Gerolf" date="1300958192"]Hi Andre,

one suggestion to the wiki page:
In the section SimpleCrypt in use it would be nice to have a list of the encryp/decrypt functions. You state thete are two times 4, but not the names :-)
this means searching inside the code :-)

The rest sound really god. Thanks for the article.[/quote]

Fair enough, done. :-)

Thanks for the praise.

giesbert

Hi Andre,

I'm currently reading your second article, and found the following "here":http://developer.qt.nokia.com/wiki/SimpleCrypt_algorithm_details#00f4e5788aab6d3546bb433842dbbefc :

bq. The payload data block’s contents are encrypted with a four byte (quint64) key.

quint64 is a 64 bit integer, which means 8 byte.

so also in the snipet page, you say:

@
SimpleCrypt crypto(Q_UINT64_C(0x7F29B208)); //some random number
@

this is just a 32 bit number, not 64 bit.

@
void SimpleCrypt::splitKey()
{
m_keyParts.clear();
m_keyParts.resize(4);
for (int i=0;i<4;i++) {
quint64 part = m_key;
for (int j=i; j>0; j--)
part = part >> 8;
part = part & 0xff;
m_keyParts[i] = static_cast<char>(part);
}
}
@

this also only uses 4 bytes, not 8.

giesbert

some additional topics:

in "Decrypted payload":http://developer.qt.nokia.com/wiki/SimpleCrypt_algorithm_details#2d478ba9ee3cf03e338b506b1a0292dc

SH1 and CRC have the same description:

bq. In case the Protection Checksum flag has been set, the layout of the decrypted payload looks like this:

I think this is just a copy paste error.

As I'm through now, no more things :-)
Very good article, interesting to read. Thanks.

andre

Thank you very much for this catch, Gerolf! You are absolutely right, and this is a big mistake in the algorithm as well. I will take care of fixing this ASAP.

andre

OK, fixed on both pages. Very embarrassing, I must say. :(

giesbert

Now it looks good, thanks :-)

luca

I tried today SimpleCrypt class and it was very useful.

Thanks!

andre

Glad you like it!

cincirin

Hi Andre.
First of all, thanks for sharing your code. :-)

I was playing with this algorithm, but I noticed a strange situation: sometimes these work well, sometimes not.

This is the string which I have tested :
10197016915918185882701231384169178913312058269-10750535699546572956586080750006397
The key is: 13775729

I tested both with string and binary data (there are several integer values).

So if I encrypt this string, and then decrypt it, sometimes original string is equal with decrypted string, sometimes differ.

andre

You'll have to provide a small testprogram that shows the problem, otherwise I can not help you debug the issue.

cincirin

A small test is something like :

@
QString cryptSerialNumber;

void testCrypt()
{
SimpleCrypt processSimpleCrypt(13775729);
QString uniqueString("10197016915918185882701231384169178913312058269-10750535699546572956586080750006397");
cryptSerialNumber = processSimpleCrypt.encryptToString(uniqueString);
}

void testDecrypt()
{
SimpleCrypt processSimpleCrypt(13775729);
QString uniqueString = processSimpleCrypt.decryptToString(cryptSerialNumber);
}
@

Sometimes decrypted "uniqueString" is the same as the original, but sometimes is :
1019701691591818588270123138416917891691033658269-10750535699546572956586080750006397, almost the same with original, but not the same :-)

andre

Strange. Very, very strange. In such cases, are the cryptSerialNumber the same, or do they differ as well?

cincirin

After encrypt step, I write "cryptSerialNumber" into file.
In decrypt step, I read it from file.

I assume it is the same, the file remain unchanged. I'll do more debug to tell you if "cryptSerialNumber" is the same ...

cincirin

Yes, the “cryptSerialNumber” is the same:
AwNgsVZWVlYFfdbw6is6+srGtTZtFxBm1rc5z8/z1lQNfU74jOk+0bsNs2vMFNlbB5RqAZI/dgJEH79ElSotizgvmf0/xg==

Yes, is very strange ...

andre

Well, at least, that narrows down the issue to the decrypting routine... Issue is: there is nothing in there that I can think of might be influenced by something else than the input string itself. I will have to investigate, but I can not do that right now. I'll need a few days before I get around to doing that. Sorry. I would like to encourage you to try to debug it on your own as well. At the very least, insert some debug statements at strategic places in the code to see what goes on.

Hmmmm... now that I think about it: it is actually very strange that your encrypted string stays the same. It should be different each time you do the encryption, even on the same input string. That is because a random byte is inserted at the front of the byte array to encrypt (line 115 and 116 from simplecrypt.cpp).

cincirin

[quote author="Andre" date="1315913144"]Hmmmm... now that I think about it: it is actually very strange that your encrypted string stays the same. It should be different each time you do the encryption, even on the same input string.[/quote]

You are right. But I do the encryption only once. This encryption string I'll write into file only once.
Then I try to decrypt it several times. And ... sometimes decrypt string = original string, sometimes is very little different.

[quote author="Andre" date="1315913144"]I will have to investigate, but I can not do that right now. I'll need a few days before I get around to doing that. Sorry.[/quote]
Thanks for your time, it is not rush. Now I'm very busy with another project, but if I have more time, I'll debug longer ...

andre

Hi

I have tried to reproduce the problem using this code:
@

#include <QtCore/QCoreApplication>
#include "simplecrypt.h"
#include <QtDebug>

bool testDecrypt()
{
const QString cryptString("AwNgsVZWVlYFfdbw6is6+srGtTZtFxBm1rc5z8/z1lQNfU74jOk+0bsNs2vMFNlbB5RqAZI/dgJEH79ElSotizgvmf0/xg==");
const QString expectedResult("10197016915918185882701231384169178913312058269-10750535699546572956586080750006397");

SimpleCrypt crypt(13775729);
QString result = crypt.decryptToString(cryptString);
if (result == expectedResult)
    return true;

qDebug() << "Fail: " << result;
return false;

}

int main(int argc, char *argv[])
{
QCoreApplication a(argc, argv);

int pass(0), fail(0);
for (int i(0); i<1000000; ++i) {
    if (testDecrypt()) {
        ++pass;
    } else {
        ++fail;
    }
}
qDebug() << "Decryption passed" << pass << "times and failed" << fail << "times.";

return 0;
//return a.exec&#40;&#41;;

}
@

My output was:
@
Decryption passed 1000000 times and failed 0 times.
@

That is: I am not able to see any instability in the algorithm, at least not via this test. That makes it hard for me to figure out why you might be seeing a problem.

qxorm

Hi,

I read your article and it is very interesting !

I am the developer of QxOrm library (Object Relational Mapping for C++/Qt) and I would like to use your class to encrypt/decrypt some datas. Indeed, QxOrm library provides QxService module to create C++/Qt application server. Here is a tutorial if you want to see QxService module : http://www.qxorm.com/qxorm_en/tutorial_2.html

So it would be great with an option to encrypt data before transfering it over network.

Can I use your class in QxOrm library ?
Can I add namespace for your class ?
Can I rename your class to add Qx prefix ?
I will not change anything else.

Thanks !

PS: I´m french so sorry if my english is not perfect.