Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    What is release 2.3_1?

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    27 Posts 20 Posters 8.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      phil.davis
      last edited by

      @2chemlud:

      …would like to see some frequent updates for openSSL in the future ;-)

      https://www.openssl.org/news/secadv/20160503.txt

      Now that little updates of individual components can happen fairly easily, in some ways security updates for stuff like this could be done routinely, even if the particular security holes that are patched do not directly apply to pfSense use cases. Then people (or dumb security checking scripts) that check the version of these things will find it is up-to-date and be happy.

      Of course there are the overheads in doing this of:
      a) pfSense core people have to do a reasonable range of testing to avoid regressions.
      b) Firewall admins may not appreciate having a (even small) update every couple of weeks, when it is strictly not essential.

      As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
      If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

      1 Reply Last reply Reply Quote 0
      • C Offline
        cmb
        last edited by

        We can put out an update with much less of a test routine as in the past since testing can be limited to things that changed. But yeah one like openssl requires a lot more care than ntpd, since it touches a lot of things. The openssl fix is in 2.3.1 already. We're possibly releasing 2.3.1 soon enough that it'll be the first including it. If that's going to take a bit longer, we'll do a 2.3.0_2.

        1 Reply Last reply Reply Quote 0
        • P Offline
          phil.davis
          last edited by

          And when it gets to 2.4, to save confusion over the _1 _2 patches naming convention, it would be good to call it 2.4.0 - then every release has 3 numbers in it up front, and the patches add to the end - 2.4.0_1 …
          Thus version 3 (one day/year!) would be 3.0.0

          As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
          If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

          1 Reply Last reply Reply Quote 0
          • C Offline
            cmb
            last edited by

            @phil.davis:

            And when it gets to 2.4, to save confusion over the _1 _2 patches naming convention, it would be good to call it 2.4.0

            Definitely, it ends up being too confusing without the implied zero there.

            1 Reply Last reply Reply Quote 0
            • jahonixJ Offline
              jahonix
              last edited by

              2.3a, 2.3b would have been way easier to understand than 2.3_1 while working on 2.3.1
              But it's better than releasing an updated 2.x version without suffix which we already had as well…

              1 Reply Last reply Reply Quote 0
              • K Offline
                Kerat
                last edited by

                the new updating system is awesome!!!

                1 Reply Last reply Reply Quote 0
                • J Offline
                  javcasta
                  last edited by

                  @nima:

                  A system mail would be nice if a system or package update is available.

                  Hello.

                  It can be done simply with php:

                  Notifier package & platform updates via email.
                  https://www.javcasta.com/bounties/#notifier_package_plarform

                  Regards.

                  Javier Castañón
                  Técnico de comunicaciones, soporte y sistemas.

                  Mi web: https://javcasta.com/

                  Soporte scripting/pfSense https://javcasta.com/soporte/

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.