GraphvizOnline VS src

(paste it into https://dreampuf.github.io/GraphvizOnline to see a visual representation)

Where task 1 diverges, you can run task2 and task3 in parallel, because they don't depend on eachother's outputs. Then you need to join task4 and task5 to task6.

My email is in my profile, I'd love to chat about your thoughts on what futuristic software means to you. For me it means futuristic interactions with computers, alternative approaches to programming.

You can view this file with the Graphviz binary or an online tool like Graphviz Viewer.

You can copy and paste this DOT graph code into an online graph visualization tool like GraphvizOnline to see the visual representation of the code flow.

You can ask gpt to output as (mermaid / graphvis digraph) format via a code block. Then view inside a valid viewer like https://mermaid.live or https://dreampuf.github.io/GraphvizOnline

Visualization was made by me using GraphVIZ, and rendered using dot. You can see the source here, and you can mess around with it by plugging the source into this handy website. You can remove factions you don't care about, or update to fit the fiction in your game..

After moving through the new Graph, is_cyclic, and prune you get to the real meat and potatoes: shortest unweighted, shortest weighted, and max flow. In the following I want to discuss some representation/visualization (shoutout Graphviz).

https://dreampuf.github.io/GraphvizOnline/ for making a basic figure.

Note: - Tools used Graphbiz and dot language: https://dreampuf.github.io/GraphvizOnline - Source: https://satisfactory.fandom.com - Recipes used are the best based on a resource-weighted analysis (Weighted Point is the weighted consumption rate which is calculated by: (resource consumption rate / maximum extraction rate) * 10,000. The lower the better. ) - Some numbers have been simplified i.e. 8.8888 to 9 to simplify other calculations. - Energy and its resource needs are not included

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...