Eugene Kabanov

I'm closing this issue, because this is not right place for advertising of your own projects. @hed0n1st @MatthewScholefield this issue could be reopened if author will remove ads from this...

``` sha3_(bits) -> SHA3_(bits) sha2_(bits) -> SHA2_(bits) keccak(bits) -> KECCAK(bits) shake(bits) -> SHAKE(bits) ripemd(bits) -> RIPEMD(bits) blake2_(bits) -> BLAKE2(bits) rijndael(bits) -> RIJNDAEL(bits) aes(bits) -> AES(bits) twofish(bits) -> TWOFISH(bits) blowfish(bits) ->...

@gogolxdong you can't reuse one `CBC[aes128]` context for encryption and decryption at the same time, because this context is changing all the time you call `encrypt` and `decrypt`. So for...

@gogolxdong could you please show original message you are trying to decrypt in hexadecimal format. Because here i can only see that you are trying to decrypt/encrypt strings not actual...

@gogolxdong your `key` and `iv` must be at least 16 bytes (octets) long. Your message length must be aligned to 16 bytes too.

AES encoding processing data via blocks of 128 bits (16 bytes). So you can't actually encode/decode safely 1 byte sequence or 15 bytes sequence, you need to have at least...

@gogolxdong there no padding schemes in `nimcrypto` yet, currently its just a library of primitives and operations. So you need to pad it by yourself.

@dryajov sorry but its not an `enhancement`, its missing feature which leads to leaks.

It is missed only because was recently introduced, like 7 months ago, while `peer.nim` implementation was published 9 months ago. Even `libp2p-key` value is not in our `multicodec` database because...

@sinkingsugar we do not need optimized C library, because we already has one - `nim-bearssl`. Also i'm not sure what you mean under word `refactor`, because `ed25519` is constant-time implementation...