Elektrine
Log in Register

#openbsd

35 posts · Last used 1d

Back to Timeline
@rqm@exquisite.social · 2d ago
$ ssh puffy@fishtank.openbsd.amsterdam The fishtank already runs the latest snapshot on -current, all locked and loaded for the imminent release of 7.9! #OpenBSD #79hype #RunBSD @OpenBSDAms@mastodon.bsd.cafe @mischa@exquisite.social
6
0
2
In reply to
@kkarhan@jorts.horse · 1d ago
@libreleah@mas.to nice to see #Wayland getting adopted more. Certainly neither it nor X are the main focus of it, but it's always good to see #OpenBSD not just getting maintenance but improving.I genuinely want OpenBSD to be more successful and force eberyone else to up their game in #ITsec…
0
0
0
Boosted by Kevin Karhan @kkarhan@jorts.horse
@justine@snac.smithies.me.uk · Apr 18, 2026
@libreleah@mas.to has submitted the #librewolf port to #OpenBSD ports so fingers crossed it won't be too long until the package is available in -current . https://marc.info/?l=openbsd-ports&m=177652909703481&w=2
0
0
1
In reply to
@kkarhan@jorts.horse · 1d ago
@kaidenshi@exquisite.social @libreleah@mas.to @MaddieM4@raphus.social yay! Also nice to see #OpenBSD used as #Desktop OS…
0
0
0
@kaidenshi@exquisite.social · 5d ago
I am slowly coming to understand that the reason some applications crash often on OpenBSD is not the fault of OpenBSD, but the fault of poorly written applications that have tons of vulnerabilities. OpenBSD is designed to be a secure operating system as one of its main goals, and trying to circumvent these safety guardrails by "optimizing OpenBSD for desktop use" -- i.e. tweaking sysctl.conf to the max -- defeats the purpose of having the guardrails in the first place. If you want an OS where applications are free to roam full of holes and exploits without crashing, use Linux I guess. It will happily continue to allow those poorly written programs to run, giving the user a false sense of stability. Meanwhile, I'm starting to prefer safety and security over "desktop performance at all costs". If a program misbehaves it should die, and OpenBSD will kill it before I even know it misbehaved. #OpenBSD #ProactiveSecurity
51
0
25
@h3artbl33d@exquisite.social · 3d ago
Hey fellow #OpenBSD crowd :flan_coffee: I am worried about @tedu@honk.tedunangst.com - can't get a hold of him, last CVS commits were somewhere 2025, no Fedi activity, websites down, etc. Just wanted to make sure he is okay, regardless of the reason for being inactive.
45
2
58
@h3artbl33d@exquisite.social · 5d ago
#MastoAdmin on #OpenBSD feel:
4
0
3
@lobsters@mastodon.social · 5d ago
Math is hard (OpenBSD on VAX) via @rk@mastodon.well.com https://lobste.rs/s/nvwn1i #historical #openbsd http://miod.online.fr/software/openbsd/stories/vaxfp.html
0
0
0
@miodvallat@hostux.social · 5d ago
Time for a new #OpenBSD story! Investigating what appears to be a VAX bug turns out to be the consequence of a more-than-late processor design change, so brace yourselves for a VAX history lesson! http://miod.online.fr/software/openbsd/stories/vaxfp.html
30
0
32
@JdeBP@mastodonapp.uk · Mar 01, 2026
#CaliforniaLaw is written by people who are either very ignorant or very incompetent. https://leginfo.legislature.ca.gov/faces/billStatusClient.xhtml?bill_id=202520260AB1043 They have assumed that all operating systems are like Microsoft Windows 11, Android, or iOS; and have written legislation for operating systems where people download glorified WWW client 'apps', from 'stores', which use 'accounts' that they have with vendors or Microsoft/Google/Apple. But the legislation *as worded* *also* covers everything from #Debian and #Ubuntu through #Arch Linux and #MobaXTerm to #FreeBSD and #NetBSD and #OpenBSD; where users anonymously use package managers or ports systems to install applications, written by developers, on operating systems, from 'publicly available internet website' repositories. There is no age field in the GECOS data in master.passwd(5) of course, and the reality is that no BSD or Linux-based operating system has this concept of apps/stores/accounts. #MidnightBSD #FreeSoftware #Unix #California #USLaw #AgeVerification #GDPR
22
0
15
@tubsta@social.bsdlab.au · 6d ago
Might be time to give #DragonFlyBSD a spin again. I want to get familiar with HAMMER2 more. I wonder what @tj@altelectron.org.uk would think. I'd love to see #HAMMER2 in #OpenBSD one day.
0
0
0
@oxy@social.bsdlab.au · 6d ago
https://polymathmonkey.github.io/weblog/artifacts/openbsdmalloc/index.html #OpenBSD
0
0
0
@km@mastodon.babb.no · Apr 14, 2026
so hw.smt is deprecated, and hw.blockcpu should be used instead #OpenBSD
4
0
1
In reply to
@tomekw@functional.cafe · Apr 13, 2026
@pointlessone@status.pointless.one I have a hard time builing #AdaLang LSP on #OpenBSD. It makes me want to abandon the whole "switch to #BSD" idea and stick to the old boring #Debian Stable...
0
1
0
@JdeBP@mastodonapp.uk · Apr 09, 2026
Here are some things that one can add to the analysis of the MacOS TCP timeout clock freeze bug. The code for calculate_tcp_clock() in XNU was changed in May 2025. Older versions of this function (e.g. in xnu-11417) worked quite differently and wouldn't have stopped ticking the clock at 32-bit unsigned integer wraparound. None of #NetBSD, #FreeBSD, nor #OpenBSD share this exact way of doing TCP timeout processing with #XNU. FreeBSD does not have a tcp_now and works off the global 32-bit ticks variable. OpenBSD effectively works off the kernel's system clock, too, but with a randomized offset, and does 64-bit unsigned modular arithmetic. NetBSD uses a distinct 32-bit unsigned tcp_now counter that it simply increments by 1 at regular intervals, and does modular arithmetic subtraction. https://photon.codes/blog/we-found-a-ticking-time-bomb-in-macos-tcp-networking #TCP #MacOS
0
0
0
@JdeBP@mastodonapp.uk · Apr 08, 2026
The new way of selling 'AI' seems to be to push it as a bugfinder. The latest example being waved around as of yesterday includes, as one of its non-embargoed examples, what is patched by this #OpenBSD patch. https://ftp.openbsd.org/pub/OpenBSD/patches/7.8/common/025_sack.patch.sig The problematic thing is that this sort of bugfixing hasn't changed the commentary in the code, which stated that p points to the last linked list entry at the point of the added null check and can never be null. But it actually can be, if there was a sole linked list entry that ended up being fully encompassed and thus deleted. So this kind of 'AI' use is going to give us a lot more comments-do-not-match-code maintenance headaches down the road. (Both #NetBSD and #FreeBSD factor this out into a separate tcp_sack.c and do the linked list handling slightly differently without a 'previous' pointer.) #AI
0
0
0
@lobsters@mastodon.social · Apr 07, 2026
[discussion] the BSDs in the AI Age via @lattera@bsd.network https://lobste.rs/s/pdhar1 #culture #freebsd #netbsd #openbsd https://lists.nycbug.org/pipermail/talk/2026-April/018894.html
0
0
0
@alip@mastodon.online · Apr 05, 2026
News from #sydbox git: Starting next release, we're going to be signing binary releases with #OpenBSD signify rather than #GnuPG. To enable practical signing in #Exherbo #Gitlab CI, I wrote an #ISC licensed, pure portable #POSIX shell implementation of #OpenBSD signify. signify.sh has no external dependencies and runs with PATH=. It has unit tests embedded which may be run with --test option: https://gitlab.exherbo.org/sydbox/sydbox/-/raw/next/dev/signify.sh #exherbo #linux #security
9
5
8
@lobsters@mastodon.social · Apr 03, 2026
OpenBSD on Motorola 88000 processors https://lobste.rs/s/1urnpv #openbsd http://miod.online.fr/software/openbsd/stories/m88k.html
0
0
0
@izder456@fe.disroot.org · Mar 26, 2026
What led up to my switch to #openbsd? I was fucking around with linux distros among other unixen in libvirt and qemu-kvm on my gentoo box to avoid distrohopping cos i was starting to get frustrated with the linux ecosystem and community chaos. Eventually i installed openbsd in a vm and really liked it. Nuked my gentoo install with openbsd and went full send. Never looked back. though occasionally ill dick around with weird niche poweruser linux distros when bored on spare hardware.
0
0
0