So, I think I might make this more formal via email and announcement, but this has been taking up a large chunk of mental space. I desperately need help in developing HardenedBSD. While I'm so grateful for the many kind and encouraging words, there's still so many hours in a day.
I'm also very grateful we have one person who recently has stepped up, helping move the Pledge port ahead (and closer to full API compat.)
Please consider this post as unofficial. This is just "my thoughts as I've experienced them the past few days." If something comes from publicly posting my thoughts, all the better.
I'm wondering if anyone knows any folks interested in the kinds things we do at HardenedBSD. specifically looking for folks to mentor to do either osdev on hbsd itself, or in developing the censorship- and surveillance-resistent mesh network proof-of-concept.
i could budget a small amount for acquiring HaLow mesh gear. i don't have the budget for a laptop or other equipment. the only requirement is that all this R&D work be done on HardenedBSD.
When it comes to hardware acquisition, it's hard to know who to trust. I would like to make sure donated funds used properly and don't want to be scammed.
On the osdev side, I would like an implementation of random fd assignment. open(2) and friends usually just use the first available number, increasing until maxfd limit is hit.
i would like to change it to be less predictable, to a random search mode rather than incremental search.
This would help mitigate file descriptor reuse bugs.
Of course, we would collaborate via #Radicle for any development work.
One last thing: I should be explicit in that all this is unpaid volunteer work. I have never received payment for my work and don't intend to.
I understand that a large portion of volunteer work fizzles out or doesn't work out. That's fine. I would just expect return to the HardenedBSD Foundation of any procured hardware.
#HardenedBSD #infosec #osdev
I'm also very grateful we have one person who recently has stepped up, helping move the Pledge port ahead (and closer to full API compat.)
Please consider this post as unofficial. This is just "my thoughts as I've experienced them the past few days." If something comes from publicly posting my thoughts, all the better.
I'm wondering if anyone knows any folks interested in the kinds things we do at HardenedBSD. specifically looking for folks to mentor to do either osdev on hbsd itself, or in developing the censorship- and surveillance-resistent mesh network proof-of-concept.
i could budget a small amount for acquiring HaLow mesh gear. i don't have the budget for a laptop or other equipment. the only requirement is that all this R&D work be done on HardenedBSD.
When it comes to hardware acquisition, it's hard to know who to trust. I would like to make sure donated funds used properly and don't want to be scammed.
On the osdev side, I would like an implementation of random fd assignment. open(2) and friends usually just use the first available number, increasing until maxfd limit is hit.
i would like to change it to be less predictable, to a random search mode rather than incremental search.
This would help mitigate file descriptor reuse bugs.
Of course, we would collaborate via #Radicle for any development work.
One last thing: I should be explicit in that all this is unpaid volunteer work. I have never received payment for my work and don't intend to.
I understand that a large portion of volunteer work fizzles out or doesn't work out. That's fine. I would just expect return to the HardenedBSD Foundation of any procured hardware.
#HardenedBSD #infosec #osdev