You should probably try to detect this at runtime. At compile time you can simply check if SEC_OID_CURVE25519 exists and fail (or do something else) if it doesn't.
At runtime you could try using SEC_OID_CURVE25519 (with your own define to 355) and have a fallback if NSS gives you an error on using it. On Wed, Feb 7, 2018 at 4:30 PM, Paul Wouters <p...@cypherpunks.ca> wrote: > On Wed, 7 Feb 2018, Andrew Cagney wrote: > > I'd like to use SEC_OID_CURVE25519 but I noticed older NSS versions >> don't have it. >> >> What is the correct way to check for things like this at build time? >> > > But you'd want to check runtime, because someone might update the nss > install to one that does support it. > > Paul > > -- > dev-tech-crypto mailing list > dev-tech-crypto@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-tech-crypto > -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
