manjarno VS src

Manjaro downsides : list

Manjaro: just avoid it even if it is (apparently) newbie firendly.

Dude is a bot replying "Manjaro on x86 crashes and breaks alot". I would say Manjaro breaks a lot regardless of the architecture: https://manjarno.snorlax.sh/

windows: forces major updates to a new not yet ready major version windows: every app has a auto-launch and randomly updates in the background or is outdated windows: updates get stuck and happen right before meetings, etc windows: adds ads to your filemanager during updates and overall is more of a downgrade linux: i tell it t update when it fits me and dont even have to restart (ok its better to reboot after major updates, but i can also tell it to download&install everything and apply it during the next reboot) linux: if for some reason anything breaks i can just undo the update within grub/systemd-boot - meanwhile updating thunderbird killed one of my windows installations permanently manjaro: a burning shipwreck on all sides minimal-distros and other ones i wouldnt recommend for average users: updates require the terminal mint/pop/ubuntu/fedora: updates are neat little pop-ups and just offer it and work

Sets out to be an easy entry to Arch with sane defaults. It tries to achieve this by making the installation of Arch easy, adding GUI-tools to ease you into Linux, own repos with less bleeding-edge software and it ships a configured Btrfs+Timeshift for easy rollbacks to a working system. Unfortunately, the team behind Manjaro has some troubles...

The OpenBSD project released 7.4 of their OS on 16 Oct 2023 as their 55th release 💫

Well since https://www.openbsd.org/ still says

> Only two remote holes in the default install, in a heck of a long time!

I'm assuming not, but I could always be mistaken.

> building a cat from scratch

> That would be an interesting project.

Here is the source code of the OpenBSD implementation of cat:

> https://github.com/openbsd/src/blob/master/bin/cat/cat.c

and here of the GNU coreutils implementation:

> https://github.com/coreutils/coreutils/blob/master/src/cat.c

Thus: I don't think building a cat from scratch or creating a tutorial about that topic is particularly hard (even though the HN audience would likely be interested in it). :-)

> I don't know how they define `MAX`, but I'm guessing it's a typical "a>b?a:b"

Indeed: https://github.com/openbsd/src/blob/master/sys/sys/param.h#L...

> Then `SYS_kbind` seems to be a signed int.

It's an untyped #define: https://github.com/openbsd/src/blob/master/sys/sys/syscall.h...

I believe your whole analysis is correct, that running an elf file with an openbsd.syscalls entry with .sysno > INT_MAX will allow an out-of-bounds write.

I can reproduce it. And this is the commit that causes the issue: https://github.com/openbsd/src/commit/d21788ce70be80e9c4ed0c52c149e01147c4a823

This doesn’t really change your conclusion, but I think that’s the wrong file. This is the real doas afaict: https://github.com/openbsd/src/blob/master/usr.bin/doas/doas...

Still just a tidy 1072 lines in that folder though.

I spent 5 minutes staring at your file trying to understand how on earth it does the things in the man page, but of course it doesn’t.

OpenBSD developers are making serious effort to kill off indirect syscalls, the base system is completely clean, take a look at the work Andrew Fresh did to adapt Perl. He write a complete syscall "dispatcher" or emulator for the Perl syscall function so that it calls the libc stubs.

https://github.com/openbsd/src/commit/312e26c80be876012ae979...

The ports tree is also being cleansed of syscall(2) usage, until they're all gone.

msyscall, pinsyscall, recent mandatory IBT/BTI, xonly. OpenBSD is making waves, but people aren't really seeing them yet.

Actually, I got it wrong, too many vulnerabilities in flight. They did fix it: https://github.com/openbsd/src/commit/375ccafb2eb77de6cf240e...