cmeerw

joined 2 years ago
 

Please share your feedback in this annual 10-minute survey to help inform C++ standardization and C++ tool vendors. This is the biggest opportunity we all have each year to make our voices heard and help improve our industry and community!

A summary of the results, including aggregated highlights of common answers in the write-in responses, will be posted publicly here on isocpp.org and shared with the C++ standardization committee participants and C++ tool vendors to help inform C++ evolution and tooling.

The survey closes in one week.

Thank you for participating and helping to inform our committee and community.

 

The NetBSD project is pleased to announce the third (and probably final) release candidate of the upcoming 11.0 release, please help testing!

 

On Saturday, the ISO C++ committee completed technical work on C++26 in (partly) sunny London Croydon, UK. We resolved the remaining international comments on the C++26 draft, and are now producing the final document to be sent out for its international approval ballot (Draft International Standard, or DIS) and final editorial work, to be published in the near future by ISO.

 

Jails for NetBSD aims to bring lightweight, kernel-enforced isolation to NetBSD.

It is designed to fill the operational gap between simple chroot environments and full virtualization systems such as Xen.

 

What looks like a simple nginx config change turns out to involve SSL library compatibility, firewall rules for a new protocol, and a subtle multi-process routing problem that only surfaces under real traffic. This documents what it actually took to get HTTP/3 (QUIC) working on nginx 1.28 inside a FreeBSD 15.0 Bastille jail - serving the Mastodon instance at burningboard.net.

[–] cmeerw@programming.dev 9 points 3 months ago

Somewhat related - who came up with the idea of stuffing all that domain verification tokens directly into TXT records for the domain?

Just querying the TXT record of a domain might give you an idea what products a company is using...

 

11.0 release expected before the end of february 2026

 

Kernel changes

  • x86: PVH boot is now supported on non-XEN platforms (QEMU, Firecracker)
  • various new drivers for temperature (and other environmental) sensors and fan control
  • the heartbeat watchdog will detect locking errors that prevent softints from running or the timecounters from making progress on one of the CPUs
  • On machines with no entropy source timing based entropy estimation allows unblocking of the entropy system (like it used to before NetBSD 10.0)
  • lots of enhancements for Linux emulation
  • new syscall: semtimedop(2)
  • lots of enhancements to the riscv port
  • various bug fixes

Userland changes

  • libm got most (all?) missing long double and transcendental functions
  • userland support for manipulating/querying (U)EFI variables has been added
  • jemalloc has been updated to version 5.3
  • various bug fixes to libpthread and making functions signal safe
  • lots of miscelaneous bug fixes
  • the in-tree X.org components are all (well, nearly - there are a few minor/unimportant exceptions) up-to-date

3rd party software updates included

  • gcc for all architectures is now at version 12.5
  • gdb for all architectures is now at version 15.1
  • binutils for all architectures is now at version 2.42
  • OpenSSL got updated to the latest long term support version available: 3.5.1
  • OpenSSH is at version 10.0
  • many others updated, including dhcpcd, openresolv, unbound, nsd, ...
 

#NetBSD 11.0 has been branched, and the stabilization process now begins. Pre-release snapshots will be available for users to try soon(tm).

This will be the first release with RISC-V, C23, and POSIX 2024 support.

[–] cmeerw@programming.dev 1 points 11 months ago (1 children)

That leaves UCEPROTECTL3

Is anyone still using them?

[–] cmeerw@programming.dev 0 points 1 year ago

see https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p3471r2.html#enabling-hardening

Much like a freestanding implementation, the way to request a hardened implementation is left for the implementation to define. For example, similarly to -ffreestanding, we expect that most toolchains would provide a compiler flag like -fhardened, but other alternatives like a -D_LIBCPP_HARDENING_MODE= macro would also be conforming.

[–] cmeerw@programming.dev 0 points 2 years ago

I am using a single package from Mint, the rest is Ubuntu 23.04. Mint would otherwise be based on Ubuntu 22.04?

view more: next ›