From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: [ANNOUNCE] wireguard-freebsd snapshot v0.0.20210428 is available
Date: Wed, 28 Apr 2021 21:51:20 -0400 [thread overview]
Message-ID: <8ee8d72b775ac0f2@lists.zx2c4.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
An experimental snapshot, v0.0.20210428, of WireGuard for FreeBSD has been
been tagged in the git repository.
At this time this code is new, unvetted, possibly buggy, and should be
considered "experimental". It might contain security issues. We gladly
welcome your testing and bug reports, but do keep in mind that this code
is new, so some caution should be exercised at the moment for using it
in mission critical environments.
== Changes ==
* wg_noise: compile on 32-bit
* if_wg: do not increment error counter when sc is null
* if_wg: handle if_transmit and if_output properly
* if_wg: do not assume that IP header is pulled up
* wg_noise: fix remote refcount leak
* if_wg: unify xmit error path
* if_wg: pull up packet before checking aip on input
* netns: enable debug logging
* if_wg: simplify state setting flow
* if_wg: use proper bool for is_retry
* if_wg: do not block for memory when sending buffer
* if_wg: write data header directly
* if_wg: enter net epoch for isr dispatch
* if_wg: do not double-free after m_pullup
* if_wg: allocate entire mbuf all at once
After the rather intense set of commits in the last snapshot, this new
snapshot has been entirely bug fixes and cleanups, addressing regressions
in the last snapshot and simplifying other things. It should be much more
stable than last week.
This snapshot contains commits from: Jason A. Donenfeld and Matt Dunwoodie.
The source repository is available at the usual location:
git clone https://git.zx2c4.com/wireguard-freebsd
This snapshot is available in compressed tarball form:
https://git.zx2c4.com/wireguard-freebsd/snapshot/wireguard-freebsd-0.0.20210428.tar.xz
SHA2-256: cceebd8f3f21d522342b3629fa0350e4fbc64a00035d330f82301741e56def46
Thank you,
Jason Donenfeld
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAmCKEQIQHGphc29uQHp4
MmM0LmNvbQAKCRBJ/HASpd4DrhlkD/9p/xcF9I5i60Qmv6zLSL+Sd88OHx9LXybv
RiLmLjIlKOYq7b5msI7Gxf7UQnHCMiu+UuC8d8ZtsW1SpaPXRx/PFAAAAP/J/RfB
Hd8uYD0whosgdzgaxvfZm+p2FPtDssQW6YNnrmkB62sNqZVEZdtWpLQK0W8BSdSa
DBcgTJe30g/bhFYKQm5GGf3FCR5wIGlcPSJG+h0uhYnRqIJxcDCJEQ9doFQLTHn/
nygIYE4itONeJnT8acmH9zQZ/zuzz4RAHXkE7ux9Ld9pyvFue7OViCYZXNUInVgz
uVbRfL90PUbQz4rcRbRoY2fs+4O5A2HOxegKhf4DqQ6ZGqYYdONnvJ1fZsHhp0zh
ldP6uzDsd1fStyoANEyG/IKRDjpNtRPKVPgtlYLoNdStJll8T6DkdKC2mKAqF4Rp
iBvEXMk1CgsXucqUESogUASKGnuIFfVYp684uqXSIYdga3M0Nnj6ESBhj1GIqGaR
eNkV5DCH3y6MVT0BMs+5UX/qHPLMwwjGYEhzZc4+cqZDjbi8fEMc6+B6SeGdb6I+
+Bl1QXJoD/uzV7OMvXrb+oVGeku59XhjxLe8hf+wilC88R4SKnf0FciiTD0/rAdD
4x+oxW1jRgDk45qN1ryI1d2smPqNaAXRFwbQaL5BpWz6tjEeF4dv9VVCrKVqc1dg
eUDt3xFu0A==
=a84y
-----END PGP SIGNATURE-----
reply other threads:[~2021-04-29 1:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ee8d72b775ac0f2@lists.zx2c4.com \
--to=jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).