Advanced Computing Environment
Hosted by SourceForge
brix-os project page

BRiX is a new operating system that redefines how operating systems should be designed. Like conventional operating systems, it will provide features such as SMP, preemptive multi-threading, virtual memory, a secure multi-user environment and an easy to use graphical interface.

BRiX is not a conventional operating system and some of its new features include:

The security in BRiX will allow untrusted source code to be downloaded and installed without worry of it harming the system or user data. The safe-language should further increase security by preventing buffer overflows and unchecked values in external services and local applications. Administrative users always have full access without needing to explicitly lower or raise their privileges, and this has no impact on security.

It does not prevent someone else from logging into the system with your credentials. Various techniques can be used to limit the success rate of brute force attacks on the local and remote auth services but simple passwords can be guessed and no amount of security will help. There is no cure for stupid.

Physical Access
It does not prevent someone with physical access from modifying binary and data files using another operating system. Encryption and other methods can be employed to secure the filesystem from simple attacks but there is no way to stop someone who has physical access, is motivated and has the right tools. This applies to all operating systems.

Compiler Bugs
Bugs in the Tetra implementation are like bugs in the Linux kernel or the GNU toolchain. Both can lead to system instability or exploitation. A C compiler is written in C and Linux is written in C. A minimal Tetra compiler will be rewritten in C which then bootstraps the full Tetra compiler written in itself, therefore, a stable Tetra compiler should provide far more security than a stable Linux system.

Memory Corruption
Cosmic radiation and hardware errors can cause memory bits to randomly change values, this is highly unlikely but affects all systems when it does happen. The lack of hardware protection between processes and with many runtime checks happening at compile-time means BRiX is more likely to crash. The stability of other systems in this situation wouldn't be much better and hardware error correction is the only real solution.