spum_xts_tweak_in_payload(9)
π spum_xts_tweak_in_payload(9) π
okay so bestie, this page is from the Kernel API Manual, and itβs here to tell you one very specific thing about SPUM and XTS tweak placement. The vibe? SPUM DOES place the XTS tweak field in the packet payload instead of using IV. no cap. β¨
πΈ NAME πΈ
spum_xts_tweak_in_payload β Indicate that SPUM DOES place the XTS tweak field in the packet payload (rather than using IV). π
π¦ SYNOPSIS π¦
u8 spum_xts_tweak_in_payload (void );
π ARGUMENTS π
voidβ no arguments. literally none. not a single one, bestie. π«Ά
β¨ RETURN β¨
1β the return value is1. thatβs it. thatβs the whole answer. β
π SEE ALSO π
Kernel file: ./drivers/crypto/bcm/spu.c
and now, the SPUM friend group, fr fr:
spum_ns2_ctx_max_payload(9)spum_nsp_ctx_max_payload(9)spum_response_hdr_len(9)spum_hash_pad_len(9)spum_gcm_ccm_pad_len(9)spum_assoc_resp_len(9)spum_aead_ivlen(9)spum_hash_type(9)spum_digest_size(9)spum_create_request(9)spum_cipher_req_init(9)spum_cipher_req_finish(9)spum_request_pad(9)spum_tx_status_len(9)spum_rx_status_len(9)spum_status_process(9)spum_ccm_update_iv(9)spum_wordalign_padlen(9)
mwah π β source/version: ./drivers/crypto/bcm, date: October 2026. this page is literally spum_xts_tweak_in_payload(9) and it ate. π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms