| |||||||||||||
|
| |||||||||||||
Poettering: Rethinking PID 1Poettering: Rethinking PID 1Posted May 9, 2010 9:53 UTC (Sun) by nix (subscriber, #2304)In reply to: Poettering: Rethinking PID 1 by foom Parent article: Poettering: Rethinking PID 1
So now locate(1) has to grow network-handling code and suddenly becomes a security target as a result and has to deal with spoofing, malicious network services and so on, where before it was only as much a target as everything that reads the filesystem and command-line (and even *that* vulnerability surface has had a security hole or two in the past).
No thank you.
(Log in to post comments)
Poettering: Rethinking PID 1 Posted May 10, 2010 1:35 UTC (Mon) by foom (subscriber, #14868) [Link]
I can see how you might not find the feature valuable. But a network service is really the only sane way to implement search on a network share.
And security shouldn't be a huge deal -- you only need expose it to the users you're exporting the filesystem to, anyhow.
|
|
||||||||||||