When I was first learning Linux and personal system administration a dozen years ago, I was taught the importance of security. However, at the time it seemed something like the importance of knowing a fire drill. We all agreed that the threat was real, but at the same time it had the air of a bogey-man story: nebulous and unlikely. And so for a
(
Read more... )
Comments 8
Reply
I'm just sad that Debian, a Linux flavor that focuses so heavily on security, would ship such an insecure configuration of one of the most popular contemporary web-development thingies.
Reply
Even back in the early 2000's when I ran my own servers most of the traffic I got was script kiddies and the like hitting on known vulnerabilities, most of which Slackware didn't have. I did get rooted once, and fairly soon after moved over to commercial hosting in part of avoid this kind of thing.
Reply
On the other hand, I have to wonder how much that also has to do with the change in the computer ecosystem over the past few years. Linux used to be the free, personal, DIY way to be on the Internet. Now it's more of a professional server OS, and the free way to be online is to get a set of free-as-in-beer accounts on Gmail, Facebook, etc.
Reply
If this fails, I'll just bust up my operations as appropriate across a little cloud of hosts, and I bet I could end up doing everything I'd like that way; I don't _need_ a root account to e.g. install and run a Catalyst-based web application. (Working with the digital library of a certain security-conscious local university has made me more proficient at this. :) ) But it would still be kind of a drag.
Reply
Reply
2. The comment about the car insurance is strangely supporting of JMac's original point of an Internet gone wrong.
Reply
Leave a comment