|
|
|
|
|
by ilyt
1270 days ago
|
|
Right but servers builtin in kernel are the worst of all cases. Not only you have service where (if not firewalled) anything can connect and try the luck sending shit to it, it is often integrated with many other systems inside the kernel so it increases effort to rewrite any of that. Protocol clients in kernel have far less problems, for one you only connect to defined endpoint so attacker just to start would need to MITM you, and it is usually smaller codebase than the server It is also usually stuff where you want to add new features relatively often and "upgrade kernel to use this new server feature" is not thing people like very much. Providing interfaces to make userspace implementations faster have far better payoff, generic "make disk access and shoving stuff between disk and network fast" will help any file serving demon, not just SMB (point which original Samba proves, as with new improvements it is currently faster than ksmbd) |
|