Create a personal blog with NetBSD on a 1€ VPS - efficient, secure, and completely under your control. Minimal cost, maximum performance. Because your thoughts don't need to float in someone else's cloud.
I see a lot of spam coming from sendgrid, so I wonder how long they can continue operating that way until they get blocked completely by one of the larger mailbox providers.
How to Secure Existing C and C++ Software without Memory Safety
The most important security benefit of software memory safety is easy to state: for C and C++ software, attackers can exploit most bugs and vulnerabilities to gain full, unfettered control of software behavior, whereas this is not true for most bugs in memory-safe software—just a few
For more background on safety and security issues related to C++, including definitions of “language safety” and “software security” and similar terms, see my March 2024 essay “C++ safety, in conte…
This is a status update on improvements currently in progress for hardening and securing our C++ software.
The slides, the notes, and the text behind my presentation at OSDay 2025 in Florence, Italy - 'Why Choose to Use the BSDs in 2025.
After the Graz, Austria February 2025 WG14 Meeting, I am now confident in the final status of the defer TS, and it is now time.
For the big brain 10,000 meter view, defer ⸺ and the forthcoming TS 25755 ⸺ is a general-purpose block/scope-based “undo” mechanism that allows you to ensure that no matter what happens a set of behavior (statements) are run.
Bjarne Stroustrup wants standards body to respond to memory-safety push as Rust monsters lurk at the door
Bjarne Stroustrup, creator of C++, has issued a call for the C++ community to defend the programming language, which has been shunned by cybersecurity agencies and technical experts in recent years for its memory safety shortcomings.
Emacs 30.1 includes security fixes for a shell injection vulnerability in man.el (CVE-2025-1244), and for arbitrary code execution with flymake (CVE-2024-53920). We recommend upgrading immediately.
Time to make C the COBOL of this century (The Register - Opinion)
Lions juggling chainsaws are fun to watch, but you wouldn't want them trimming your trees
There's no perhaps about the FBI and CISA getting snippy at buffer overflows. These people worry about exploits that threaten car-crash incidents in enterprise IT, and they've seen enough to get angry. It's not that making mistakes is a crime when writing code. No human endeavor worth doing is without error. It's more that this class of bug is avoidable, and has been for decades, yet it pours out of big tech like woodworm from a church pew. Enough already, they say. They are right.
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=
<mode>
macro would also be conforming.
On Saturday, the ISO C++ committee completed the second-last design meeting of C++26, held in Hagenberg, Austria. There is just one meeting left before the C++26 feature set is finalized in June 20…
On Saturday, the ISO C++ committee completed the second-last design meeting of C++26, held in Hagenberg, Austria. There is just one meeting left before the C++26 feature set is finalized in June 2025 and draft C++26 is sent out for its international comment ballot (aka “Committee Draft” or “CD”), and C++26 is on track to be technically finalized two more meetings after that in early 2026.
It is now 45+ years since C++ was first conceived. As planned, it evolved to meet challenges, but many developers use C++ as if it was still the previous millennium. This is suboptimal from the perspective of ease of expressing ideas, performance, reliability, and maintainability. Here, I present the key concepts on which performant, type safe, and flexible C++ software can be built: resource management, life-time management, error-handling, modularity, and generic programming. At the end, I present ways to ensure that code is contemporary, rather than relying on outdated, unsafe, and hard-to-maintain techniques: guidelines and profiles.
I wonder if it would be possible to build such a tool on top of tree-sitter (although not sure tree-sitter's C++ grammar can handle modules yet)
Contracts for C++ explained in 5 minutes
With P2900, we propose to add contract assertions to the C++ language. This proposal is in the final stages of wording review before being included in the draft Standard for C++26.
Isn't that mainly just torrent trackers that publish your IP address and then the ISP gets a request for who was using that particular IP address. I don't think an ISP would itself be interested in detecting whether their customers download illegal content - there is no business case for them to do that.
Full-text search engine for the C++ Working Draft (and older versions from Tim Song's repository)
NetBSD 10.1 released
The NetBSD Project is pleased to announce NetBSD 10.1, the first point release of the NetBSD 10 stable branch.
On Saturday, the ISO C++ committee completed the third-last design meeting of C++26, held in Wrocław, Poland. There are just two meetings left before the C++26 feature freeze in June 2025, and C++2…
On Saturday, the ISO C++ committee completed the third-last design meeting of C++26, held in Wrocław, Poland. There are just two meetings left before the C++26 feature freeze in June 2025, and C++26 is on track to be completed two more meetings after that in early 2026. Implementations are closely tracking draft C++26; GCC and Clang already support about two-thirds of C++26 features right now.
Version 7.6 – the 'OpenBSD of Theseus' – released
Ideal for black-clad ultra-minimalist types. You probably wouldn't like it
EuroBSDcon 2024 in Dublin, Ireland: some notes after the conference
The empire of C++ strikes back with Safe C++ blueprint
You pipsqueaks want memory safety? We'll show you memory safety! We'll borrow that borrow checker
at least you could keep their reviews so users could at least know if the app can be trusted.
You mean, don't trust a flatpak uploaded by a random person, but if there are enough fake reviews, it can be trusted?
No mention of Reflection which was passed to the Core Working Group for wording review, or senders/receivers (on the library side) which was actually voted into the working paper.
Huh? There is no such alternation between new features and feature freeze releases. In fact, C++26 will very likely get reflection as a major new feature. In comparison, the biggest core language feature in C++23 was probably "deducting this (explicit object member functions)".
The only thing that keeps Contracts out of C++26 is that they might not be finished in time (they'll need to be handed over from Evolution to Core by the February 2025 meeting, and then make it through Core review during the summer 2025 meeting).
... except when ISO delays publication of the standard.
Can anyone explain why there is such a huge difference in some of the benchmarks: Poll, Forking, CPU Cache, Semaphores, Socket Activity, Context Switching (all Stress-NG). Can we really trust these tests?
Depends on what semantic you want. Sure, if you use a unique_ptr member, you will get a deleted copy constructor/operator - I wouldn't consider that blowing up in my face.
And even the presented fix hurts my eyes. Should have used a unique_ptr or optional.
Yes, it's not Open Source, but I am not sure that's really relevant here. I see it more as a prototype implementation for something that could be standardised for C++.
The linked tweet links to the recording, but it has apparently also been uploaded to YouTube: https://youtu.be/5Q1awoAwBgQ
Also the location of known Wifi networks.
Embracing the GC
I never actually liked the GC in D as it didn't seem to fit in with the general direction of the language, and Walter Bright in D at 20: Hits and Misses says:
Miss: Emphasis on GC
There is also lowendspirit, but in both cases you have to be very careful what you buy - not everything that is advertised there will work as advertised or will work long-term
where they will double your monthly data limit for free when you comment your order number.
where they use you to spam the forum thread (for giving away something rarely anyone has any use for)
So they actually rewrote The Hurd in Rust.
There is no reason to “hate” Ubuntu but there are better choices.
What are those better choices then (for those who currently use the non-LTS Ubuntu releases and don't want to move to rolling releases or LTS-only releases)?
I still think Ubuntu is the best option (particularly if you want to use the non-LTS releases)
Having said that I do hate snaps and also dislike flatpaks. So what I do is just use the Firefox deb package from the PPA and the chromium package from Linux Mint. Oh, and I have actually replaced ubuntu-advantage-tools with a no-op dummy package.