It’s fixed now.

Before it worked.

  • Red@reddthat.com
    link
    fedilink
    English
    arrow-up
    7
    ·
    5 days ago

    You can download it over http and check the SHA256SUMS.

    Or better yet torrent it and check the same sha256

    I can’t remember if it was always like that or not, but all the apt repos are the same. No SSL and verification via signing.

    • lengau@midwest.social
      link
      fedilink
      arrow-up
      5
      ·
      5 days ago

      Apt repos are like that for several reasons, one of which is that it allows DNS based mirroring without having to share a certificate. Another is that back when apt started out, HTTPS was pretty rare.

    • dunes@feddit.orgOP
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      edit-2
      5 days ago

      It seems like an odd choice if it’s not a mistake to put it on the first page and it’s not just a HTTP warning it’s an SSL warning that appears quite scary on Chromium browsers.

      But cool to know that apt repos don’t use SSL i knew they verified via signature but fought they had both.

    • EddyBot@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      5 days ago

      Torrent programs already do checking hash checksums to determine if you got it 100%

      thats also the only reason to check your download with a provided hash checksum from a website… to check the intigrity of the download and not for safety reasons

      • Red@reddthat.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 days ago

        Torrents verify that the data they downloaded is correct.
        That doesn’t mean the data that was used to create the torrent was correct. In this case I suggested downloading via torrent (because of http) and then checking the sha from the website to verify everything matches. If it does they you’ve got a good iso!