The camellia cipher currently uses lookup tables instead of a bitsliced/hardware accelerated backend.
I mention hardware acceleration because there are affine isomorphisms between the AES S-Box and the Camellia S-Box, meaning you can utilise AES-NI or AES bitslicing (and their SIMD accelerations) on Camellia through introducing a small affine transformation over GF(2).
See: https://arxiv.org/abs/2411.12360
I'm just noting this down here to get some input whether this kind of solution is something this project is interested in. I have started drafting out some things in code in a fork and would PR it as soon as it's in a ready enough state.
The
camelliacipher currently uses lookup tables instead of a bitsliced/hardware accelerated backend.I mention hardware acceleration because there are affine isomorphisms between the AES S-Box and the Camellia S-Box, meaning you can utilise AES-NI or AES bitslicing (and their SIMD accelerations) on Camellia through introducing a small affine transformation over GF(2).
See: https://arxiv.org/abs/2411.12360
I'm just noting this down here to get some input whether this kind of solution is something this project is interested in. I have started drafting out some things in code in a fork and would PR it as soon as it's in a ready enough state.