News for hackers. Stuff that matters.
Re:Libressl.org is running apache1 by byroot on Thursday April 24, 2014 @10:28PM (#7644416)
I don't know much about OpenBSD but I know that they upgraded to Apache 2.X only very recently (1 year max IIRC) and it seems that they still maintain the 1.x version: http://openports.se/www/apache-httpd-openbsd
Re:Libressl.org is running apache1 by borando on Thursday April 24, 2014 @10:45PM (#7644480)
OpenBSD did not upgrade to 2.X. You're talking about ports, which are separate from the base operating system. For accurate information about OpenBSD, right now, check:

http://www.openbsd.org/55.html

Regarding ports, they're basically a compilation build system that complements binary packages (which OpenBSD also has) for 3rd party software not installed with the base system . See:

http://www.openbsd.org/faq/faq15.html#Ports

Re:Libressl.org is running apache1 by byroot on Thursday April 24, 2014 @10:52PM (#7644491)
My bad. So OpenBSD included Apache will still be 1.3 even in the upcoming 5.5. (along a more modern nginx)

Thanks for the info.

Re:Libressl.org is running apache1 by mrmondo on Thursday April 24, 2014 @10:39PM (#7644459)
I had someone describe the OpenBSD fork as 'FrankenApache', After they forked it, they clearly struggled to maintain and keep it updated.
Re:Libressl.org is running apache1 by copergi on Thursday April 24, 2014 @11:31PM (#7644612)
That someone was mistaken. How exactly do you think they "struggled to maintain" a fork of software that was barely active in the first place? How does "apache but chrooted by default" constitute "frankenapache" exactly? Given that their struggling was so clear to you, could you point me to something that would make it clear to the rest of us?