News for hackers. Stuff that matters.
Re:A cautionary tale from the decline of SourceForge by mike_hearn on Thursday April 21, 2022 @01:43PM (#31112716)
Hash verification does nothing as SSL is protecting ordinary downloads from MITM attacks already.

Actually, binary package managers are arguably strictly less safe than getting the binaries directly from upstream because you've just introduced a (literal) "man in the middle", who might have their own agendas and their own need to monetize. Like, for example ... SourceForge did. In a different context these MITM attacks can go wrong even when they're genuinely trying to be helpful, as we may remember when Debian accidentally patched out important code from a core encryption library and caused everyone to get the same SSH keys.

Generally for security you want to reduce the number of middlemen who can tamper with things, unless those middlemen are explicitly adding some sort of security value by pre-tasting the apps. So, Apple app reviewers: yes. Linux distro maintainers: sorta sometimes. Homebrew, winget etc: no. It's all automated.

Re:A cautionary tale from the decline of SourceForge by noasaservice on Thursday April 21, 2022 @05:05PM (#31115175)
Explain to me how SSL tells me so I know which is the right site:

     https://www.vlcdownload.com
     https://www.vlcdownloads.com
     https://www.videolan.com
     https://www.vlc.com
     https://www.downloadvlc.com
     https://www.videolan.org
     https://www.videolan.co.uk
     https://sourceforge.net/projects/vlc/
In linux/Mac, I can "sudo apt install vlc", "sudo yum install vlc", or "sudo brew install vlc". I know I'm getting a valid and good software delivery. It just works. No malware. No sketchy websites. No malware packages.

On Windows, well, you feelin lucky?

Re:A cautionary tale from the decline of SourceForge by mike_hearn on Friday April 22, 2022 @06:30AM (#31120016)
That's true, but it cuts both ways.

apt-get install wine

Did you just get Wine from upstream? The answer is no and this has wasted significant amounts of time of Wine developers in the past. I used to be one and spent way too many free evenings and weekends debugging subtle crashes reported by users, that turned out to be packaging bugs introduced by men-in-the-middle.

Lots of other Wine devs had the same experience, so at that time we had a policy that if someone reported a bug the first instruction was to uninstall their distro package and to install the binary packages produced by the Wine project itself. Sometimes users were upset by this advice, but it resolved a significant number of "bugs" that were being added by the distributors.

Re:A cautionary tale from the decline of SourceForge by arinlen on Thursday April 21, 2022 @06:40PM (#31116060)
> On Windows, well, you feelin lucky?

Doesn't chocolatey fit the bill?

https://chocolatey.org/

Re:A cautionary tale from the decline of SourceForge by willismichael on Thursday April 21, 2022 @07:22PM (#31116406)
The whole point of the earlier comments is that it is preferable to use a package manager instead of using a browser to download binaries.
Re:A cautionary tale from the decline of SourceForge by arinlen on Friday April 22, 2022 @02:40AM (#31118913)
> The whole point of the earlier comments is that it is preferable to use a package manager instead of using a browser to download binaries.

But there are package managers for Windows, aren't there?

Microsoft even has its own app store, that you need to use to install applications such as Windows Terminal.

People often install software on Linux and macOS by downloading installers using a browser. In fact, that's how non-bleeding edge versions of Xcode are installed.

Re:A cautionary tale from the decline of SourceForge by TheSpiceIsLife on Thursday April 21, 2022 @07:25PM (#31116420)
On Windows I can just

   choco install vlc
Re:A cautionary tale from the decline of SourceForge by dijit on Thursday April 21, 2022 @07:43PM (#31116557)
It is preferable to read comments before replying.
Re:A cautionary tale from the decline of SourceForge by InfiniteRand on Friday April 22, 2022 @09:59AM (#31121615)
As a practical approach on Windows, for well-known software, I go to Wikipedia, look up the project there and then get the link, obviously that's not guaranteed to be correct, but for well-known projects bad links usually get corrected relatively fast, so it's probably correct

For lesser known projects I just cross my fingers, but typically lesser known projects are less likely to have malware posing as them

Re:A cautionary tale from the decline of SourceForge by yurymik on Thursday April 21, 2022 @05:57PM (#31115686)
Now we have `winget install VideoLAN.VLC` :)
Re:A cautionary tale from the decline of SourceForge by sharken on Thursday April 21, 2022 @10:18PM (#31117508)
Which is sadly not as intuitive as 'choco install vlc', WinGet really needs to support aliases to become widely used.

Chocolatey does have it's quirks though, there is both a '7zip' and a '7zip.install' package, it's not intuitive what the difference is.

Re:A cautionary tale from the decline of SourceForge by abetancort on Friday April 22, 2022 @05:45PM (#31128575)
Go to GitHub directly... forget direct links.
Re:A cautionary tale from the decline of SourceForge by saghm on Thursday April 21, 2022 @10:13PM (#31117476)
I think the idea is that a lot of the major package repositories tend to curate what's published (rather than let anyone arbitrarily publish whatever they'd like). If I trust the maintainers of the Debian or Fedora or Arch repos or whatever, then the fact that they serve a package means I would trust it more than downloading from some random website I don't know.