NetBSD 10.0 Beta Available(blog.netbsd.org)
blog.netbsd.org
NetBSD 10.0 Beta Available
http://blog.netbsd.org/tnf/entry/netbsd_10_0_beta_available
2 comments
> Among the features you can expect to find in NetBSD 10 are reworked cryptography, including compatibility with WireGuardⓇ, automatic swap encryption, new disk encryption methods, and CPU acceleration in the kernel
> more ARM hardware (including Rockchip RK356X, NXP i.MX 8M, Amlogic G12¸ Apple M1, and Raspberry Pi 4)
Awesome! I've read that there are potential issues with NetBSD's WireGuard implementation. Hopefully that gets sorted out soon. And great to see further advancement in ARM. Asahi Linux deserves a lot of praise for doing the gnarly initial work on M1, which also helped OpenBSD to get support for M1 and M2.
BTW, anyone recognize the funky comma after "Amlogic G12" - what's that?
> more ARM hardware (including Rockchip RK356X, NXP i.MX 8M, Amlogic G12¸ Apple M1, and Raspberry Pi 4)
Awesome! I've read that there are potential issues with NetBSD's WireGuard implementation. Hopefully that gets sorted out soon. And great to see further advancement in ARM. Asahi Linux deserves a lot of praise for doing the gnarly initial work on M1, which also helped OpenBSD to get support for M1 and M2.
BTW, anyone recognize the funky comma after "Amlogic G12" - what's that?
> Awesome! I've read that there are potential issues with NetBSD's WireGuard implementation.
I think you may be thinking of the implementation FreeBSD had (which have now been fixed) unless I have missed some news
I think you may be thinking of the implementation FreeBSD had (which have now been fixed) unless I have missed some news
Parent may be referencing this from August 2020:
https://mail-index.netbsd.org/tech-net/2020/08/22/msg007842....
https://mail-index.netbsd.org/tech-net/2020/08/22/msg007842....
> BTW, anyone recognize the funky comma after "Amlogic G12" - what's that?
It seems to be a cedilla, which is generally placed under the letter "c" like so "ç".
https://unicode-table.com/en/00B8/
It seems to be a cedilla, which is generally placed under the letter "c" like so "ç".
https://unicode-table.com/en/00B8/
The author of the post probably accidentally hit the Compose key before comma by mistake. Compose comma comma produces that character.
https://en.wikipedia.org/wiki/Compose_key
A very NetBSD mistake.
https://en.wikipedia.org/wiki/Compose_key
A very NetBSD mistake.
There's no issue with the WireGuard® implementation aside from the fact that the author of WireGuard®, Jason Donenfeld, didn't like that it wasn't a straight port of his code, but was instead a new implementation based on the WireGuard® protocol paper.
He never articulated any reasons about what might be wrong with it aside from vague handwaving. The implementation actually works well.
He never articulated any reasons about what might be wrong with it aside from vague handwaving. The implementation actually works well.