OpenBSD 3.3 Released 348
An anonymous reader writes "OpenBSD 3.3 was released today, with many new features, including integration of the ProPolice stack protection technology, W^X ('write xor X') on sparc, alpha and hppa, privilege separated XFree86 and an incredible number of enhancements and stability improvements to the packet filter, pf, including address pools for reverse NAT/load balancing, ALTQ integration for network conditioning, and anchors/tables/spamd for spam tar-pitting. Information on the release can be found here and download sites are listed here. (Also, here's a handy way to speed up your DSL connection - prioritizing empty TCP ACKs and ToS low-delay traffic with OpenBSD 3.3's pf.)"
OpenBSD 3.3 Song (Score:5, Informative)
-dk
Re:OpenBSD 3.3 Song (Score:3, Informative)
-dk
Re:OpenBSD 3.3 Song (Score:2)
I remember a different more techno song about OpenBSD.
Re:OpenBSD 3.3 Song (Score:5, Informative)
Here are the tracks with my made-up genre categorization of them. I think 3.0 and 3.1 are superior to 3.2 and 3.3.
3.0 "E-Railed (OpenBSD Mix)" Genre: Electronica
3.1 "Systemagic" Genre: Germanic industrial
3.2 "Goldflipper" Genre: James Bond theme
3.3 "Puff the Barbarian" Genre: Fantasy metal
OpenBSD = Coordinated Innovation (Score:5, Insightful)
If anyone hasn't tried OpenBSD yet, give it a shot - you're certain to appreciate the quality that goes into it.
Re:OpenBSD = Coordinated Innovation (Score:4, Insightful)
"Here's some iron ore, build a truck"
I can vi ascii files, but getting X running was an absolute chore, it was reminiscent of Slackware back in the 1.4 kernel days.
Re:OpenBSD = Coordinated Innovation (Score:2, Insightful)
I dunno, I've always found it quite easy. You've got about 5 or so tgz files that it downloads (I always do ftp installs) and decompresses them. I find it simple and clean.
Re:OpenBSD = Coordinated Innovation (Score:5, Informative)
Maybe you should have checked out the FAQ on the website or man afterboot
I don't know what to tell you if you can't do that much without more hand-holding.
Re:OpenBSD = Coordinated Innovation (Score:3, Funny)
Re:OpenBSD = Coordinated Innovation (Score:2, Interesting)
Re:OpenBSD = Coordinated Innovation (Score:2)
Re:OpenBSD = Coordinated Innovation (Score:2, Informative)
X -configure
Edit XF86Config and add monitor refresh setting, wheel mouse tweaks, default color depth
startx
This method has worked great for me. YMMV
Re:OpenBSD = Coordinated Innovation (Score:4, Informative)
Re:OpenBSD = Coordinated Innovation (Score:2)
Re:OpenBSD = Coordinated Innovation (Score:2, Insightful)
However, there's a difference between being able to do things the hard way, and having no option other than to do things the hard way.
Re:OpenBSD = Coordinated Innovation (Score:3, Insightful)
"man afterboot" is hardly a common UNIX way of finding out about necessary post installation tasks. To expect everyone to know that it's there, even after reading every word of the FAQ, is assuming too much. It's all in the attitude. A simple "your answer can be found in 'man afterboot'" is much better than "I don't know what to tell you if you can't do
Re:OpenBSD = Coordinated Innovation (Score:5, Interesting)
There isn't much there to begin with when compared to FreeBSD or Linux because of this philosophy. While it's not exactly politically correct to say so within the OBSD community, it's sort of an accepted truism that 'less is more', and you're better serviced by one of the former two OSes if you're for ease of use and a desktop OS. GUIs and user friendliness = reams of unaudited code = lots of bugs. That said, the GOBIE project IS looking to overhaul the OpenBSD setup process, at least, so hopefully things will be easier for everybody in the future.
Personally, I came to OpenBSD three years ago after having used RedHat for only six months and having gotten my box owned *HARD* - while it took a bit to figure everything out for a relative *nix newb, I can vouch that the payoff is worth it if you're willing to invest the time into making sure you never get owned again (not that there are any 100% guarantees with any software).
--Ryv
Getting 0wn3d (Score:4, Informative)
Then once you are clean again, examine the saved files and try to figure out how they got in. Learn from your mistake and carry on.
Happened to me a couple of times, usually when I make a mistake in configuration or don't keep up with the errata. Yes I'd like to connect electrodes to the script kiddies testicles, but it really isn't something to get bent overly out of shape over either.
Re:Getting 0wn3d (Score:3, Funny)
It's a good job I stopped the Linux =2.4.19 ptrace kmod local root hole, or I'd have been rooted on Sunday morning (see my journal).
Ironically, the skript kiddie hasn't been too careful, and he has left the PHP shell unpassworded and unprotected on his system. Running a uname -a through it shows that he's running a vulnerable kernel. I now face a terrible internal struggle - do I play ethical and just email abuse@chello.nl agai
Re:Getting 0wn3d (Score:5, Insightful)
It's too easy to get on the wrong side of the law these days, and you might have a wrong target to boot. I wouldn't risk it.
Re:Getting 0wn3d (Score:4, Funny)
Speaking as a Chello.nl subscriber: Don't even bother. They let their members violate every little bit from the EULA, including the running of webservers, FTP servers, IRC server, other servers, NAT gateways, etcetera. And I'm talking from personal experience here ;)
Re:Getting 0wn3d (Score:2, Insightful)
Unless you spend all day chatting on IRC or playing UT2k3/NWN on your box and that is the best you can put it to use, having your system compromised can be very serious.
Personally, I use my computers for my online banking, my business billing/invoicing system, not to mention the fact that I have quite a bit of sensitive personal and business information stored in spread sheets and oo.org documents.
This type of thinking (getting hacked is no big deal, so I will be lazy about se
Re:OpenBSD = Coordinated Innovation (Score:5, Interesting)
Between
Also, the source where you will get information on OpenBSD (for example, setting up X) is VERY different from what you'd expect for Linux.
Namely, OpenBSD has EXCELLENT manual pages. Also, the online documentation is very helpful for new users, as it clearly explains the basics of the system, and where to start if you're unfamiliar with it.
Re:OpenBSD = Coordinated Innovation (Score:3, Interesting)
The man pages are excellent. The only place I've been bit is that the dclient man page doesn't mention that it runs a script in
Since the 3.2 rel
I miss the SysV init scripts. (Score:2)
As someone who is currently ditching redhat for openbsd, I don't care for rc.conf at all.
However, I am certainly looking forward to not upgrading my kernel/glibc every three months. My complaints are mostly cosmetic.
Re:OpenBSD = Coordinated Innovation (Score:5, Informative)
From the web site:
The main goal of the GOBIE is to add a graphical installation of the famous OS OpenBSD. This project has bee developped in the spirit of OpenBSD which means that the installation is as close as possible as the text one.
GOBIE wishes to add some value to the product by developping installation modules to known servers such as Bind, Sendmail, Inn, Apache...
Here are some screenshots [gobie.net] - looks pretty cool to me. The only downside to it is that the release is scheduled for July and thus not availabe yet, so keep your eyes open. It seems like a project that is worth supporting.
Re:OpenBSD = Coordinated Innovation (Score:3, Insightful)
They didn't have
man afterboot
then? (Incidentally one of the best man pages you'll ever read. Everyone should have one).
And did they not have xf86config ?
Seems unlikely, but then I have only ever used 2.8+ IIRC.
The biggest hurdle for most people is getting around the idea of BSD "slices." But it makes sense and there are good reasons they did it that way. The installer and help are very good, actually. I would have to say OpenBSD has some of the best docs of any system out there, period.
X Doesnt belong on OpenBSD (Score:2)
Trying to shoehorn it into that mode would defeat the whole idea of it being secure, as 'un-ceritifed' apps would break that faster then you can blink....
If you want a BSD desktop, go FBSD.. and keep OBSD on your server/firewall/etc where it belongs.....
Re:OpenBSD = Coordinated Innovation (Score:2)
Easier to use? Learn it and you will never look back. Seriously. Read the FAQ, man afterboot, there are some OpenBSD specific books coming out... I am pretty much finished with Linux (although Gentoo interests me for media/MAME console), I'm only keeping up with it for employment reasons.
Easier to install? OK, if you're not going to use the whole disk, then it can be trickier than Linux to install at first, but besides th
If Microsoft wants to steal... (Score:4, Funny)
Aside from maybe the esoteric trusted OSes (i.e. Trusted Solaris), is there really another "mainstream" OS people can just rely on for security?
Hell, Bill G oughtta just start waving $$$ in front of Theo and company until they all say "OK, that will do" and join MS to show them Redmond boys the Right Way (TM) to lock down an OS*!!!
* of course the Office team would no doubt open right back up any holes the new security-conscious OS team closed down...
Re:If Microsoft wants to steal... (Score:3, Insightful)
Bearing in mind that security is, code flaws aside, one side of a balance between security and user features, OpenBSD, from what I can tell, more than pays the price for its security in lack of features. For example, Outlook is notorious for its security flaws. Most of these seem to stem from all sorts of abilities to run code embedded in emails. Did MS coders do this because they were stupid and forgot not to code in this feature? No, they did it because it is indeed a feature, when not abused.
Re:If Microsoft wants to steal... (Score:2)
I wouldn't necessarily say that. If anything, OpenBSD shows you can be secure without a great deal of sacrifice, it just requires applying talent and effort (which the OpenBSD team has). Just look at PrivSep XFree86. You don't really lose anything by doing it that way, afaik. It just wasn't being done before, somebody needed to code it.
Will apple inherit this (Score:2)
when can I expect I get my security enhancements in OS X?
Re:Will apple inherit this (Score:4, Informative)
Of all the BSD's, NetBSD and OpenBSD are the most similar, and share the most code, primarily because OpenBSD forked from NetBSD not so long ago. FreeBSD has taken quite a different path to be more mainstream.
Improvements to OpenBSD should not be impossible to merge into FreeBSD/Darwin, but it's an easy or painless task either - not to mention that FreeBSD and Darwin are quite different. This isn't saying that a fair share of code isn't shared, indeed it is, but it's not a trivial task.
Re:Will apple inherit this (Score:2)
Also, the change to FreeBSD compatibility is recent. The userland
Re:Not at all... (Score:2)
And the piracy protection in XP is activation, not registration, registration is very different.
Argh! (Score:3, Funny)
and still no SMP =( (Score:4, Interesting)
Re:and still no SMP =( (Score:2, Funny)
Would be nice, but in the meantime (Score:2)
Firewall, Mail, and DNS I handle with OpenBSD (running Postfix and DJB's tinyDNS), and my actual website gets run on FreeBSD 5.0 in order to take advantage of SMP - a very, very stripped down FreeBSD, I might add. Looking at my loads, I'm considering setting up a secondary OpenBSD machine strictly for the apache processes, and
That isn't my site (Score:2)
Re:and still no SMP =( (Score:5, Insightful)
look [slashdot.org] at
Newer desktop systems are equal to the quad box minus the extra cache on the xeons.
So, IMHO SMP support is not a huge deal and should not be for most sub 1000 user companys.
Re:and still no SMP =( (Score:2)
RH 6.2 (Score:3, Interesting)
HAH! I know of *many* sites that use a RH 6.2 boxes for serving, and even some that use RH 5.x distros as well. Just because RH no longer rolls their own fixes doesn't mean that the distros have dried up. Many sysadmins would rather manually update the software on their servers than go thru the trouble of migrating to yet another distro.
There are also those that use a heavily locked down ancient distro for serving. Ap
Re:and still no SMP =( (Score:5, Informative)
In an SMP environment, auditing all applications and figuring out all race conditions and resource corruption is a nightmare. You never know when a programmer overlooked the fact that a signal handler and a thread could *actually* be running in parallel and cause a race condition.
Theo wants to avoid these pitfalls for now. Thus OpenBSD has no SMP support.
Incorporating SMP support in OpenBSD shouldn't be an issue, mainly because NetBSD from which its derived has had SMP for ages and FreeBSD has it too! The friggin' thing is how to be sure that sendmail's author imagined all parallel excution scenarios and has coded accordingly.
Trust me, SMP environments are bitch to work in and you should either have professional tools to work with or a really good imagination to work out all possible race conditions.
Re:and still no SMP =( (Score:2)
Are you sure about that?
If the OS is properly done, the userlevel applications shouldn't have to worry about if the box has multiple cpus or just one. If something works with one cpus and fails with multiple cpus, then either 1) the OS isn't doing it's job right or 2) there's some subtle timing bug in the (application) code that would probably eventually fail on the right s
Re:Wrong (Score:2)
In theory they can be interleved. In practice things are frequently not so random. For example when you call fork on a non-SMP system the parent process gets to use up it's time slice before the new child process gets it's first chance to run.
Re:and still no SMP =( (Score:2)
Re:and still no SMP =( (Score:5, Insightful)
Consider what OpenBSD excels at and consider these questions:
Does a firewall really need two 2GHz CPUs?
How about a router, modest fileserver, or e-mail server?
Considering the complexity that SMP would probably add to the kernel (race conditions, data integrity, etc.), it may be counter-productive towards the goal of uncompromising security.
For bigger servers (4 or more CPUs) just run Solaris, FreeBSD, or Linux behind OpenBSD-based infrastructure. I think this is a tasty compromise.
would be nice (Score:4, Informative)
Re:would be nice (Score:5, Insightful)
Or, you could add USB HID support to the RAMDISK kernel on a spare box, and cd
Re:would be nice (Score:2, Informative)
boot the kernel with -c (bsd.rd -c)
disable uhci
disable ohci
Install using USB keyboard (on KVM switch).
Eh? (Score:5, Informative)
Just to clarify that, W^X is not "write xor X", but "write xor execute". It's a new policy that OpenBSD uses to specify whether memory is writable or executable, but not both.
This helps prevent buffer overflows on the architectures that support it (sparc, sparc64, alpha, hppa) in that any memory that can be written to cannot be executable, and vice versa - so even if a buffer overflow succeeds in overwriting memory, that memory cannot be executed (or, the memory cannot be overwritten in the first place if it is executable).
Also note that W^X is also available on x86 in -current.
does *nix not allow self-modifying code? (Score:4, Funny)
Re:does *nix not allow self-modifying code? (Score:4, Interesting)
Last time I wrote this type of code was on Data General's AOS/VS (which pretty much dates it), and DG didn't approve of that kind of thing at all. It didn't stop my program from working, though.
any idea if it's ever done? (Score:2)
Re:any idea if it's ever done? (Score:5, Informative)
Re:any idea if it's ever done? (Score:2)
Needless to say, this kind of facility was never in the hands of COBOL programmers, for instance, but I wrote lots of self-modifying routines to link COBOL or FORTRAN programs run on diferent machines simultaneously. In those days, it was more or less expected that a decent sysprog should have no real difficulty with that.
Steve Ballmer's Comments on BSD (Score:3, Informative)
Re:Steve Ballmer's Comments on BSD (Score:2, Informative)
Only slashdot... (Score:3, Funny)
Oh WOW!
My prayers for the packet filter, pf, including address pools for reverse NAT/load balancing, ALTQ integration for network conditioning, and anchors/tables/spamd for spam tar-pitting have been answered!
Thanks OpenBSD! Thanks for the World!!
Re:Only slashdot... (Score:2)
OpenBSD just makes sense... (Score:5, Insightful)
Regarding various troll-slams on OpenBSD... I dunno, I'm using OpenBSD and it's great. Nowhere to go but up, as far as I'm concerned. FreeBSD and NetBSD don't have much of a value proposition in my book compared to mainstream Linux distros, but if you want a secure webserver (or network appliance) without having to patch the thing all the damn time, OpenBSD seems a heck of a lot better than any Linux variant.
That said, I'm not dogmatic about this; it's just the conclusion I've come to based on the evidence I've seen so far.
--LP
Re:OpenBSD just makes sense... (Score:3, Interesting)
While OpenBSD is certainly the leader in the security and frontline realm, the guys at FreeBSD really have a slew of interesting ideas as far as what directions they want to go in are.
Can't wait to see what the OpenBSD 3.4 release looks like, though. That's supposed to be an even bigger release than 3.3 -
Re:OpenBSD just makes sense... (Score:2)
This myth has to die or someone has to prove it, with recent versions of linux and bsd. There have been so many advances with linux (for instance after the mindcraft incident etc.) that I doubt it's true.
The current advances in linux can clearly be seen over at spec.org, linux with the tux webserver scales nearly linearly to 8 procs.
Re:OpenBSD just makes sense... (Score:2)
Re:OpenBSD just makes sense... (Score:3, Informative)
http://www.chromium.com/x15tech.html
PF FAQ (Score:5, Informative)
http://openbsd.org/faq/pf/index.html [openbsd.org]
Interesting feature - spamd (Score:5, Informative)
-- Probably questionable legality and ethics on that one, being a real tool in the battle against what some call 'free speech'.
Re:Interesting feature - spamd (Score:5, Insightful)
Probably 'Free Speech,' but the activity consumes the finite resources of a computer that costs the operator money in electricity, bandwidth, maintenance and access by customers and/or employees.
There is nothing about 'free speech' that allows one entity to force another to be the carrier or reciever of the idea or message.
Re:Interesting feature - spamd (Score:3, Insightful)
They are free to speak, we are free to not listen or to not pass their messages on.
Re:Interesting feature - spamd (Score:3, Insightful)
When "speech" becomes effectively a Denial of Service attack, freedom of speech ends, IMO.
Examples:
SPAM -- literally reducing peoples' ability to communicate effectively. This hurts individuals and businesses. The cost to the recipient is real.
Loud Music -- that bass pumping out of my asshole neighbor's house is not protected speech. It distrupts my family, my quality of life, my own attempts at speech, and is, like S
Re:Interesting feature - spamd (Score:2)
Re:Interesting feature - spamd (Score:2)
basically spamd is going to waste resources of open mail relays and spammers who spam directly from their computers. Besides bandwidth, how is anyone else in the world affected? If you get your e-mail from a mail server that is also an open relay, well than I say you got whats coming. Chances are that server will get blacklisted and you may not receive your mail due to other anti-spam solutions you use (if yo
Re:Interesting feature - spamd (Score:2)
ITYM "frea speach". HTH. HAND.
Google cache of the pf tip (Score:5, Informative)
Prioritizing empty TCP ACKs with pf and ALTQ [216.239.53.100]
Ahh damn (Score:5, Funny)
Re:Ahh damn (Score:2)
*BSD is Dying (Score:4, Funny)
Way to go!
AbiertoBSD (Score:2)
I've been waiting for this release for a number of months now and want to express my gratitude to the OpenBSD folks. Of course, that means buying a few more of their CDs [openbsd.org]. Heh, heh... Shameless support for my favorite OS. What's in their best interest is in the best interest of my computing environment, right? Good!
Now where is that post I wrote a few days ago about building a new distro called AbiertoBSD out of used car parts?
Prioritizing ACKs (Score:5, Interesting)
Damn, that business with the prioritizing ACKs sounds fantastic! I have the same setup as in their example (ADSL 512Kb down/128Kb up) and always have to put upload limits on filesharing programs so they only upload at maybe 11KB or 12KB per second, 'cos if I let them hit their full 16-ish KB/sec, the downloads choke and die.
I might have to salvage some crappy old box from work and see if I can't set it up as an OpenBSD gateway..
Linux traffich shaper here... (Score:5, Informative)
enjoy it!
Q.
Re:Linux traffich shaper here... (Score:3, Funny)
Show your support! (Score:4, Insightful)
Re:Why? (Score:5, Informative)
2. Stability. Like a rock. Even running the current branch, you will most likely not have any stability problems. Install, configure, and throw away the key. This is the first OS I've run that I can truthfully say is, besides any necessary patches, maintainence free.
3. BSD systems are much easier to maintain than Linux yet just as powerful as a full Unix. The ports system is well kept up and easy to use and the filesystem is much less cluttered than in Linux.
Very much worth a try if you have never used it.
Re:Why? (Score:5, Insightful)
FreeBSD is a close second. The reason you hear so little about FreeBSD's security is that there is no concept of the 'default install', and thus, there's no easy way to tell what FreeBSD's security record would be if you did the default install. But, if you choose the absolute minimum, and configure it similarly to OpenBSD (which is quite easy to do, make sendmail start only on the loopback, set the same defaults for SSH, etc). It's not as secure by default, because there is no default.
Moreover, anyone who installs services they don't need deserves to get hacked. Need a mail server? You're gonna get hit with the sendmail holes. Need SSH access? You're gonna get hit with the (1) OpenSSH hole. If you don't need the services, they shouldn't be enabled. You can mitigate the threat with firewalling (or hopefully, detaching it from the real internet), but chances are, the holes are going to be in the services you run and not in the OS itself.
(You could argue that systrace can limit a lot of otherwise horrific vulnerabilities: fair enough. So does chroot() and jail())
2. Stability. Like a rock. Even running the current branch, you will most likely not have any stability problems. Install, configure, and throw away the key. This is the first OS I've run that I can truthfully say is, besides any necessary patches, maintainence free.
FreeBSD. More stable and FASTER.
3. BSD systems are much easier to maintain than Linux yet just as powerful as a full Unix. The ports system is well kept up and easy to use and the filesystem is much less cluttered than in Linux.
I agree. 'make buildworld; make buildkernel; make installkernel; reboot ; make installworld' is pretty nice too.
Re:Why? (Score:2)
Not to mention in most linux distro's all the files in
Re:Why? (Score:2)
I will stick wiht the ports thank you.
Re:Why? (Score:2)
Re:Why? (Score:2, Informative)
How so? Are you going to tell me that *BSD can only run Windowmaker or something? Or does *BSD ship with a broken [k||x||g]dm?
In what way is it that FreeBSD and NetBSD are somehow less usable for a desktop compared with G
Re:fp (Score:2, Interesting)
...but to stay on topic, it sounds good, I will wait a week before even attempting to download it and throw it on a spare partition on my server. Quick question, is this ProPolice [ibm.com] by Hiroaki Etoh which is integrated into OpenBSD's 'system compiler' the same as the stack protector patch for GCC developed by Hiroaki Etoh at IBM [slashdot.org], as previously mentioned on /. concerning the new Trusted Debian 1
Re:pri TCP ACKs for linux patch? (Score:2, Informative)
Wonder Shaper.
Re:pri TCP ACKs for linux patch? (Score:3, Informative)
Re:High bandwidth whoring (Score:2, Informative)
Looking at the homepage helps.
Re:High bandwidth whoring (Score:5, Funny)
Re:tsarkon reports - openbsd - seirous issues. (Score:5, Informative)
Also, good luck getting a JDK/JRE to run here. HAHAHAHAHAHA. Fuckers.
I must have good karma.Re:(Linux|*BSD) Sucks! (*BSD|Linux) Rules! (Score:2)
Re:(Linux|*BSD) Sucks! (*BSD|Linux) Rules! (Score:2)
I didn't need that karma anyway.
Re:But is it ... (Score:2)
Rus
Re:Is the i386 port finally ELF? (Score:4, Informative)