Announcement

Collapse
No announcement yet.

Kodi-Powered LibreELEC 8.2 Released

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

  • Kodi-Powered LibreELEC 8.2 Released

    Phoronix: Kodi-Powered LibreELEC 8.2 Released

    There's a new release of LibreELEC, the Linux distribution focused on delivering a premiere HTPC/multimedia experience by being built around the Kodi HTPC software...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Typo:

    Originally posted by phoronix View Post
    while bundlding the latest Kodi release,

    Comment


    • #3
      I'm wondering why they switched from LibreSSL to OpenSSL

      Comment


      • #4
        Originally posted by profoundWHALE View Post
        I'm wondering why they switched from LibreSSL to OpenSSL
        because of the y2k38 bug on 32bit platforms that's not going to be "fixed" in libressl

        EDIT: to be clear: libressl fails to validate notAfter for root CAs with validity beyond year 2038. and that's in fact not a libressl bug (as libressl is doing the right thing - it refuses to deal with those 32 bit time_t values)
        Last edited by stefansaraev; 28 October 2017, 06:21 PM.

        Comment


        • #5
          Originally posted by stefansaraev View Post

          because of the y2k38 bug on 32bit platforms that's not going to be "fixed" in libressl

          EDIT: to be clear: libressl fails to validate notAfter for root CAs with validity beyond year 2038. and that's in fact not a libressl bug (as libressl is doing the right thing - it refuses to deal with those 32 bit time_t values)
          I must be missing something here, but it can't validate expiration dates past 2038, how is that not a LibreSSL bug?

          Also, a distro with Libre in its name and Nvidia driver. Take that, you open-source die-hards

          Comment


          • #6
            Originally posted by bug77 View Post

            I must be missing something here, but it can't validate expiration dates past 2038, how is that not a LibreSSL bug?
            As said, libressl doing the right thing, but I wont argue with you, here some background:

            Since version 2.3.x (noticed that first when LibreELEC bumped version in April 2016), LibreSSL has a Year 2038 problem with certificate verification, to validate notAfter field, it used to work fin...



            Originally posted by bug77 View Post
            Also, a distro with Libre in its name and Nvidia driver. Take that, you open-source die-hards
            why do you think a project that ships nvidia driver sould not be allowed to use "Libre" in it's name?

            Comment


            • #7
              Originally posted by stefansaraev View Post
              why do you think a project that ships nvidia driver sould not be allowed to use "Libre" in it's name?
              Because NVIDIA is evil.

              More seriously, "libre" name is usually used by blob-free programs or firmwares, while "open" is just opensource (that can have blobs or not).

              So it looks strange that a "Libre" program is shipping blobs. But he didn't say anything about allowing/not allowing projects to use "libre" wherever they want.

              Comment


              • #8
                Originally posted by starshipeleven View Post
                Because NVIDIA is evil.

                More seriously, "libre" name is usually used by blob-free programs or firmwares, while "open" is just opensource (that can have blobs or not).

                So it looks strange that a "Libre" program is shipping blobs. But he didn't say anything about allowing/not allowing projects to use "libre" wherever they want.
                .. but not always. "libre" does not mean "blob-free"

                LibreELEC was born as a fork of OpenELEC. they never promised a blob-free linux distro.

                Comment


                • #9
                  offtopic: btw, your beloved intel requires non-free blobs for their gpus. and wireless... your beloved amd requires non-free blobs too

                  Comment


                  • #10
                    Originally posted by stefansaraev View Post
                    .. but not always. "libre" does not mean "blob-free"
                    Stallman begs to differ: https://www.gnu.org/philosophy/free-sw.html
                    Thus, “free software” is a matter of liberty, not price. To understand the concept, you should think of “free” as in “free speech,” not as in “free beer”. We sometimes call it “libre software,” borrowing the French or Spanish word for “free” as in freedom, to show we do not mean the software is gratis.

                    So yeah "libre" is spanish/french for "free", and in many projects it is used instead of "free" to show that the software respects your freedom, while just stating "free software" is too generic as "free" is used for shareware and other gratis software which may or may not respect the user's freedoms. (and "Open" is not enough)

                    It's not a hard rule, but it's common nowadays.
                    Libreboot, Libreoffice, Linux-Libre, LibreCAD, LibreJS, LibreCMC, Libre.fm, Libreplanet, and probably other minor ones.

                    LibreELEC was born as a fork of OpenELEC. they never promised a blob-free linux distro.
                    Does not change the fact that "libre" is commonly used by such projects, so it does look strange on a distro shipping blobs.

                    It's not a crime either, I'm not flaming them for a name.

                    Comment

                    Working...
                    X