Recordings will be released after the conference, but I was happy enough with my dry run or backup recording that I'm making that available too, along with the slides to follow along. I hope this will be useful in your advocacy or education on OpenBSD and why the project matters.
In case you were wondering, this is an update on a talk we covered previously, with updates to cover the more recent OpenBSD 6.8.
from the who-says-i'm-stable? dept.
Solène Rapenne (solene@) has written a
on the software system underlying the building of -stable packages:
In this long blog post, I will write about the technical details
of the OpenBSD stable packages building infrastructure. I have setup
the infrastructure with the help of Theo De Raadt who provides me
the hardware in summer 2019, since then, OpenBSD users can upgrade
their packages using pkg_add -u for critical updates that has
been backported by the contributors. Many thanks to them, without
their work there would be no packages to build.
The new release comes with a large number of improvements and debuts a new architecture, OpenBSD/powerpc64, running on the POWER9 family of processors. The full list of changes can be found in the announcement and on the release page. Some highlights:
As already mentioned, this release debuts the OpenBSD/powerpc64 architecture, supporting the POWER9 [and POWER8] family of processors.
Numerous kernel improvements such as better time measurements across several architectures,
(see eg this article),
updated graphics support, and of course numerous improvements in hardware support with updated drivers across several platforms.
Thanks to the developers for all the good work that went into this
excellent new release!
While your install sets download or when your packages update, please take the time to look at and use one or more of the recommended ways to support the project, such as making a donation, buying T-shirts. Corporate entities may prefer sending some money in the direction of the OpenBSD Foundation, which is a Canadian non-profit corporation.
from the token-effort dept.
Hitherto, releases of the
software (which underlies
have been unsigned.
This is overdue for change, so for the latest release [version 1.7], we are providing a digital signature.
As signing is being performed manually, why not employ an additional [hardware] factor?
does not support the use of FIDO authenticators.
However, recent versions of
OpenSSH do support signing
using the [under-appreciated]
-Y sign option of
and with the recent addition of FIDO authenticator support to OpenSSH
[as reported previously],
we have a means (using tools in base OpenBSD) of using a hardware factor when signing files.
Ingo (schwarze@) writes in about a side project he's been working on to do his own accounting:
Sometimes, it happens to me that i make little progress with the
work i planned to do (so let's not talk about the badly needed
mandoc release today) and instead end up doing work that wasn't
planned at all.
Fresh off the k2k20 hackathon, Rafael Sadowski (rsadowski@)
Due to the pandemic, this hackathon seemed to be called very spontaneously.
Fortunately, the hackathon was over a weekend. This enabled me to attend
without missing any professional obligations. On Friday morning, shortly after
sunrise, I took the train to Bad Liebenzell. On the train I worked for my
employer until I reached Karlsruhe at about 11am. I swapped my MacBook for my
OpenBSD ThinkPad T470s.
The fourth report from k2k20 comes from Florian Obser (florian@), who worked mostly on DNS related things:
I spent the week before the hackathon with monitoring the current
pandemic situation. Will ze germans let me in? Will I put people at
risk? In the end it all looked OK-ish and I booked my train ticket a
day before leaving. Time to pack!
My current bag of holding is an Osprey Talon 22 and it fits an X1,
roost laptop stand, Microsoft sculpt keyboard, assorted cables,
toiletry bag and clothing for 6 days. Yes, this includes fresh
underwear and T-Shirts for every day.
from the hotwired or notwired dept.
Our next k2k20 report comes from Klemens Nanni (kn@):
I'd been looking forward to k2k20 just like my
other hackathon with its unique
atmosphere where getting work done in fact means holiday hacking with friends.
There was nothing big on my list but it had already grown into a rich assortment
of issues and itches to scratch - this usually aligns well with the release
cycle since it means focusing on regression fixes and polish during the -beta
phase until the tree gets locked for release.