ngtcp2 1.25.0 rpms released

ngtcp2 1.25.0 rpms released and added to all supported platforms.

Major changes:

— Fix build error with gcc-16 by @tatsuhiro-t — build(deps): bump actions/cache from 5 to 6 by @dependabotbot — ksl: Align keys in 8 bytes boundary by @tatsuhiro-t — bbr: Update longterm variable computation by @tatsuhiro-t — Remove condition that is always true by @tatsuhiro-t — Verify the end offset of STREAM frame before updating flow control by @tatsuhiro-t — Rework connection flow window accounting after sending STOP_SENDING by @tatsuhiro-t — Stop buffering data after shutting downstream read by @tatsuhiro-t in — Cleanup by @tatsuhiro-t — Update bbr by @tatsuhiro-t — Update doc by @tatsuhiro-t — Add ngtcp2_stream_close2 callback by @tatsuhiro-t — examples: Adopt ngtcp2_stream_close2 callback by @tatsuhiro-t — Tweak stream_close2 callback behavior by @tatsuhiro-t — Expand NGTCP2_MAX_INITIAL_CRYPTO_OFFSET to 64K by @tatsuhiro-t — Partially revert #2242 by @tatsuhiro-t — Make max CRYPTO offsets configurable by @tatsuhiro-t — Minor cleanup by @tatsuhiro-t — Optimize rob by @tatsuhiro-t — build(deps): bump actions/setup-python from 6 to 7 by @dependabotbot — Optimize acktr by @tatsuhiro-t — Remove ngtcp2_acktr_entry and squeeze len into key by @tatsuhiro-t — Minor fixups by @tatsuhiro-t — Amend ba2e5f0142863a0a539671e0194de6019008ad3e (part of #2255) by @tatsuhiro-t — Deal with the case where client migrate back to the original path by @tatsuhiro-t — crypto/quictls: Rework the global initialization by @tatsuhiro-t — ksl: Remove unnecessary NULL initialization by @tatsuhiro-t — Document about C11 compilers by @tatsuhiro-t — Bump boringssl by @tatsuhiro-t — Bump aws-lc to v5.4.0 by @tatsuhiro-t — Bump picotls by @tatsuhiro-t — fuzz: Fuzz more parameters like CID, AEAD tag, and transport parameters by @tatsuhiro-t — Revert «Make max CRYPTO offsets configurable» by @tatsuhiro-t — Require nghttp3 >= 1.18.0 by @tatsuhiro-t

ngtcp2 libraries stack built with OpenSSL 4.0.1. QUIC client name is osslclient.

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *