The Apache Haus Forum

Advanced search  

News:

Welcome to Apache Haus Distribution Forum

Pages: [1] 2 3 ... 10
 1 
 on: July 14, 2018, 08:09:38 PM 
Started by Gregg - Last post by Gregg
Announcing the release of Apache 2.4.34

This version is mainly a bug fix version.

This release includes:
APR Version:        1.6.3
APU Version:        1.6.1
Brotli Version:    1.0.5
Jansson Version:    2.11
Libcurl Version:   7.60.0
LibXML2 Version:    2.9.8
LUA Version:        5.1.5
NGHTTP2 Version:    1.32.0
OpenSSL Version:    1.0.2o, 1.1.0h or LibreSSL 2.7.4
PCRE Version:       8.42
SQLite3 Version:    3.24.0
ZLib Version:       1.2.10

You can get your copy of the new Apache HTTP Server from our download page.

Change Log for Apache 2.4.34

 2 
 on: June 30, 2018, 08:08:49 PM 
Started by Gregg - Last post by Gregg
IIRC 1.3.9 was the first really good version.

Quote from: mario
I confess that I still miss the VC6, it ran on every windows computer without installing anything. Plug the USB stick or copy the files and one of my friends had a running apache on their computer for the next LAN party. Safer than open the windows share.

I remember showing you why I liked it so much that day during your first visit ... it's utter speed.


 3 
 on: June 30, 2018, 07:49:45 PM 
Started by Gregg - Last post by Gregg
I know Montana was first to put something into effect at the beginning of the year but I think that was just data the ISPs collect. After the Facebook fiasco I'm sure it will be amended to include any entity that collects data. Most states are in the process of doing the same since our government doesn't seem willing.

Could this be the beginning of the end for this type of collecting, tabulating and selling data? One can only hope.

https://www.theregister.co.uk/2018/06/29/california_data_privacy_law/

In this article it mentions the way it came to be. It also mentions that it can be dismantled because it was not due to the peoples vote. That said, if they tamper with it to neuter it, it will end up on the ballot, it will be passed by the voters and all the legislators will most likely be voted out of office.

So to the many slimy politicians in Sacramento, just try and neuter it. :D

 4 
 on: June 25, 2018, 10:00:31 AM 
Started by Gregg - Last post by mario
I can't say which version number it was for me. But I know it had only one digit after the three. Maybe 1.3.6 or 1.3.9.

IIRC 1.3.17 was the first one with an msi installer. One with the sources and one jsut the binaries. I wanted a portable version or at least a zip file. I was never able to open the msi files to extract the files. After some time I figured out how the change the path in the config that I was able to run it with from a USB strick any drive letter on any computer.
The msi was one of the reasons I found frist XAMPP which was too bloated and then Apache Lounge.

I confess that I still miss the VC6, it ran on every windows computer without installing anything. Plug the USB stick or copy the files and one of my friends had a running apache on their computer for the next LAN party. Safer than open the windows share.

 5 
 on: June 20, 2018, 06:00:40 PM 
Started by Gregg - Last post by Gregg
It was 20 years ago today that I picked up my first copy of Apache for Windows. Apache 1.3.0 was the first version to run on Windows and was released on June 6, 1998.

 6 
 on: May 14, 2018, 02:19:59 PM 
Started by mario - Last post by mario
The next version can be found here https://www.apachelounge.com/viewtopic.php?p=36843#36843

 7 
 on: May 09, 2018, 06:42:21 PM 
Started by Gregg - Last post by Gregg
Announcing the release of Apache 2.4.29 with LibreSSL 2.7.3

Bug fix release for LibreSSL.

This release includes:
APR Version:        1.6.3
APU Version:        1.6.1
Brotli Version:    1.0.3
Expat Version:      2.2.5
LUA Version:        5.1.5
LibreSSL Version:    2.7.2
LibXML2 Version:    2.9.7
NGHTTP2 Version:    1.28.0
PCRE Version:       8.41
SQLite3 Version:    3.21.0
ZLib Version:       1.2.10
mod_http2 Version:  1.10.12

LibreSSL changes can be viewed HERE
You can get your copy from our download page.

 8 
 on: April 24, 2018, 09:12:17 PM 
Started by mario - Last post by mario
We have a new download mirror in the US. You will see it on our download page.  Happy downloading

 9 
 on: April 09, 2018, 06:52:04 PM 
Started by long76 - Last post by Gregg
Yes I know this is a moldy old thread but it's still relevant to this day so here's the latest news on Apache & TLS 1.3.

IETF: The IETF accepted Draft 28 of TLS 1.3 spec, so that draft will become the official RFC.

Apache side: TLS/1.3 has been added to trunk where 2.5/2.6 will be spawned from and it works for me on the Firefox Nightly. It supposedly works on some version of Chrome but I will not install it on any of my computers so I cannot confirm that.

That said it will be interesting to see when and how we get it in 2.4 because of how SSLCipherSuite had to be changed to accommodate tls1.3.

Old way:
SSLCipherSuite list:of:ciphers:in:order:of:admins:preference

New Way:
SSLCipherSuite SSL list:of:ciphers:up:to:tls1.2
SSLCipherSuite TLSv1.3 list:of:only:tls1.3:ciphers

If it's not done this way, it falls back to OpenSSL/LibreSSL's defaults. So TLS 1.3 will somewhat break our 2.4 SSL configs (which is a no no). I ran into this when testing. It still worked, still got tls1.3 on FF nightly and tls1.2 on others (current FF ESR, Palemoon (what I use everyday) and Vivaldy. But I had no control over the cipher order.

Good news is there's not a huge list of TLS1.3 ciphers and even though Palemoon & FF ESR support the top 3 ciphers (TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256 & TLS_AES_128_GCM_SHA256), they must be using and older draft of the RFC. So as things stand, there's no rush in my opinion until at least it goes into a FF stable release.

Edit: And OpenSSL 1.1.1 or LibreSSL 2.8 have to be releast as well.

 10 
 on: April 09, 2018, 05:25:13 PM 
Started by APleger - Last post by Gregg
You can usually but in my case they will tell me I have to get a business package for a lot more $$$.

So since I currently have to manually do it via TXT records in DNS anyway, I'm now getting wildcard cert (now that they're available) which you must do manually via DNS. My first wildcard expires mid June.

Pages: [1] 2 3 ... 10