Announcement

Collapse
No announcement yet.

Nginx 1.18 Stable Released With Many Fixes, Improvements

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Nginx 1.18 Stable Released With Many Fixes, Improvements

    Phoronix: Nginx 1.18 Stable Released With Many Fixes, Improvements

    Nginx 1.18 is out this week as their newest stable branch succeeding the Nginx 1.16 series for this versatile HTTP server and reverse proxy / load balancer / HTTP cache / mail proxy...

    http://www.phoronix.com/scan.php?pag...-1.18-Released

  • #2
    Seeing as this thing is everywhere, it's not bad to see it improve. The minimum OpenSSL seems a tad old though.

    Comment


    • #3
      What happened with the patent and code steeling issue around nginx?

      Comment


      • #4
        Originally posted by Spam View Post
        What happened with the patent and code steeling issue around nginx?
        The criminal case was dropped (with a statement that they reserve the right to file a civil case). The general consensus is that the original filing was an attempted money grab, and that the evidence that is already known will not support a civil case even if filed in the future.

        Comment


        • #5
          Originally posted by bug77 View Post
          Seeing as this thing is everywhere, it's not bad to see it improve. The minimum OpenSSL seems a tad old though.
          Precisely because it is used in some many places the goal will be to try to support the oldest OpenSSL that provides the necessary functionally so that upgrade to the newer nginx does now also require all those sites to upgrade their OpenSSL version, and force a significant upgrade for other packages on the web server (some web server admins use the "if it ain't broke yet, I am not going to break it (upgrade it)" approach). If you need some newest features (TLS 1.3?) you may need to upgrade supporting packages (OpenSSL or BoringSSL?), but not everyone needs/wants the latest capabilities.

          Comment


          • #6
            Originally posted by CommunityMember View Post

            Precisely because it is used in some many places the goal will be to try to support the oldest OpenSSL that provides the necessary functionally so that upgrade to the newer nginx does now also require all those sites to upgrade their OpenSSL version, and force a significant upgrade for other packages on the web server (some web server admins use the "if it ain't broke yet, I am not going to break it (upgrade it)" approach). If you need some newest features (TLS 1.3?) you may need to upgrade supporting packages (OpenSSL or BoringSSL?), but not everyone needs/wants the latest capabilities.
            That may be, but OpenSSL 0.9.8 is from 2005. It predates heartbleed & co. Unless the actual version is a more recent 0.9.8 variant, but the official docs sure don't mention it.

            Comment


            • #7
              In other news, Caddyserver is nearing their 2.0 release. I've been using their release candidates for a few months now and I'm very impressed.

              Comment

              Working...
              X