AEGIS-X implementations

[asterized]

Hi, I've noticed that AEGIS-X implementations are on the roadmap, and I'm wondering whether I could port implementations of these from libaegis.

[jedisct1]

They are on the roadmap, but the libsodium APIs are more limited than the one from libaegis (no streaming, no RAF), so the implementations may be a bit different.

See 2ee63911bf710e4ce8863f359b3c29882600e662 from libaegis. That was reverted because it needs a bit of testing/tuning and it makes implementations more complicated with the libaegis features, but it's something we can do more easily in libsodium.

[asterized]

I am aware of the differences between libaegis and libsodium's APIs, although could you explain a bit more about why the commit needs testing/why its easier in libsodium? I presume its harder to evaluate because it relies more on specific CPU behavior in the case of tuning?

[jedisct1]

In libsodium there are only one-shot interfaces where the size is known upfront. No buffering, no user-defined offsets, no partial blocks except the last one.

[asterized]

Ah, that makes sense, thanks!