What if I told you there’s an OS that’s ultra-secure, actively developed — but without much noise? What if I add that Windows, Mac & Android are all using parts of this Operating System?
@DrHyde Probably unrelated, but did you removed the now-unnecessary PerlIO::scalar after upgrading to #OpenBSD 7.7:
https://www.openbsd.org/faq/upgrade77.html#RmFiles
I didn't look any further other than seeing that it's to be removed, Perl-based, and I/O related.
@timb_machine I have it running on #Openbsd -current on my Lenovo Thinkpad E16 v2. Hibernate/suspend doesn’t resume and two finger scroll doesn’t work on the track pad. KDE Gear is beautiful. And it works. Except left click when using Dolphin file browser thing.
OpenBSD boots and works - but it seems the trackpad isn't moving. I'm sure I can fix it as it's correctly detecting it, but I'm now testing FreeBSD.
It immediately throws a kernel panic, but this seems to the the problem:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274014
So, 15-CURRENT boots and works. I'll probably burn a 14-STABLE usb pen and continue with that.
Let me introduce you to aceBSD! Yesterday, while I was out grocery shopping, I saw a special offer on a final unit, and I had already been thinking for a while about getting a mid-range laptop to take with me to conferences, on trips, etc. Something small, practical, with an HDMI port, and capable of running at least one of the BSDs decently. After some careful thought, I decided to go for it today.
It's an Acer Swift Go 14 - with an Intel i5, 16 GB of RAM, and a 512 GB NVMe SSD. What I really like is that it’s compact and has a high-definition OLED screen, a good keyboard, and for the rest... we’ll see. I just used Clonezilla to make a backup of the preinstalled Windows (I didn’t even boot into it...) and I’m now installing OpenBSD. I had to disable VMD (from a hidden BIOS menu) because otherwise the installer wouldn’t detect the NVMe. It also seems to detect the Wi-Fi, but I’m proceeding with a USB-C Ethernet adapter just to be safe.
I got it at a good price, so this could be the ideal solution. Fingers crossed, and… we’ll see!
I'll keep posting about this adventure, with the hashtag #aceBSD
#OpenBSD -current has replaced its own aging (freedesktop.org compatible) pkg-config(1), originally written in Perl by ckuethe@, espie@ & jasper@, with the more modern and actively maintained pkgconf implementation.
tb@ modified src/usr.bin/pkgconf/*: import pkgconf 2.4.3
Our homegrown Perl-based pkg-config cannot cope with the giant DAGs [Directed Acyclic Dependency Graphs] arising in modern software, especially from the abseil-cpp and protobuf family. Waiting minutes for configure to complete in some ports is just awful.
Thus we're switching to the sanely-licenced, widely used pkgconf, which is actively maintained, written in a sensible dialect of C, and does not suffer from these performance issues.
Work that should happen in tree during this cycle:
- see what we want to do with our old manual and pkgconf's
- add pledge and unveil.
Initial work done by espie during or right after p2k23, support from many.
ok semarie
The old pkg-config implementation has now been unlinked from the build, but not yet removed from the tree.
tb@ modified src/usr.bin/Makefile: switch from pkg-config to pkgconf
leave the old pkg-config in the tree for now.
@MichaelRoss given #CloudAct and other tools of #Espionage against the #UN, this does make sense.
Ooh, new #OpenBSD release!
nice, baikal #openbsd port works even with a higher php version \o/
Looks like mpi@ has been roleplaying as Doomguy, R.I.P and tearing the reaper process out of the #OpenBSD kernel. 
https://marc.info/?l=openbsd-tech&m=174618517712499&w=2
If people are interested, Martin is looking for test reports.
I'd appreciate tests reports on many different setups as well as other architectures.
"I have yet to meet an admin who plausibly claims to never have been tripped up by their overload rules at some point."
More, and a walk down memory lane, in "The Hail Mary Cloud And The Lessons Learned" https://nxdomain.no/~peter/hailmary_lessons_learned.html
#ssh #passwords #bruteforce #passwordgroping #cybercrime #openbsd #pf #packetfilter #security #guessablepasswords #hailmary #hailmarycloud
et baikal sous #openbsd n'est pas dispo avec sqlite, car il n'y a plus l'extension sqlite avec la version de php pour laquelle baikal est packagée...
In addition, a new lldp(8) companion command line utility for interacting with the new #OpenBSD lldpd(8) daemon has been added.
dlg@ modified src/usr.sbin/lldp/*: add lldp(8), a command line tool for interacting with lldpd(8).
lldp can fetch LLDP packets from lldpd and then pulls them apart and displays them.
by default it shows a brief summary of the lldp neighbor ports and systems on all interfaces, but you can request verbose info and/or info only from specific local interfaces.
now that i've done the easy part (implementing AF_FRAME and lldpd) it would be nice to get some help with the hard stuff (pretty printing strings in c).
ok djm@ deraadt@
general enthusiasm from many
David Gwynne (dlg@) has imported a new daemon to #OpenBSD -current, not yet linked to the build.
lldpd(8), a new LLDP (Link Layer Discovery Protocol) agent daemon.
This daemon uses the newly added AF_FRAME socket protocol type.
dlg@ modified src/usr.sbin/lldpd/*: lldpd(8): a daemon that acts as an LLDP agent on Ethernet interfaces.
lldpd uses the recently added AF_FRAME Ethernet sockets to listen for LLDP packets on all Ethernet interfaces in the system, and stores them so a lldp(8) client connecting to the control socket can fetch and display the packets.
AF_FRAME means we can avoid BPF for receiving LLDP packets, which has a couple of benefits.
firstly, BPF needs to look at all packets entering an interface so it can filter for the ones you're interested in, which is annoying for low packet/data rate protocols like LLDP. AF_FRAME is handled late in ether_input, and only after other protocols (like ip) are handled, so it's lower overhad compared to BPF listeners.
secondly, attaching a BPF filter to new interfaces relies on having access to and the privileges to open /dev/bpf, while AF_FRAME provides a wildcard listener that is able to receive LLDP from all interfaces on a single socket, like how binding to on 0.0.0.0 with an AF_INET socket let's you receive packets for all the IPs on your system from a single socket. lldp can create and configure this socket when it starts up just use it from then on. this means lldpd is simpler and needs fewer privileges to operate than if it went the BPF route.
at the moment lldpd only handles LLDP packet reception on all interfaces, you can't disable reception on interfaces yet. it also doesn't transmit LLDP packets (yet).
there is no intention of implementing any protocol other than LLDP in this daemon either.
ok djm@ deraadt@ general enthusiasm from many
Call for testing and comment: Make the installer prefer >1G disks #openbsd
https://undeadly.org/cgi?action=article;sid=20250502060000
Call for testing and comment: Make the installer prefer >1G disks https://www.undeadly.org/cgi?action=article;sid=20250502060000 #openbsd #installer #disks #storage #softraid #keydisks #partitioning #development #configuration
There is no official OpenBSD Handbook.
The site claiming to be so is not from the project, and on top of just copy and pasting a lot of FAQ content (at one point) without credit, it has lots of things that are incorrect.
The amount of times I see "Well, that's what the handbook says" on reddit. 
Gear 25.04 has made it into 
