Download the PHP package secudoc/php-liboqs without Composer

OQS Wrapper Extension

A minimal PHP extension wrapping liboqs KEM and signature APIs into a namespaced API suitable for the SecuDoc stack. The runtime namespace, configure flag, and module name are OQS (extension: oqs.so).

Note on naming: NIST standardized Kyber as ML-KEM (FIPS 203). liboqs exposes both names (Kyber{512,768,1024} and ML-KEM-{512,768,1024}) depending on build options. This extension accepts whatever your liboqs provides.

Once PHP natively supports PQC, this wrapper will likely be deprecated.

API

KEM

OQS\KEM exposes post-quantum key encapsulation:

• OQS\KEM::algorithms(): string[] — list enabled KEM identifiers.
• OQS\KEM::keypair(string $algorithm): array{publicKey: string, secretKey: string}
• OQS\KEM::keypairDerand(string $algorithm, string $seed): array{publicKey: string, secretKey: string} — deterministic keygen from seed
• OQS\KEM::encapsulate(string $algorithm, string $publicKey): array{ciphertext: string, sharedSecret: string}
• OQS\KEM::encapsulateDerand(string $algorithm, string $publicKey, string $seed): array{ciphertext: string, sharedSecret: string} — deterministic encaps from seed
• OQS\KEM::decapsulate(string $algorithm, string $ciphertext, string $secretKey): string

All algorithm identifiers surfaced by liboqs are also available as class constants, e.g. OQS\KEM::ALG_KYBER768 and/or OQS\KEM::ALG_ML_KEM_768 (depending on your liboqs build).

Binary outputs: All keys, ciphertexts, and shared secrets are raw binary strings. Base64-encode if you need printable or JSON-safe values.

Secret handling: temporary native buffers are wiped with OQS_MEM_cleanse, but returned PHP strings remain managed by the Zend engine and are not guaranteed to be securely erased later. Treat secret keys and shared secrets as sensitive application data.

Signatures

OQS\Signature wraps stateless PQ signatures:

• OQS\Signature::algorithms(): string[]
• OQS\Signature::keypair(string $algorithm): array{publicKey: string, secretKey: string}
• OQS\Signature::keypairDerand(string $algorithm, string $seed): array{publicKey: string, secretKey: string} — deterministic keypair from seed (ML-DSA: 32 bytes)
• OQS\Signature::sign(string $algorithm, string $message, string $secretKey): string
• OQS\Signature::signWithContext(string $algorithm, string $message, string $context, string $secretKey): string — context-bound signing
• OQS\Signature::verify(string $algorithm, string $message, string $signature, string $publicKey): bool
• OQS\Signature::verifyWithContext(string $algorithm, string $message, string $signature, string $context, string $publicKey): bool — context-bound verification

Signature identifiers are also class constants, e.g. OQS\Signature::ALG_DILITHIUM_3.

Global namespace constants (e.g. OQS\VERSION_TEXT) mirror liboqs build info.

Quick start (usage)

Installing liboqs

Before building this PHP extension, you need the liboqs C library and headers installed on your system.
You can either build it from source or install it via a package manager if available.

Build from source (recommended)

This installs liboqs.so to /usr/local/lib and headers to /usr/local/include/oqs.

Verify installation

Then proceed with the build steps below.

Requirements

• PHP dev tools (phpize, php-config, headers)
• liboqs 0.14.0 or newer (headers under include/oqs, libs under lib)
• A compiler toolchain (gcc/clang, make, autoconf)

Check your liboqs version:

Build & install

Using pie (recommended)

Retrieve the pie.phar from https://github.com/php/pie and install the extension as follows:

Make sure you have liboqs already installed.

Build it from scratch using pkg-config

Using an explicit liboqs prefix

If liboqs isn’t in pkg-config, pass the prefix that contains include/oqs and lib/:

Troubleshooting

• liboqs 0.14.0 or newer is required
  Ensure pkg-config finds liboqs ≥ 0.14.0 (pkg-config --modversion liboqs) or your --with-oqs prefix points to headers with oqs/oqsconfig.h reporting ≥ 0.14.0.

• oqs.h not found
  Your --with-oqs=/prefix must contain /prefix/include/oqs/oqs.h and /prefix/lib/liboqs.*.

• Runtime loader can’t find liboqs.so
  Either install liboqs to a standard location (e.g. /usr/local) or set:

• Which algorithms are enabled?

Notes

• Algorithms and sizes are defined by liboqs at build time. If an identifier isn’t present in OQS\KEM::algorithms(), your liboqs was built without it.

• Thread safety: the extension itself is stateless; use a thread-safe PHP build (ZTS) if your SAPI requires it.

Disclaimer

This extension is provided as-is without any warranty. It is intended for experimentation, prototyping, and research purposes only. Do not use this software in production environments that require certified or audited cryptographic implementations. The liboqs library itself is not a FIPS-validated module, and the PHP wrapper has not been security reviewed. Use entirely at your own risk.