Red Bear OS
263950aefa
CRITICAL BUG #1: is_syn() IPv4-only conntrack.rs is_syn() hardcoded offset 33 (IPv4: 20+13). For IPv6, TCP flags are at offset 53 (40+13). IPv6 SYN packets were never detected as SYNs, so SYN flood rate limiting was completely broken for IPv6 traffic. Fix: pass l3num, compute tcp_offset correctly for both families. Added ipv6_syn_detection_works regression test with IPv6 SYN packet at offset 53 — verifies the fix. CRITICAL BUG #2: netfilter writes all broken open_path stored paths without leading '/' (e.g. 'rule/add') but commit() compared against '/rule/add' (with leading '/'). Result: ALL write operations silently failed with EINVAL: - rule/add - never added rules - nat/add - never added NAT - rule/del - never deleted - nat/del - never deleted - policy/X - never set policy - reset - never reset - counters/reset - never reset Fix: align commit() paths with the stored convention (no '/'). Removed dead /rule/del/<id> REST-style path (no open_path arm existed). Updated stored path convention comment. Tests: 21 total (added ipv6_syn_detection_works), all passing.
Base
Repository containing various system daemons, that are considered fundamental for the OS.
You can see what each component does in the following list:
- audiod : Daemon used to process the sound drivers audio
- bootstrap : First code that the kernel executes, responsible for spawning the init daemon
- daemon : Redox daemon library
- drivers
- init : Daemon used to start most system components and programs
- initfs : Filesystem with the necessary system components to run RedoxFS
- ipcd : Daemon used for inter-process communication
- logd : Daemon used to log system components and daemons
- netstack : Daemon used for networking
- ptyd : Daemon used for pseudo-terminal
- ramfs : RAM filesystem
- randd : Daemon used for random number generation
- zerod : Daemon used to discard all writes and fill read buffers with zero
How To Contribute
To learn how to contribute you need to read the following document:
If you want to contribute to drivers read its README
Development
To learn how to do development with these system components inside the Redox build system you need to read the Build System and Coding and Building pages.
How To Build
It is recommended to build this system component via the Redox build system, you can learn how to do it on the Building Redox page.
To build and test outside the build system, install redoxer then use check.sh script to build or test:
./check.sh- Check build for x86_64./check.sh --arch=ARCH- Check build for specific ARCH (aarch64,i586,riscv64gc)./check.sh --all- Check build for all ARCH./check.sh --test- Check the base system boots up on x86_64
You can also use make install to inspect the content on ./sysroot, or make test-gui to test booting with orbital interactively.