XOR-encryption is the application of a key through bitwise exclusive OR to the source text. The mechanism of the bitwise exclusive is the following:
X | Y | X⊕Y |
---|---|---|
0 | 0 | 0 |
0 | 1 | 1 |
1 | 0 | 1 |
1 | 1 | 0 |
Thus, when executing an exclusive OR, there will always be a zero value if the variables have the same values.
The peculiarity of XOR is that one and the same function can both encrypt data and decrypt it. This is a simple method of data encryption, which can be hacked quickly enough if there is a large enough encrypted text, or a large password dictionary. But nevertheless, this can already be used for small initial data protection.
In the context of Qt, the use of XOR is no different from how the program was written without using Qt. The question here is how to extract data for encryption from QString objects, for example, if the text was entered in QTextEdit.
To do this, write a program that contains:
- QTextEdit, In which the text will be entered, which will be encrypted.
- QLineEdit, In which the encryption key will be entered.
- QPushButton, In the slot of the click handler of which, data encryption / decryption will be performed. Again, I note that the method will be used the same.
The program will look like this:
Project structure
The project is written using CMake, so the structure will be as follows:
- CMakeLists.txt
- main.cpp
- EncoderWidget.h
- EncoderWidget.cpp
Encryption / decryption function
To implement encryption / decryption it is necessary:
- The presence of a char array with the original data
- Length of the array with the original data
- Key as array char
- Length of key
- And also an array with output data.
const char* input; int inputLength; const char* key; int keyLength; char output[inputLength]; for (int i = 0; i < inputLength + 1; ++i) { output[i] = input[i] ^ key[i % keyLength + 1]; }
Slot handler for encryption
As already mentioned, to encrypt the text, you need to correctly extract data from the input fields. To do this, you need to translate the text in the form of a QString string into a QByteArray from which to extract the data in the form of const char *. And also take the length of this data.
There is one point. This from QString in QByteArray is translated using the toLatin1 () method, which will result in data to the ASCII table, which will lead to data corruption if the text was written in Cyrillic. That is, this approach to encryption will be relevant if only symbols from the ASCII table are used, for example, for the login and password.
void EncoderWidget::encodeDecode() { const char* input = m_textEdit->toPlainText().toLatin1().data(); int inputLength = m_textEdit->toPlainText().toLatin1().length(); const char* key = m_keyLineEdit->text().toLatin1().data(); int keyLength = m_keyLineEdit->text().toLatin1().length(); char output[inputLength]; for (int i = 0; i < inputLength + 1; ++i) { output[i] = input[i] ^ key[i % keyLength + 1]; } m_textEdit->setText(QString::fromLatin1(output, inputLength)); }
Conclusion
The project can be downloaded from the following link
Шифрует/дешифрует текст от 8 символов, так и должно быть?
Не обратил внимания на это, Проверял с большим текстом.. По идее не должно.
Хоть пост и старый, но хочется понять. В случае xor шифрования символов мы может получить специальнвй символ(к примеру \0 или \n)? И, если, к примеру, нам нужно записать в текстовый файл эти данные, то мы при следующем считывании можем получить проблемы с считыванием?
в контексте этой статьи с символом \n, то есть символом новой строки проблем быть не должно, поскольку он точно присутствует в таблице символов ASCII, касательно \0 смотрите в таблице символов ASCII, если есть соответствующий символ.
А так, по идее можно доработать и для юникода и для любой другой кодировки, тогда проблем быть не должно.
Здравствуйте, не очень понимаю, почему в строках
добавляется единица к inputLength и keyLength?