Fresh off the k2k20 hackathon, Rafael Sadowski (rsadowski@) writes in:

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.

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.

Fresh off the just-finished k2k20 hackathon, here is a report from Bob Beck (beck@):

We have a saying about hackathons - They are for starting something, or for finishing something. This time for me was a "finishing something" - I landed the new x509 certificate chain validation in libcrypto.

The k2k20 hackathon concluded recently, and we are please to have received a report from Martijn van Duren (martijn@):

I came to k2k20 on my motorcycle with my mask, a small backpack and a stack of projects burning on my laptop to get pushed. After a long ride ending on the lovely winding roads of the black forest I arrived at Burg Liebenzell slightly past noon, where I was greeted by a collection of other OpenBSD developers who just came back from lunch. After checking in and a quick lunch of my own I joined the rest in the hackroom where everything was set up in a wide circle giving every table plenty of room for privilege separation^W^Wsocial distancing.

With this commit, Martijn van Duren (martijn@) added login_ldap(8) to -current:

CVSROOT:	/cvs
Module name:	src
Changes by:	martijn@cvs.openbsd.org	2020/09/12 09:06:12

Modified files:
	libexec        : Makefile 
Added files:
	libexec/login_ldap: Makefile aldap.c aldap.h bind.c login_ldap.8 
	                    login_ldap.c login_ldap.h search.c util.c 

Log message:
Import login_ldap.

The code is based login_ldap port, but uses our own aldap implementation
instead of openldap. It also uses a stand alone configuration file
instead of login.conf, since setting this up might contain information
not destined for everyone to see.

OK bluhm@
"Go for it" deraadt@

An example configuration file was also committed.

Theo (deraadt@) has just committed the crank to 6.8-beta to CVS

From: Theo de Raadt
Date: Mon, 31 Aug 2020 10:08:28 -0600 (MDT)
To: source-changes@openbsd.org
Subject: CVS: cvs.openbsd.org: src

CVSROOT:        /cvs
Module name:    src
Changes by:     deraadt@cvs.openbsd.org 2020/08/31 10:08:28

Modified files:
        sys/conf       : newvers.sh 
        sys/sys        : param.h 
        usr.bin/signify: signify.1 
        etc/root       : root.mail 
        share/mk       : sys.mk 
        sys/arch/macppc/stand/tbxidata: bsd.tbxi 

Log message:
crank to 6.8-beta

You know what this means: time to test snapshots and report any issues you find, both in the base systems as in the supplied packages, so that the upcoming 6.8 release will not surprise you in unfortunate ways!

Frederic Cambus (fcambus@) has published an article on his blog about the work that has been done to improve the text-console experience on OpenBSD. Well worth a read if, as a proper UNIX-sysadmin, you enjoy working in a text-only environment; but also if you spend most of your time in X!

More than six years ago, LibreSSL was forked from OpenSSL, and almost two years ago, i explained the status of LibreSSL documentation during EuroBSDCon 2018 in Bucuresti. So it seems providing an update might be in order.