6 ms·
Apache Removed from OpenBSD Base
- midas007 13y agoThis is a good thing. Apache is a swiss-army chainsaw of last-resort, not a minimal webserver.
- muppetman 13y agoApache is very modular. You enable what you need. Apache's biggest problem is that it isn't cool and hip anymore. It's config file is too easy to understand. Good { thing we = have; nginx; } Phew!
- tiquorsj 13y agoIt does have too easy of a config file. Who needs per directory config anyway? Or the ability to create redirects without a restart? I love nginx, but it has some flaws. The reality is it just has different flaws and strengths than Apache.
- bluefinity 13y agoYou can do per-directory config in nginx with the location block, it's just that you just can't put the config inside the directory itself and have nginx automatically load it. You can tell nginx to reload its configuration without restarting the entire server process by running "sudo /etc/init.d/nginx reload", or on ubuntu "sudo service nginx reload".
- twic 13y ago'service' is not just on Ubuntu - i believe it started life on Red Hat, and has now spread everywhere. Including FreeBSD: http://www.freebsd.org/cgi/man.cgi?query=service&sektion=8 http://www.freebsd.org/cgi/man.cgi?query=service&sektion=8
- bluefinity 13y agoOh, I thought it was part of upstart for some reason. Thanks for the the clarification.
- mercurial 13y agoI find the lack of dynamically loaded modules more aggravating, personally. Having to recompile and optionally repackage the damn thing because you need a module not included in the base nginx is a pain.
- midas007 13y agoI <3 nginx and apache. Tech is a toolbox. Pick the closest tool for the job. Per directory config is extremely beneficial for static hosting / VPS, but sketchy to get the security of values just right.
- _ak 13y agoNo, Apache's biggest problem is its architecture that limits quite a few things you can do. Case in point: the farce around mpm_event. It took ages to implement it to solve a central issue Apache always had (i.e. that it could be DoS'd by slow but long-living connections), and even now, it's not exactly in a great state, compared to nginx's async I/O internals.
- liveoneggs 13y agompm_event in 2.4 is quite fast and let's you keep all of your terrible mod_rewrite hacks in place. :)
- reitzensteinm 13y agoSounds like it's time for an anecdote! In 2008, my web site saw some decent traffic, and I was stuck in a spiral of buying more and more expensive servers to keep up with the demand. Some of the media files were large, and slow downloads would tie up a thread, and corresponding chunk of memory. I spent a long time working through the documentation that was available at the time, and I couldn't get anything to work stably with Django. Then I found a guide for lighttpd, and was floored when the resources used by my web server dropped to single digits. Much later, I'd learn that even saturating a gigabit pipe with just html/css/image traffic ran fine. Nginx has since replaced lighttpd, since the latter doesn't seem to be well maintained these days. As I understand it, Apache now is capable of high performance, but once bitten twice shy. The whole thing just seemed to be a big, bloated mess to me. Like you can do everything imaginable, except what you actually want to do. I couldn't imagine a feature that would exist to convince me to move back. I expect quite a few web developers are in the same boat. Your criticism of the config file is nonsensical. I'd use nginx with Apache style configuration over the inverse in a heart beat - though I disagree it would be an improvement.
- midas007 13y agoI like servers that work reliably so the "pager" doesn't go off in the middle of the night nor get calls as to why our service is down.
- __david__ 13y ago> Apache's biggest problem is that it isn't cool and hip anymore. It's config file is too easy to understand. Yeah, mod_rewrite sure is the epitome of a readable config file syntax. Why have one or two simple to understand "if" statements when you could have a pile of incomprehensible regexps with random one letter control flow flags? Simple. Ha.
- midas007 13y agoBikeshedding on config syntax isn't a valid critique. Apache uses tons of memory regardless of which worker model is used. Nginx is reliable and stable, we've never had memory leaks or weird shit happen. This is why it's often uses as a front-end reverse proxy. More often, nginx is put out in front of apache where other dependencies require it (dav svn).
- clarry 13y agoThe fork of Apache 1.3 that OpenBSD had wasn't really that big. EDIT: The C source files and headers under src/usr.sbin/httpd are about 100k lines. Under src/usr.sbin/nginx you have closer to 170k lines. Of course this isn't exactly apples to apples comparison as both have optional modules and at least nginx has some OS-specific code. In any case though, it is really hard to argue that nginx is "light, small, and fast" while httpd is a bloated swiss army chainsaw with a kitten sink...
- dtech 13y agoCode size is in almost no way an indicator of performance or bloat. Ik can write a program that will use 100% CPU in about 10 LOC, while there can be very well-optimized pieces of software can be thousands to millions LOC. e.g. the Quake 3 engine is probably as well optimized as you can make it and is about 300K LOC: https://github.com/id-Software/Quake-III-Arena https://github.com/id-Software/Quake-III-Arena
- clarry 13y agoIn my book bloat and performance are two entirely different things, and I think there is a strong correlation between code size and bloat. I agree about highly optimized code being typically larger than the simpler alternative. Now nginx has interesting optimizations in some places (e.g. the http parser), but if you read the code, it's not like 90% of the code in nginx is there due to optimization. I'd like to add that from an OpenBSD perspective, excess optimizations would no doubt be considered bloat as well. One of the goals is that the code is clean, correct, and secure. I know for a fact that the developers are not going to carefully audit and maintain millions of lines of micro-optimizations. What these might get you is a tick in a hypothetical feature checklist ("performance"). But if another daemon does the job and performs well enough, then that feature is unneeded complexity, hence bloat. Not something you want to include in what aims to be the world's most secure general purpose operating system.
- BorisMelnik 13y agocan I ask why? I am not an openbsd guy obviously but know httpd is popular. Is it because adding it to base install adds too many security concerns?
- throwaway2048 13y agoIt is being replaced by Nginx
- danieldk 13y agoIt's the base system, so it makes more sense to include a small, fast, and secure HTTP server than one that includes everything and the kitchen sink. Note that it's still easy to install Apache from the OpenBSD ports.
- mrweasel 13y agoOpenBSD forked Apache 1.3, when the Apache 2.0 license was introduced. One argument could be that maintaining, patch and extend a web server on top of writing an operating system is to much work, especially if there's a better alternative, with a license you can accept. Including a web server isn't necessarily a security concern, it's not running by default. The advantages is that there's a web server included, with privsep, chrooting and a sane default configuration.
- rbanffy 13y agoWhat was the incompatibility?
- ef47d35620c1 13y agoThe incompatibility is with their beliefs, it's not technical. You can get Apache 2 in ports and packages. They disagre with the license, so it is not acceptable to them in base. It's the same reason they ship an ancient GCC in base, but once again, the newer ones are in ports. What they include in base OpenBSD is very special to them.
- riffraff 13y ago
- greatsuccess 13y agoAlthough Im not an nginx fanboy, I think Apache needs to get out of the way. It's incredibly poorly documented, and in general a pain in the ass. It served us well. time to move on, perhaps beyond nginx at some point in the near future.
- SwellJoe 13y agoWhile I understand that if the choice were between the OpenBSD fork of Apache and nginx the only sane choice would be nginx (the OpenBSD fork is silly). But, I see people making the argument that nginx is "more secure", which would fit into the OpenBSD mindset. But, the reality is that nginx and Apache both have imperfect security records; Apache is pretty damned good on the security front and has been for a decade or more. Also, nginx makes it much easier for a sysadmin to screw up their security...including with some example configurations that are commonly found floating around on the web.
- tobiasu 13y agoAha, "silly". I see your comment is full of arguments why this was the case all these years. Most Apache security issues didn't affect or had lesser impact on OpenBSDs fork. The only thing silly here is your opinion.
- SwellJoe 13y agoThe OpenBSD fork was ancient. The only people using it were those who didn't actually need a modern web server...which is to say, not even OpenBSD users were using it, if they were using their OpenBSD server for serious web service. While I understand the motivation behind it, I believe it would be silly to build a web service on top of an effectively 15 year old version of Apache (1.3 was first released in 1998 and was EOL, even for security releases, years ago). What is also silly is for a project that has so few serious developers to take on a project as massive as maintaining a fork of a project as large as Apache. When Apache had security issues that didn't affect the OpenBSD fork it was often because the OpenBSD fork didn't have the module in question (most security issues in Apache in the past decade have been in modules, often not frequently used ones). People not using those modules wouldn't have had those security issues, and people using those modules on OpenBSD (after building from source to get those modules and a modern version of Apache) would have also been affected. I'll admit that there is a certain charm to software that has few bugs because it does very little, but Apache is what it is because people need it to be those things. It is certainly not through incompetence. So, my opinion may be silly. But, it is not unconsidered. I've thought a lot about web service for the past 15 years, as it's a core part of my business. I could very well be wrong. Maybe OpenBSD would have been even less successful for web service had they opted to include a modern version of Apache. (And, before you say "popularity isn't a measure of being right", I will point out that no matter how secure software is, it is useless if no one uses it.)
- clarry 13y agoIn somewhat related news, OpenSMTPD finally replaced sendmail as the default mailer on OpenBSD. http://undeadly.org/cgi?action=article&sid=20140313052817 http://undeadly.org/cgi?action=article&sid=20140313052817 http://www.opensmtpd.org/ http://www.opensmtpd.org/
- bananas 13y agoThis is medium news. I'd rather use postfix. There's a ton of stuff missing from opensmtpd at the moment. Recently it had some serious crashing bugs when pipes were getting severed between the various privsep processes as well. It's getting there but it'll be a while yet before it should be in production on anything than really simple single nodes as a relay/local delivery.
- hosay123 13y agoNote this is about OpenBSD dropping support for OpenBSD's own fork of the skanky old Apache 1.3 line, which hasn't been officially developed in aeons, and no official security updates since 2010. The title implies some vote of no confidence by the OpenBSD team regarding Apache, when in actual fact they're just cleaning up their own mess, due to objecting to an earlier licensing change in the 2.x line.
- clarry 13y ago> The title implies some vote of no confidence by the OpenBSD team regarding Apache No it doesn't. It says what it says: Apache was removed from base. Now that there is a reasonable alternative with an acceptable license, it is time to move on. > when in actual fact they're just cleaning up their own mess You choice of words sure reeks of negativity towards the project. The fact is, skanky old Apache 1.3 has served the project well for a long long time, and it has had a good track record as far as security goes. Keep in mind that code in the base system has been audited, patched and maintained by the project.
- hosay123 13y agoSo I can see this getting boring pretty fast, but whatever.. on reading the title I wondered "why!", and on reading the article I find a recommendation for nginx. The reason for this appears to be entirely due to licensing in modern (and more comparable) versions of Apache 2.x than anything technical. The article does not make that clear at all. Apologies if you read so much negativity into my choice of words, it wasn't meant as an attack on OpenBSD, forking unmaintained software, or whatever else, just intended to point out a correction in the way probably half or more of readers will interpret the article – as some kind of indication that Nginx is technically somehow better than Apache
- protomyth 13y agoIts not entirely due to licensing. OpenBSD has security patches to Apache that weren't accepted plus the license change. OpenBSD has been maintaining their own branch until the switch.
- herokusaki 13y agoHow good is OpenBSD's USB support on recent motherboards? A USB bug that affects motherboards with Intel chipsets in FreeBSD 9.2-RELEASE makes me think of switching; it hit print servers bad.
- clarry 13y agoI've had mixed results, though my sample set is small, and I can't say for certain that the problems I've had are a software issue. Also, there have been some recent cleanups and fixes in the USB stack that I have not tried yet. For these, you need to grab a -current snapshot or wait for 5.5. Note that the xhci work is post 5.5. Your best bet is to find some spare hardware and give it a try. I wouldn't switch a production box over before that.
- profquail 13y agoHave you tried 9-STABLE to see if the xhci bug is fixed there? It looks like some patches were committed for it, but not until after the change freeze for 9.2-RELEASE: http://www.freebsd.org/cgi/query-pr.cgi?pr=181159&cat= http://www.freebsd.org/cgi/query-pr.cgi?pr=181159&cat= If the problem is fixed in 9-STABLE, but you're only deploying RELEASE builds, 9.3-RELEASE should be available in a few months: http://www.freebsd.org/releases/9.3R/schedule.html http://www.freebsd.org/releases/9.3R/schedule.html
- herokusaki 13y agoNot sure if it's in STABLE already but I was aware of the patch. We have rolled back to 9.1-RELEASE for now and will wait for 9.3-RELEASE.