Basically, I created a new branch with a "toy" encryption feature. It's out of the way and is accessed using the right click context menu.
My reasoning behind this is that it can be used to obscure the answers to a question (in a puzzle?), it sort of fits in with everything else, and it gives people the ability to do something they might not normally be able to do (encrypt messages.)
It's pretty strange, and I'm not sure whether or not you want to pull these changes in, so please don't feel obligated to do so.
The algorithm used is XXTEA, and the key derivation function is 256 salted iterations of SHA-512. The KDF and encryption algorithm actually provide decent cryptography, but as with any cryptosystem, don't trust it with your valuable information.
I used a 3-clause BSD licensed implementation of the XXTEA encryption algorithm in Python. This license is compatible with the GPL, so there shouldn't be any legal problems with including it. Everything else is from Python standard libraries.
Basically, I created a new branch with a "toy" encryption feature. It's out of the way and is accessed using the right click context menu.
My reasoning behind this is that it can be used to obscure the answers to a question (in a puzzle?), it sort of fits in with everything else, and it gives people the ability to do something they might not normally be able to do (encrypt messages.)
It's pretty strange, and I'm not sure whether or not you want to pull these changes in, so please don't feel obligated to do so.
The algorithm used is XXTEA, and the key derivation function is 256 salted iterations of SHA-512. The KDF and encryption algorithm actually provide decent cryptography, but as with any cryptosystem, don't trust it with your valuable information.
I used a 3-clause BSD licensed implementation of the XXTEA encryption algorithm in Python. This license is compatible with the GPL, so there shouldn't be any legal problems with including it. Everything else is from Python standard libraries.