Encryption include compression, AES and shift
Posted: Mon Sep 05, 2011 7:25 amCompression of data reduce 50% of time of data transfer. If using database as server, will get better performance.
AES, Advanced Encryption Standard, common used encryption method. Both client and server should input the same AES key.
Compression + AES, it may not reduce the time and increase the data security. It depends on what server service is used. You can try, if performance is not good, change it to AES only.
Shift Byte, a very simple encoding method, just to shift you data byte value. If the first byte of data is 1 and you input the shift byte by value is 5, the final data byte will become 6.
Why we use shift byte:
. very less cpu usage, data changed will not easily recognized by filter program.
. use this encryption only if you data between client and server is not sensitive.
. We will discuss on how to apply simple shift on application sample.
Client and server sides may not need to select the same Compression or AES or both. If you find data from client is not safe or is plaintext, select AES or compression. Data client always send data out with plaintext. Normally, data transfer from server to client is encrypted by their standard, we will not easily understand. Therefore server side Magic Router do not need to select AES/compression. Be notice, select AES/compression will use up a little bit cpu time.
IF select shift byte, both client and server should input the same value, otherwise decoding will not correct.
SSL3 is a OPENSSL standard. Stunnel module will be loaded at the same time. If you need you own cert. to connect to server side, see stunnel\stunnel.html for more detail.
AES, Advanced Encryption Standard, common used encryption method. Both client and server should input the same AES key.
Compression + AES, it may not reduce the time and increase the data security. It depends on what server service is used. You can try, if performance is not good, change it to AES only.
Shift Byte, a very simple encoding method, just to shift you data byte value. If the first byte of data is 1 and you input the shift byte by value is 5, the final data byte will become 6.
Why we use shift byte:
. very less cpu usage, data changed will not easily recognized by filter program.
. use this encryption only if you data between client and server is not sensitive.
. We will discuss on how to apply simple shift on application sample.
Client and server sides may not need to select the same Compression or AES or both. If you find data from client is not safe or is plaintext, select AES or compression. Data client always send data out with plaintext. Normally, data transfer from server to client is encrypted by their standard, we will not easily understand. Therefore server side Magic Router do not need to select AES/compression. Be notice, select AES/compression will use up a little bit cpu time.
IF select shift byte, both client and server should input the same value, otherwise decoding will not correct.
SSL3 is a OPENSSL standard. Stunnel module will be loaded at the same time. If you need you own cert. to connect to server side, see stunnel\stunnel.html for more detail.