You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to discuss about the feasibility of adopting the famous "three processes" model which is used for lots of OpenBSD services.
I'm not a developper, but if I understand correctly, the benefit of this model is having three specialized processes that you can very easily restrict with pledge/unveil, while with a single thread that does everything, you have to do some compromises for it to work correctly.
Thank you for the suggestion! I think it's a great idea. Unfortunately, I don't have much time for improvements these days, but when I do, I'll try to get around to it. 😃
P.S. Sorry about the delay! I'm on GitHub everyday and still it feels like sometimes I don't get notifications.
Hello,
I would like to discuss about the feasibility of adopting the famous "three processes" model which is used for lots of OpenBSD services.
I'm not a developper, but if I understand correctly, the benefit of this model is having three specialized processes that you can very easily restrict with pledge/unveil, while with a single thread that does everything, you have to do some compromises for it to work correctly.
Here is a skeleton example of an OpenBSD daemon for reference.
The text was updated successfully, but these errors were encountered: