nng, branch wolf-peer-cnA mirror of https://github.com/nanomsg/nng
https://cogarr.net/source/cgit.cgi/nng/atom?h=wolf-peer-cn2025-10-05T14:19:24Zfixes #2158 Implement support for NNG_OPT_TLS_PEER_CN for WolfSSL2025-10-05T14:19:24ZGarrett D'Amoregarrett@damore.org2025-10-05T14:19:24Zurn:sha1:bc2cbfea1ed4a5c6192cc86117dbc6d306b4fdaf
This also provides an implementation for getting ALT names, although
nothing uses that yet. We plan to provide a new certificate API to
replace these with a nicer API, as obtaining the full list of certs
may be unreasonable.
tests: Add test for serving http static binary2025-10-05T00:57:56ZGarrett D'Amoregarrett@damore.org2025-10-05T00:41:06Zurn:sha1:cfcc004cff8f6e11c545070ed0e9ba0253227e44fixes #2165 nng_http_handler_alloc_static crashes if content type is null2025-10-05T00:57:56ZGarrett D'Amoregarrett@damore.org2025-10-05T00:17:59Zurn:sha1:d6eeff578cc8e2ada1a80f4d1ddaa098931f9a7dremaps EAI_AGAIN to NNG_EADDRINVAL (#2169)2025-10-05T00:10:07ZJon Gjengsetjon@thesquareplanet.com2025-10-05T00:10:07Zurn:sha1:37fe4eff0e23ffbc251034b8001a1065c55f9951
When running nng tests in CI under nix on Linux, I would see
`nng_dialer_start` fail with `NNG_EAGAIN` when invoked with `flags = 0`
and a URL of `tcp://999.888.777.666:8080` (this is in a test that is
supposed to check that dialing that gives you `NNG_EINVAL` or
`NNG_EADDRINVAL`).
This can happen if `nni_resolv_ip` in `posix_resolv_gai.c` gets
`EAI_AGAIN` from `getaddrinfo`, which the man pages suggest _can_ happen
due to "a temporary failure in name resolution". In the nix case, this
is due to the nix build sandbox, but it can also arise simply due to DNS
overload or misconfiguration.
In either case, nng should not bubble up `EAI_AGAIN` `as `NNG_EAGAIN`
from `nng_dialer_start`, as `NNG_EAGAIN` has a different semantic
meaning. `NNG_EAGAIN` is more equivalent to "would block", and should
only be generated through calls with the `NONBLOCK` flag. We don't have
a perfect mapping for `EAI_AGAIN`, but the closest is probably
`NNG_ADDRINVAL` to indicate that we failed to resolve the given address
(even if it's temporary). Another option would be to introduce another
error variant like `NNG_ENAMELOOKUP`, but that felt excessive to cover
this case.
dtls: Add a test for "large" (1K) messages2025-09-29T06:40:32ZGarrett D'Amoregarrett@damore.org2025-09-29T05:41:52Zurn:sha1:ef8e535c441f116f653e327cc66c21286a4104ecFix nuts colors to match acutest.2025-09-29T05:34:02ZGarrett D'Amoregarrett@damore.org2025-09-29T05:34:02Zurn:sha1:159ac495db4cb32f40870e19ee8a87ec77fc3482defs: Fix incorrect define of NNI_PUTLEXX macros.2025-09-29T05:21:04ZGarrett D'Amoregarrett@damore.org2025-09-29T05:21:04Zurn:sha1:35ad85188b28bcfd13c4e286eb797df6779281ad
This was responsible for breaking DTLS, and likely other things we
never noticed, if the pointer passed in was not already a uint8_t *.
Fix dtls reconnect attempts.2025-09-15T00:21:00ZGarrett D'Amoregarrett@damore.org2025-09-15T00:21:00Zurn:sha1:f716f61c81a5f120d61b58ee9b4a52b33b2ecb16
Once a DTLS client is started and has reasonably resolved things, it
will restart message connections; this way we can restart after a
failed connection attempt (e.g. if the CERT was bad or something.)
Only log aborted connections at debug.2025-09-15T00:20:14ZGarrett D'Amoregarrett@damore.org2025-09-15T00:20:14Zurn:sha1:d32abc2d5944637372f6ba597575ed17b14b974e
This is occurs normally on socket close and the error messages were alarming.
mbedtls: reduce logging for debug crypto to debug log2025-09-15T00:19:08ZGarrett D'Amoregarrett@damore.org2025-09-15T00:19:08Zurn:sha1:a096df1fc30cc44ab01aa10bd1f72b33fd477b10
Warning level was just too noisy.