WvdS Doku - en:int:l4resvc

API Reference

Anonymous (anonymous@undisclosed.example.com) — 2026-01-29T21:52:34+00:00

API Reference All functions are declared in the header wvds_crypto.h. ---------- Request Builder wvds_build_aes_encrypt_request int wvds_build_aes_encrypt_request( uint8_t* buffer, // [out] Destination buffer size_t* buffer_len, // [in/out] Buffer size / actual length uint32_t key_id, // Key-ID const void* aad, // Additional Authenticated Data size_t aad_len, // AAD length const void* plaintext, // Data to encrypt size_t pt_len …

System Architecture

Anonymous (anonymous@undisclosed.example.com) — 2026-01-29T21:52:10+00:00

System Architecture Two-Daemon Architecture The WvdS Crypto Service consists of two independent daemons on L4Re: L4Re System +---------------------------------------------------------------------+ | | | +------------------+ +------------------+ +--------------+ | | | crypto_service | | est_service | | OEM Gateway | | | | | | | | …

Compliance & Certifications

Anonymous (anonymous@undisclosed.example.com) — 2026-01-29T21:54:38+00:00

Compliance & Certifications The WvdS Crypto Service meets the requirements of the following standards and regulations. ---------- NIS2 (EU Directive) The NIS2 Directive (Network and Information Security 2) has been in effect since January 2023 and must be transposed into national law by October 2024.

Glossary: Post-Quantum Cryptography

Anonymous (anonymous@undisclosed.example.com) — 2026-01-29T21:54:54+00:00

Glossary: Post-Quantum Cryptography Cryptographic Methods ML-KEM (Module-Lattice Key Encapsulation) Standard FIPS 203 Purpose Key exchange Security Post-Quantum secure ML-KEM replaces classical methods like RSA or ECDH for key exchange. It's based on the

Installation: 3-Step OEM Integration

Anonymous (anonymous@undisclosed.example.com) — 2026-01-29T21:53:20+00:00

Installation: 3-Step OEM Integration The WvdS Crypto Service is a ready-to-use black box. You don't need to compile or configure anything. Simply follow these three steps. ---------- Step 1: Include Daemon in L4Re Image Add the Crypto Service to your

Integration: Code Examples

Anonymous (anonymous@undisclosed.example.com) — 2026-01-29T21:53:50+00:00

Integration: Code Examples AES-256-GCM Encryption Encrypt #include "wvds_crypto.h" #include int encrypt_message( const uint8_t* plaintext, size_t pt_len, const char* aad, size_t aad_len, uint8_t* ciphertext, size_t* ct_len, uint8_t nonce[12], uint8_t tag[16] ) { uint8_t request[65536]; size_t request_len = sizeof(request); // 1. Build request int rc = wvds_build_aes_encrypt_request( request, &request_len, 1, //…

Protocol Specification

Anonymous (anonymous@undisclosed.example.com) — 2026-01-29T21:54:14+00:00

Protocol Specification The Request/Response protocol is binary and runs over Shared Memory. ---------- Request Format Offset Size Field Description ----------------------------------------------------------------------- 0 1 Magic 0xC7 (fixed value) 1 1 Version 0x01 (protocol version) 2 1 RequestType Operation (see table) 3 1 Flags Reserved (0x00) 4 4 PayloadLength Payload length…

Security Mechanisms

Anonymous (anonymous@undisclosed.example.com) — 2026-01-29T21:53:02+00:00

Security Mechanisms The WvdS Crypto Service implements several protection mechanisms that are automatically active. You don't need to configure anything. ---------- Rate Limiting Protects against Denial-of-Service (DoS) attacks through overload.

L4Re Crypto Service

Anonymous (anonymous@undisclosed.example.com) — 2026-01-29T21:51:46+00:00

L4Re Crypto Service Post-Quantum Secure Cryptography for Edge Devices on L4Re Microkernel Version 0.2.0 | OpenSSL 3.6 FIPS Provider | ML-KEM + ML-DSA + AES-256-GCM Big Picture: Double-Layer Security DOUBLE-LAYER SECURITY ==================================================================================== +------------+ +-------------------+ +-----------------------+ | DEVICE | | PQ-EDGE-GATEWAY | | PQ-PROXY | | …