Daiki Ueno commented: 
https://gitlab.com/gnutls/gnutls/-/merge_requests/1842#note_1986864313


I think this is in the reviewable state, though the support is intentionally 
"hidden" from the production use:

- liboqs support is off by default
- When liboqs is enabled, it is dynamically loaded through dlopen
- When liboqs is enabled, any usage of lower-level cryptography in liboqs is 
replaced with GnuTLS based implementation
- The algorithm identifiers are prefixed with "_EXP_", e.g., 
GNUTLS_PK_EXP_KYBER768 and GNUTLS_GROUP_EXP_X25519_KYBER768, and assigned a 
vendor specific codepoint outside the normal range, e.g., 0 .. 
GNUTLS_{PK,GROUP}_MAX

-- 
Reply to this email directly or view it on GitLab: 
https://gitlab.com/gnutls/gnutls/-/merge_requests/1842#note_1986864313
You're receiving this email because of your account on gitlab.com.


_______________________________________________
Gnutls-devel mailing list
[email protected]
http://lists.gnupg.org/mailman/listinfo/gnutls-devel
  • Re: [gnutl... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities

Reply via email to