News for hackers. Stuff that matters.
Re:Writing an OS in Rust by vinc on Saturday September 14, 2024 @01:46PM (#41541454)
I started working on MOROS[1][2] after completing the tutorial 5 years ago, and I cannot recommend it enough for anyone interested in Rust and osdev. Phil put a lot of work into it, and it shows! The project covers a lot, and after that there's the osdev wiki[3] to keep going.

[1]: http://moros.cc

[2]: https://github.com/vinc/moros

[3]: https://wiki.osdev.org

[dead]
Re:Writing an OS in Rust by vinc on Sunday September 15, 2024 @03:01AM (#41545774)
Thanks! If you try again and still have it don't hesitate to create an issue on GitHub and I'll look into it!
Re:Writing an OS in Rust by codethief on Saturday September 14, 2024 @04:34PM (#41542630)
Re [1]: No TLS? :(
Re:Writing an OS in Rust by vinc on Saturday September 14, 2024 @05:06PM (#41542955)
Good question, there's no TLS support inside MOROS so its website must be available over HTTP, especially when I self-host it. That's not the case currently so I could also have HTTPS but I'm using Dokku and last time I tried the Let's Encrypt plugin would redirect HTTP to HTTPS automatically, which is annoying.

Edit: I set up CloudFlare in front of the server and there's now a working HTTPS version along with the HTTP version accessible from inside MOROS. This should also work when I'll use again the web server inside the OS. Thanks for prompting me to look into it!

Re:Writing an OS in Rust by bigstrat2003 on Saturday September 14, 2024 @05:55PM (#41543341)
There's nothing sensitive, therefore there is no reason to use TLS.
Re:Writing an OS in Rust by appendix-rock on Saturday September 14, 2024 @08:07PM (#41544078)
No! Stop! Why won’t this one die! MITMing is a two way street. I could intercept sensitive data, or I could shove something in that tricks the user (phishing, etc), exploits the user agent, and more!.

“You only need encryption for the sensitive stuff” is what we did, poorly, in the late ‘00s / early ‘10s, and it was rightfully proven to be a bad idea. There’s a reason why browsers treat HTTP the way they currently do, and it isn’t because they’ve been co-opted by Big Certificate Authority.

EDIT: and as the other commenter says, there are download links.

Re:Writing an OS in Rust by tcfhgj on Saturday September 14, 2024 @09:21PM (#41544423)
You don't need encryption to prevent something shoved into it without detection
Re:Writing an OS in Rust by XorNot on Saturday September 14, 2024 @11:37PM (#41545016)
No but we have no "httpv" protocol scheme to require signatures but not encryption

Which IMO has been a huge mistake since breaking caching proxies for networks because we want to prove authenticity and have to do secrecy as well has been quite silly.

Re:Writing an OS in Rust by aaronmdjones on Sunday September 15, 2024 @02:09AM (#41545566)
No, but you do need authentication, and TLS does both.
Re:Writing an OS in Rust by 0xFF0123 on Saturday September 14, 2024 @07:53PM (#41544012)
Other than the build and download links?
Re:Writing an OS in Rust by anta40 on Saturday September 14, 2024 @10:14PM (#41544676)
Whoa, looks very cool. So far, my favourite project is xv6, because:

- codebase is reasonably compact, can be understood in a few weeks

- can be built with standard GCC provided by package manager, no need to built a custom GCC from source

- has user space, too

Seems like your project also have those points checked. Bookmarked!

Re:Writing an OS in Rust by vinc on Sunday September 15, 2024 @02:52AM (#41545739)
Thanks! Compared to xv6, you will find some important pieces missing. For example, there's no multiprocessor support and no scheduler, only one process can run at any time.

I should also note that user space programs can do memory allocation via syscall, but I currently have an issue with the kernel memory that I probably need to remap higher in memory. So, most commands inside the OS are still executed from kernel space, although they use syscalls and everything as if they were user space programs. I'm having a lot of fun creating device files inspired by Plan9 to communicate with the kernel.

There's a lot of work yet to arrive at something that feels truly complete as an educational OS, but I'm hoping to get there eventually. I really like this project because I'm learning along the way all the time!

Your first point is one of my main goals: I want the whole OS, including user space programs, to fit inside one brain. I'm always trying to find ways to keep complexity low without compromising too much on performance.