epiphany hybrid kem support issue

[titankraken5-lgtm]

I want to know if epiphany support mlkem768x25519. As i have tried but it falls back x25519. i am running httpd server.

[baentsch]

The last time I checked, it did. But @davidkel is maintaining that code right now so should be able to give a more current answer.

[baentsch]

Out of curiousity I just built the docker image (activating X25519MLKEM768 of course) -- and it works perfectly fine.

[titankraken5-lgtm]

SSLOpenSSLConfCmd Curves X25519MLKEM768 this doesnt work

but

SSLOpenSSLConfCmd Curves X25519MLKEM768:X448:X25519:prime256v1 this works fine falls back to X25519.

[baentsch]

Did you change

oqs-demos/epiphany/Dockerfile

Line 16 in 643ef99

ARG KEM_ALGLIST="mlkem768:p384_mlkem768:x25519"

as documented to include support for X25519MLKEM768 ? When I do everything works fine for X25519MLKEM768,

[titankraken5-lgtm]

thanks @baentsch what i did is

i ran

/opt/openssl/bin/openssl s_server -provider oqsprovider -provider default -accept 4433 -cert /opt/httpd/pki/server.crt -key /opt/httpd/pki/server.key -www -tls1_3 -verify 0 -groups mlkem768:p384_mlkem768:x25519 -trace

then opened epiphany from the logs:

Sent TLS Record
Header:
Version = TLS 1.2 (0x303)
Content Type = Handshake (22)
Length = 122
ServerHello, Length=118
server_version=0x303 (TLS 1.2)
Random:
gmt_unix_time=0x415BE78F
random_bytes (len=28): AA8F8A6A3BC74D12A0A3B201F981EA589896C35370D338828ED1AAA0
session_id (len=32): 336161699F38E2A0E2CD417ECEBCBD4147ED3BEB402A356AF9F9FF90CE266FC5
cipher_suite {0x13, 0x02} TLS_AES_256_GCM_SHA384
compression_method: No Compression (0x00)
extensions, length = 46
extension_type=supported_versions(43), length=2
TLS 1.3 (772)
extension_type=key_share(51), length=36
NamedGroup: ecdh_x25519 (29)
key_exchange: (len=32): B08D39CC7A0FCFD33C0F6E96E44F5C4FDF72E226398C19686A144E1C4302C539

that means ecdh_x25519 is being used and on tls1.2

[baentsch]

/opt/openssl/bin/openssl s_server -provider oqsprovider -provider default -accept 4433 -cert /opt/httpd/pki/server.crt -key /opt/httpd/pki/server.key -www -tls1_3 -verify 0 -groups mlkem768:p384_mlkem768:x25519 -trace

does not activate X25519MLKEM768, so no client could possibly use that group.

fwiw, we have made available https://test.openquantumsafe.org as a "baseline test server" for clients interested in checking out all OQS-supported KEM/SIG alg combinations; please note that standardization and development has moved on since I wrote this server a few years back, so it cannot be seen as a true interoperability server any more -- but it would serve this purpose in this specific case: Connecting epiphany to https://test.openquantumsafe.org:6003/ should yield this result:

Successfully connected using ecdsap256-X25519MLKEM768!
Client-side KEM algorithm(s) indicated: X25519MLKEM768:mlkem768:p384_mlkem768:x25519:secp256r1:secp384r1

(or whichever client-side KEMs you configured)

[davek-at-ibm]

@baentsch Thanks for stepping in and handling this.