Hacker Newsnew | past | comments | ask | show | jobs | submit | brynet's commentslogin

OpenBSD developer Tobias Heider (tobhe@) has already committed the first pieces of OpenBSD/arm64 support for these Qualcomm Snapdragon X2 Elite laptops.

"This gets USB, keyboard and touchpad working in ACPI mode on the HP Elitebook X G2q."

https://marc.info/?l=openbsd-cvs&m=178891082169317&w=2

Tobias (who also works for Canonical) recently demoed Ubuntu on mastodon and confirmed ARM EL2 works, meaning KVM support unlike previous generations.

bsd.network/@tobhe/117122761215052773

(I'd love to get my hands on one of these X2 Elite machines, hmu qcom.)


> At that time, its researchers have modified Chromium to make use of Capsicum and compared how much effort was required to make use of each sandboxing mechanism within Chromium. [..] If you’re only going to study one sandboxing mechanism in your life, it should be Capsicum. To this date, I have yet to see a better sandboxing mechanism than Capsicum.

In the years since it was added, there's a reason you can count on two hands the number of programs using it in FreeBSD. Even less using it effectively, with refactoring, and not just calling cap_enter().

Capsicum Chrome has never been committed to the official FreeBSD ports tree, it was an academic research project from 17 years ago.

https://github.com/rwatson/chromium-capsicum

https://www.freshports.org/www/chromium/

https://cgit.freebsd.org/ports/log/www/chromium/Makefile?qt=...

No browsers on FreeBSD today use Capsicum.

Compare that instead to OpenBSD, where the Chromium port has used pledge(2) since January 2016, and unveil(2) since 2018. Enabled by default. The Mozilla Firefox ports also use both pledge and unveil since 2018-2019, and this work has even been accepted upstream.

https://marc.info/?l=openbsd-ports-cvs&m=145211683609002&w=2

https://github.com/openbsd/ports/blob/master/www/chromium/pa...

https://github.com/openbsd/ports/tree/master/www/chromium/fi...


> No browsers on FreeBSD today use Capsicum.

Strictly speaking, that's false, my hobby project chawan[1] supports capsicum :)

Anyway, IME capsicum vs pledge doesn't make much of a difference because seccomp already forces you into a specific sandbox architecture; after implementing that, adjusting the result to support the rest takes (relatively) little effort. So I think the difference in adoption is more because nobody has volunteered to do the work for capsicum (and keep it up to date etc.)

[1]: https://chawan.net


Making rent as an open source developer.

Desperately trying to attract new monthly sponsors and people willing to buy me the occasional pizza with my terrible HTML skills. Is it working?

If any individuals, companies (or bitcoin millionaires) would like to help a long-time OpenBSD slacker, unslack, I'd really like to focus more of my time on open source development (and advocacy), rather than making rent. Feel free to contact me.

https://brynet.ca/wallofpizza.html

(Native SegWit): bc1qwe6zv0ezq4gzlea6tw45qhsn5kckheljn0krvt


I'm curious what 2.5GbE chipset they used.


I assume a Aquantia one.


Making rent as an open source developer.

Desperately trying to attract new monthly sponsors and people willing to buy me the occasional pizza with my terrible HTML skills. Is it working?

If any individuals, companies (or bitcoin millionaires) would like to help a long-time OpenBSD slacker, unslack, I'd really like to focus more of my time on open source development (and advocacy), rather than making rent. Feel free to contact me.

https://brynet.ca/wallofpizza.html

(Native SegWit): bc1qwe6zv0ezq4gzlea6tw45qhsn5kckheljn0krvt


Do see: https://oss.fund/ All the best!


Thanks, but unfortunately I found nothing new there that's applicable in my case. Not looking for project grants or rigid commitment/goals based funding at this time.


> IIRC OpenBSD used to use GCC 2.95 for years.

2.95.3 and 3.3.6, both have now been retired in favour of gcc4. The majority use clang now, though.


Indeed, 4.2.1 was the last GPLv2 version. OpenBSD still uses it (w/ patches) for a few platforms, for example.

/bsd.own.mk:GCC4_ARCH=alpha hppa m88k sh sparc64

The rest have already been migrated to LLVM/Clang 22 by default (except sparc64 below, that's experimental).

./bsd.own.mk:CLANG_ARCH=aarch64 amd64 arm i386 mips64 powerpc powerpc64 riscv64 sparc64


Making rent as an open source developer.

Desperately trying to attract new monthly sponsors and people willing to buy me the occasional pizza with my terrible HTML skills. Is it working?

https://brynet.ca/wallofpizza.html


This is not usenet, it's the openbsd misc@ mailing list.


Maybe they mixed up usenet by doing what I used to do back then - use gmane so I could follow various mailing lists via NNTP for better thread tracking and not filling up my inbox.


No.

https://github.com/openbsd/src/blob/d5b0ed23b6fe61f0278c37a4...

Perhaps relevant, Students from the University of Southern Denmark released a paper earlier this month, which once again noted the fact that over ~90% of the OpenBSD base system uses pledge(2). Almost certainly all of the network speaking daemons in base do.

https://arxiv.org/abs/2607.03056


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: