Search the Community
Showing results for tags 'secure'.
Found 2 results
Fuchas One of the best OSes (as said by me) Fuchas in a Nutshell Fuchas is revolutionnary in that it uses drivers instdead of component access and support UAC (with separate permissions!) ! It's the end of the era where the program needs to maintain integration with different components, the OS now does it! The driver library will try automatically choosing the best driver, but it can be configured by user. Meaning programs adapt to components with no effort (e.g. Computronics cards) Mostly one of Fuchas big feature is security. Feared of viruses or foreign access? Control permissions! Each account can have its own set of permissions! Allow one to have free access on a specific drive? You can do that!. Security is useful for computers on big servers with competivity. Fuchas doesn’t hide files starting with ".", it uses attributes, filesystem’s one if supported on unmanaged drives, or with a .dir file at file’s parent directory. It only provides yet those attributes: System (requires permission to write, but not to read), Protected (needs specific permission to write AND read), Hidden and Read-Only Fuchas is also fast at startup, around 2x faster than OpenOS down like memory usage. And graphical features are optional, so you can use command-line on your T1 computer, and a graphical interface on T3, all on the same OS! And since the UI is compatible with 40x16 and doesn't uses a lot of memory, you can use both on a T1 computer! Extra Features (compared to other OSes) First Fuchas automatically handles Unicode with string library, the methods are the same, except it is now unicode. Of course it can be disabled for applications not wanting Unicode (mostly when operating with bytes using text) (WIP - Planned -->) Fuchas will also use the viewport screen feature to have an efficient double-buffer and extra rendering speed compared to other GUIs. It work in a way that for example, user will have a resolution of 80x25, but it will be viewport, resolution will stay at 160x50, meaning that it frees two 80x25 areas (right and bottom). Using those efficiently will allow fast copying to viewport. If the user accepts it and there is enough memory available, Fuchas will use a memory double-buffer for OCX (the UI and drawing library of Fuchas) which so keeps the best advantage of two worlds, with out-of-viewport buffers allowing for fast move using screen copy, and the double-buffer to optimize operations. Interfaces Fuchas, being modular, is about not fair to have 1 interface. That's why there can be multiple interfaces. Here are the interfaces included: Fushell (basically like OpenOS shell) and Concert. Soon to come will be "Ondroid" (tablet interface), which is a GUI interface, better suited for multi-tasking. For example here is Fushell (warn: old version [4 major releases ago], but still a little representative): I'm not doing a whole documentation here, but basically "pl" lists processes. Install It OpenOS: Just type the following: pastebin run EbHYvEE8 MineOS: Search for the application 'Fuchas Installer'. Install it, launch it, and press Install. Fuchas: You’re on Fuchas (Note that all comments about broken installation below are outdated, and installers has been fixed!) Links: GitHub, Wiki, Progress to next version, And here is how to break the whole Fuchas security system
With the newest versions of Feed the Beast featuring opencomputers prominently on 1.10.2 I decided it was time to start publicly releasing my opencomputer OS project. I have started working on an operating system that implements proper kernel protection rings, secure system calls, and process management. It will be modular with integrated hardware drivers, so it will support most major mods in a secure way. It will feature a package manager to download both drivers and applications, hosted globally or allowing private hosts for servers that want to pick which software packages are available. It will also have built in support for a UDP-like protocol, which will be supported by a range of services like DNS and routing services which allow proper addressing. They won't be 1-to-1 implementations because that would be far too large to implement or maintain, but they will follow the same basic principles. The networking stack will allow drop-in protocols, so future implementations of true TCP (proper connection throttling, segmented transfers and error detection) are possible. [For clarification this is a layer 3 to layer 7 partially implemented stack] The OS will not feature a GUI to begin with unless I find someone very competent who would work on that, as the amount of security and networking code this will require is monolithic and I doubt I will have the time to work on that. I will also be creating full featured documentation for the OS,how to interface with it and write apps, as well as how to setup and install a working network with it. Hopefully I will have something to show everyone soon. For now I have not included any source code until I can get a working version of the full kernel with sandboxing. I'll be posting updates here and on the repository once I share it and would appreciate feedback once I get to that point. I will be hosting a server as well to test large scale network design and allow people to see what the system is capable of once I get fully-working prototypes.