Comment IT management, stress, and OpenBSD (Score 1) 114
There is one thing in which OpenBSD has the edge over EVERY other OS's in the world: the stress factor.
I'm rookie, ok. Most of all, I'm availability conscious and rather the anxious type. I guess I'm not alone.
Three days ago I gave OpenBSD a try. This OS is straight Unix. Configuration may be painfull at some stage, like disklabel creation. I guess more awaits me. I compiled Samba in, which is not audited and may suffer exploits and flaws. I'll certainly add other similar software in the future.
Why bother then, some will argue?
That's what is impressive with OpenBSD: network exploits, security holes, can only result of MY wrong doing. To my surprise, the thought is surprisingly conforting.
The thing is, I know I may be adding vulnerabilities which each service I add, but as I add services, I can read the related doc, learning IN TIME about the security issue, and learn AT THE SAME TIME what countermeasure I have to take.
I've added Samba, my next move is set the firewall accordingly.
The relief is so great that the unix "unfriendliness" of the systems appears light in comparison: being carefull is feasible and will be fully rewarded.
In summary:
The stress factor is all important but often neglected, especially in business. But the hidden costs inccured are probably high. OpenBSD may help reduce these costs, as it gives the following adventages:
More infos:
- BSD Today: A step-by-step journal of installing OpenBSD
- www.openbsd.org
- OpenBSD Explained
enjoy!
Raph
I'm rookie, ok. Most of all, I'm availability conscious and rather the anxious type. I guess I'm not alone.
Three days ago I gave OpenBSD a try. This OS is straight Unix. Configuration may be painfull at some stage, like disklabel creation. I guess more awaits me. I compiled Samba in, which is not audited and may suffer exploits and flaws. I'll certainly add other similar software in the future.
Why bother then, some will argue?
That's what is impressive with OpenBSD: network exploits, security holes, can only result of MY wrong doing. To my surprise, the thought is surprisingly conforting.
The thing is, I know I may be adding vulnerabilities which each service I add, but as I add services, I can read the related doc, learning IN TIME about the security issue, and learn AT THE SAME TIME what countermeasure I have to take.
I've added Samba, my next move is set the firewall accordingly.
The relief is so great that the unix "unfriendliness" of the systems appears light in comparison: being carefull is feasible and will be fully rewarded.
In summary:
The stress factor is all important but often neglected, especially in business. But the hidden costs inccured are probably high. OpenBSD may help reduce these costs, as it gives the following adventages:
- Less time spend closing hole(!), following bugtrack, upgrading faulty software, etc.
- You spend more time setting up your server, but as a reward you get increased preemptive security, strong knowledge of your system and by derivation, a stronger ability to deal quickly and efficiently with incidents.
- You are more confident, less subject to stress, so you think better.
- Everything you learn is standard stuff, which will be usefull everywhere you go. Conversely, you stop cloggering your brain with lists of distribution dependent problems, exploits, holes...
- You have more time to develop your system and educate users.
- Your boss can boast to his peer (and competitors) when they go offline while he doesn't. That's what you want, right?
- You live longer.
More infos:
- BSD Today: A step-by-step journal of installing OpenBSD
- www.openbsd.org
- OpenBSD Explained
enjoy!
Raph
