Review: CentOS: Red Hat Enterprise Linux, Minus Red Hat
|
|
|
Comments (2)
One of the things going in Linux's favor at the moment is that stuff like this makes exploiting it wildly difficult. Granted, it also makes deploying network services a bit more painful.
If you have to deply a network service, you should have taken all of the time needed to understand _all_ of the implications -- not just some lame dialog box that says "enable this service for me". Opening a firewall port or two to make it happen is par for the course.
We're within weeks of a total Windows network service melt-down, I believe. It's unfortunate, but highly likely. And Longhorn is still nowhere in sight.
If you have to deply a network service, you should have taken all of the time needed to understand _all_ of the implications -- not just some lame dialog box that says "enable this service for me". Opening a firewall port or two to make it happen is par for the course.
We're within weeks of a total Windows network service melt-down, I believe. It's unfortunate, but highly likely. And Longhorn is still nowhere in sight.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

Granted, a local user could possibly exploit one of the services. And if a cracker does get in through sshd, he might be able to exploit a service to escalate his privileges. But the implication that these services could be exploited remotely is as incorrect as ever.