Skip to content

[PATCH v2] api: crypto: add ZUC 256 algorithm#2335

Open
nkaithakadan wants to merge 1 commit intoOpenDataPlane:masterfrom
nkaithakadan:zuc_v2_spec
Open

[PATCH v2] api: crypto: add ZUC 256 algorithm#2335
nkaithakadan wants to merge 1 commit intoOpenDataPlane:masterfrom
nkaithakadan:zuc_v2_spec

Conversation

@nkaithakadan
Copy link
Copy Markdown
Contributor

Add ZUC256 cipher and integrity algorithm.

@odpbuild odpbuild changed the title api: crypto: add ZUC 256 algorithm [PATCH v1] api: crypto: add ZUC 256 algorithm Apr 10, 2026
Add ZUC256 cipher and integrity algorithm.

Signed-off-by: Nithinsen Kaithakadan <nkaithakadan@marvell.com>
@odpbuild odpbuild changed the title [PATCH v1] api: crypto: add ZUC 256 algorithm [PATCH v2] api: crypto: add ZUC 256 algorithm Apr 13, 2026
@nkaithakadan
Copy link
Copy Markdown
Contributor Author

@JannePeltonen Could you review these changes

@MatiasElo MatiasElo added this to the v1.5X.X milestone Apr 14, 2026
* https://eprint.iacr.org/2021/1439
*/
ODP_CIPHER_ALG_ZUC_EEA3,
ODP_CIPHER_ALG_ZUC_NEA6,
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is not really adding a new algorithm in the API as the commit message says but just moves the currently defined 256-bit ZUC variant with 16-byte-IV from ODP_CIPHER_ALG_ZUC_EEA3 to ODP_CIPHER_ALG_ZUC_NEA6.

But, AFAIK, the algorithm defined in the referenced document is not exactly the same as NEA6 (unless things have recently changed), so adding a new algorithm name is fine, but it should not reference that document.

If we are adding ..._NEA6 and ..._NIA6 then maybe ..._NCA6 should be added too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants