diff options
| author |  un1versal | 2015-10-08 13:10:17 +0100 |
|---|---|---|
| committer | un1versal | 2015-10-08 17:39:57 +0100 |
| commit | 02bf7911f3afe6e5960349e5e61329afb3a995a9 (patch) | |
| tree | f2ba9133be0a95091e85cbbb8d75e485e8f59aa5 /src/kvilib/ext/KviCryptEngine.cpp | |
| parent | [ci skip] various header files, typos corrections (diff) | |
| download | KVIrc-02bf7911f3afe6e5960349e5e61329afb3a995a9.tar.gz KVIrc-02bf7911f3afe6e5960349e5e61329afb3a995a9.tar.bz2 KVIrc-02bf7911f3afe6e5960349e5e61329afb3a995a9.zip | |
[ci skip] no strings - cpp files - typo corrections
Diffstat (limited to 'src/kvilib/ext/KviCryptEngine.cpp')
| -rw-r--r-- | src/kvilib/ext/KviCryptEngine.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/kvilib/ext/KviCryptEngine.cpp b/src/kvilib/ext/KviCryptEngine.cpp index b52b6565c..6ec745cbd 100644 --- a/src/kvilib/ext/KviCryptEngine.cpp +++ b/src/kvilib/ext/KviCryptEngine.cpp @@ -129,7 +129,7 @@ Well, there is no protocol actually, only the existing implementations, that can be accessed by anyone that want to reproduce them. There are only some points relating to the crypting engines that need to be cleared:[br] - The crypted text must be suitable to be sent thru an IRC connection; + The crypted text must be suitable to be sent through an IRC connection; this means that some characters can not appear in the crypted text (e.g. CR,LF,NULL....). KVIrc solves it in a simple way: the crypted binary data is encoded, either as hexadecimal numeric string or in base64.[br] |