OpenBSD Now Nine Years Old 60
NekkidBob writes "OpenBSD, my personal favorite *BSD, turns 9 years old today. And with only 1 remote hole in the default install, I'd say that is a pretty good acheivement. The first commit was at 16:36 MST on Saturday, October 14, 1995. Happy birthday OpenBSD!"
What can i say.... (Score:1)
Re:What can i say.... (Score:3, Interesting)
Hmm (Score:1)
Re:Hmm (Score:1)
Re:Hmm (Score:1)
Re:Hmm (Score:1)
Re:Hmm (Score:3, Insightful)
A similar attempt has been ongoing with the HURD kernel for at least the last decade.
Packaging attempts were made with FreeBSD and OpenBSD.
I don't know the status of the Debian/FreeBSD port but the Debian/OpenBSD port was abandoned when Andreas Schuldei, the maintainer of the port, realised
Re:Hmm (Score:3)
"He" does not understand that in context of licenses, they are very far appart. OpenBSD have replaced several GPL licensed utilities with a free alternative. They still use alot of GPL (LGPL) like the tool chain from the gcc project, but the spirit is there. Just witness the fork of Apache 1.3 and XFree86
Re:Hmm (Score:2)
I think you're thinking Debian GNU/NetBSD (Score:2, Informative)
http://www.debian.org/ports/netbsd/ [debian.org]
Re:Hmm (Score:1)
And yet he doesn't answer when asked about his finds: http://lists.debian.org/debian-bsd/2002/10/msg0006 3.html [debian.org]
But GNU is. (Score:1, Funny)
today is the fifteenth (Score:1)
Re:today is the fifteenth (Score:2)
The love of BSD (Score:2, Interesting)
Let the Birthday party begin!
David Ross
dross logged on
freenode.net - Join the #openbsd channel
And with only 1 remote hole in the default install (Score:1, Troll)
But, what good is the default install? Don't you want it to be doing something? It's suffered the same Apache/SSL/FTP/PHP errors as everyone else. I know if you search cert for openbsd you get lots of hits, so there are wholes in the applications.
Nothing as secure as a box unplugged in a closet!
Re:And with only 1 remote hole in the default inst (Score:3, Insightful)
Re:And with only 1 remote hole in the default inst (Score:3, Interesting)
I have, and do. But I favor freebsd for my servers, and linux for personal use. But for my work I use Solaris (with clustering).
I just find the comment amusing, soon as you add in server applications, you decrease the security.
Re:And with only 1 remote hole in the default inst (Score:1)
Re:And with only 1 remote hole in the default inst (Score:2)
Is this possible without invoking black magic? Windows 2000 might very well have some advanced features to harden it, but they are so inaccessible/hard to understand as to be useless.
Re:And with only 1 remote hole in the default inst (Score:5, Insightful)
No shit?!
The point with OpenBSD, is that it has so many active security mechanisms, that a [insert network daemon] exploit might allow a remote root on your FreeBSD, Solaris and Linux machines, but only result in a DoS of that particular service on OpenBSD.
Already we are not only seeing open source OS' take leafs out of OpenBSD's book, but also Microsoft and Sun.
The multitude of active and passive security measures in OpenBSD is very impressive.
Plus the point is, that an OS should be locked down from the initial install and then built on from there as the admin requires, not as the OS maintainers think you will require.
Presumptuous people who build operating systems, do not make secure operating systems.
Re:And with only 1 remote hole in the default inst (Score:2)
Re:And with only 1 remote hole in the default inst (Score:2)
There are people in the world who are objective and who form conclusions based upon evidence and experience. I know that when you hang out on slashdot too long it is easy to become convinced that everyone is biased, prejudiced, and an inflexible partisan on one side or the other of one of the various ideological/technological disputes.
The next time you read a critique, don't assume that the person making it has some kind
Re:And with only 1 remote hole in the default inst (Score:1, Informative)
first off, the FTP daemon is in the default and hasnt had holes. apache is also heavily modified and audited, and has also not had any remote root exploits as configured by default, not to mention its chrooted
second, most of the other security issues dont even matter because they are inapplicable due to propolice.
third, if youre going to make a comment about security on openbsd, you better know what your are talking about. noob.
Re:And with only 1 remote hole in the default inst (Score:3, Informative)
FTP is not on by default, so it doesn't count.
Anyways, that kind of comments like the grandparent post come from time to time from people that can't see the importance of a secure by default OS installation.
How much does it take to hack into any Windows box just installed and connected to Internet? Make the numbers. How about a Red Hat Linux?
With the "Secure by default" and the "Only one remote exploit ..." slogans OpenBSD is not claiming it is the most secure OS, but that you can be reasonably
Re:And with only 1 remote hole in the default inst (Score:2)
What? I never said no such thing. I said the comment was funny thats all. So stop throwing windows into the mix. My comment was, and is, a basic install unix type OS box are almost always secure, and yes even redhat. But a basic box by itself is of no use, its the applications which by default have the applications, thus the exploits.
The "Wind
Re:And with only 1 remote hole in the default inst (Score:1)
What? I never said no such thing.
I guess you mean "I never said such thing". From your first post:
But, what good is the default install? Don't you want it to be doing something? It's suffered the same Apache/SSL/FTP/PHP errors as everyone else. I know if you search cert for openbsd you get lots of hits, so there are wholes in the applications.
Then you can't see the importance of the security in the default install in OpenBSD.
I said the comment was funny thats all.
I fail to see where do
Re:And with only 1 remote hole in the default inst (Score:2, Insightful)
Re:And with only 1 remote hole in the default inst (Score:2, Insightful)
It depends what you're doing, doesn't it?
its the applications which by default have the applications, thus the exploits.
Not sure what you mean by "the applications which by default have the applications", but if you meant "the applications which by default have the holes" (or "wholes" as you call them), no they don't. Stop spewing nonsense and spend 5 minutes at openbsd.org and read about the auditing work that goes into many of the specific versions of the appli
Re:And with only 1 remote hole in the default inst (Score:4, Insightful)
this doesn't mean your final system won't have holes, but it means you're not already starting "in the hole"; it doesn't sound like much, and yet how many other systems out there can make this claim? OpenBSD isn't the end-all, be-all, it's just a good tool for your toolbox
Re:And with only 1 remote hole in the default inst (Score:5, Informative)
Drop a fresh OpenBSD installation into a hostile environment such as the internet.
Drop a fresh WindowsXP installation into the same environment.
You won't ask that question again.
Don't you want it to be doing something?
No I want it to do as little as possible. It is ready to serve when I say it is and no sooner. This lets you patch first and not everyone has the luxury of installing a box in a secure network.
It's suffered the same Apache/SSL/FTP/PHP errors as everyone else.
More or less, yes, the same problems. Thats why these services are off by default, to let you patch them first, and enable only what you need.
I know if you search cert for openbsd you get lots of hits, so there are wholes in the applications.
No one has ever suggested otherwise.
Re:And with only 1 remote hole in the default inst (Score:4, Insightful)
Fortunately, that's where you are wrong.
It's quite common to search through bugtraq or another security list, and find it in the list as the only OS "unaffected". Now, that's not always the case, but it's surprisingly common.
OpenBSD is more secure than other OSes, not just out of the box, but with major services enabled too... When you install Apache on Linux/FreeBSD, you just get the plain vanilla version. With OpenBSD, you get a version that has been audited by the team, and lots of changes have been made.
Plus, about a year ago, Propolice, W^X, and other protection measures have be included by OpenBSD, which does negate most bugs, and does protect your OTHER services against software bugs.
BTW, most of my machine have only SSHD enabled (which is one of a few services enabled by default), so the default install can be very useful for a great many things. SSH handles log-in, file transfer, plus port forwarding. So any other services can run on 127.0.0.1, and only be accesses remotely (via SSH) if you have an account.
Of course, but baring that, OpenBSD is a very good choice.
Re:And with only 1 remote hole in the default ... (Score:1)
generally speaking, operating systems are relatively secure out of the box,
its the shit you add to it, apache, php, sql, perl, ftp, etc...
that end up really being your headache.
in fact, i believe a study was done, (i don't remember where now though)
about ~90% of all unix and unix-like boxes "rooted", are done so under the ftp service/daemon.
it kinda makes people want to think
Re:one hole? (Score:4, Informative)
The point of OpenBSD is SANE defaults (i.e. not running telent, ftp, and rsh by default). Turning on Apache (bundled by default) is really simple, and because they've gone through and clobbered most buffer overflows and built everything with ProPolice, what were on other systems are root holes turn into non-events or program crashes (which can in theory be used to do a DoS, but that's a huge improvement).
Re:one hole? (Score:2)
The last time I installed OpenBSD it did have the OpenSSH daemon enabled by default and maybe some inetd services if I remember correctly. IMHO that is too much. Every service that is on by default is too much. Therefore I consider NetBSD the cleanest as it does not have a single server enabled by default.
Having services enabled by default is nothing to brag about.
That is my humble opinion.
Re:one hole? (Score:1)
The installation script now asks you if you want it enabled
Re:one hole? (Score:4, Informative)
Here's a ps ax from my primary DNS server (which is very busy).
# ps ax
PID TT STAT TIME COMMAND
1 ?? Is 0:01.11
5741 ?? Is 0:06.49 syslogd: [priv] (syslogd)
3517 ?? I 1:13.56 syslogd -a
24875 ?? Is 0:00.03 named: [priv] (named)
10792 ?? I 320:27.22 named
25379 ?? Is 0:00.25 inetd
12780 ?? Is 4:13.98
23171 ?? Is 11:22.04 sendmail: accepting connections (sendmail)
15125 ?? Is 0:06.28 ntpd: [priv] (ntpd)
9037 ?? I 9:36.04 ntpd: ntp engine (ntpd)
26494 ?? Is 5:11.57
10568 ?? Is 0:36.80 cron
8249 ?? Is 0:00.33 sshd: root@ttyp0 (sshd)
4537 a Is+ 0:00.05
32091 p0 Is 0:00.10 -sh (sh)
20044 p0 R+ 0:00.02 ps -ax
Here's a netstat -ss from that same machine
# netstat -ss
ip:
11272118 total packets received
12 with data size data length
6741 fragments received
6726 fragments dropped after timeout
7 packets reassembled ok
10332389 packets for this host
318009 packets for unknown/unsupported
###
Had to truncate because of some retarded junk filter.
Re:one hole? (Score:2)
16 processes: 2 running, 14 idle
CPU states: 0.0% user, 0.0% nice, 1.8% system, 0.0% interrupt, 98.2% idle
Memory: Real: 30M/55M act/tot Free: 189M Swap: 0K/250M used/tot
root login! (Score:1)
Aargghh!!! You logged in as root! :)
I've finally broken myself of that, even on single-purpose non-Internet-exposed machines. Bad habit I picked up from Windows... Broke down and started disabling ssh root login, now I have to su/sudo.
Re:one hole? (Score:4, Insightful)
You speak with such authority, for someone who obviously knows nothing about the subject.
OpenSSH has been ON by default at some stage after or including OpenBSD 2.6 and only recently has the option to disable it within the install script, become an option for users. That's about 5.5 years out of that 8.
The foundation of your rant is completely non-existent.
Nowdays, even if you do enable popular daemons, your typical worst case is likely to be a DoS instead of a remote root, thanks to OpenBSD.
I take, "Only one remote hole in the default install, in more than 8 years!", as a fact that is representative of the mindset of the developers behind the project, not as an absolute gauge of overall project security. Anyone who does or thinks that is what it is supposed to represent, is stupid.
Take that statement for what it is. Reading more into it is your problem.
Re:Does it count NetBSD history? (Score:1)
RTFF (Score:2)
Also, if you can't figure out an ftp install, you might be barking up the wrong tree.
Ahh yes, the joys of youth... (Score:2)
Some of the early 1980s were some fun times.
Though i can't decide whether computers were cool then, or if they sucked.
All Hail Theo and Crew (Score:2)
The world can sleep better tonight knowing Puff the Barbarian is on guard.
"Happy Birthday OpenBSD" modded down "flamebait" (Score:1)
I'm trying to understand the mechanics of this fellow's brain. I'll provide here all the possible explanations I can think of - since mine was indeed a three-word post, their number is actually quite small.
1) It's "Happy".
Maybe my wishing a "happy" birthday instead of a "fairly good birthday", or "decent birthday", sounded like an abuse to everybody in the world who was not particularly happy ("Hey! How dare you talk about happiness
...so... (Score:1)
but it thought... (Score:1)