Christopher Klooz

Security-critical issues solved in https://github.com/hyperledger/iroha-python/pull/58 - still, further testing of the pull request suggested!

xxhash has only 64 bit and is designed for modern 64bit architectures. If xxhash is already default, SHA1 cannot replace it in terms of performance. I have no explicit comparison...

@thestinger just made me aware that arm/aarch64 implement AES differently than x86_64. This is relevant only for arm/aarch64 architectures and does not impact my proposal as far as it concerns...

Sorry, I accidentally closed, my bad -> now reopened.

On x86_64: yes, it remains as it is: e.g., `lscpu | grep aes` -> if no output == AES-NI false / if Flags output == AES-NI true. You just need...

Thank you very much Daniel! In this case, the different implementation of AES does not make a difference in our approach: it remains the `aes` flag on both x86_64 and...

> AArch64 CPUs mostly have the AES acceleration instruction > I'm talking about AArch64, not x86_64. Sorry, I read your original sentence mistakenly as generally applicable to AES-NI and AArch64...

> 64-bit ARM cores (Cortex-A53 and Cortex-A57) I just remembered that during our discussion in the Fedora devel mailing list, another Fedora member has checked [1] the Raspberry PI's 2,...

> not in a cryptographic sensitive way. Agreed. The problem is that users are not aware of that: many people link md5 intuitively with broken crypto, even if it is...

Generally, it were just examples to illustrate the point. I absolutely understand your argument. A realistic compromise would have to be somewhere in between. However, to stick for a moment...