Hacker News Reader

Comment by gigel82 | Hacker News Reader

Likely done by an eager intern back then as a binary drop and never properly integrated into whatever build system Windows uses.

Nevertheless, as a consumer, I appreciate having curl in-box (no matter how out-of-date). Came in handy when I wanted to firewall the heck out of Windows 11 and strip out every unwanted component (including the only browser, Edge). Of course, later found out that curl.exe complains about ssl certificates if you firewall / block whatever Windows service does certificate validation, but luckily PowerShell has a built-in wget command as well for downloading which doesn't seem to care as much :)

View on HN

Well, if you really want to strip all unwanted components, take a look at WinGet. Everything (by everything, I mean everything) is just a winget uninstall away

And if you really really wanted to strip all the unwanted components, install Linux! xD

I know its a joke, but programming is not the only essence people have to use a windows system. There is entire Adobe Suite, and many windows exclusive softwares sometimes mandatory.

Adobe runs just fine on macOS, if you have to use Adobe.

The parent talked about Linux, so.

Yeah thanks...now i have systemd :)

BTW, the Wget that comes built-in with Powershell is not GNU Wget. But a weird abomination from Microsoft. They just call it Wget despite it having nothing to do with the original

It's an alias for Invoke-WebRequest command, to be more precise.

  Get-Alias wget
  CommandType     Name                      
  -----------     ----                      
  Alias           wget -> Invoke-WebRequest

https://docs.microsoft.com/en-us/powershell/module/microsoft...

This is how to remove it, in case you want to use a real version of 'wget' found on your $env:PATH:

    Remove-Item Alias:\wget -force

I also suggest doing the same for curl so that the real version of curl can run when just typing in 'curl':

    Remove-Item Alias:\curl -force

I have added these lines to my $PROFILE so that every time I invoke a PowerShell, I get more sane settings.

Luckily, these aliases are removed in PowerShell Core. https://github.com/PowerShell/PowerShell/pull/5268

Only for Windows Powershell. The alias is no longer there in Powershell 7.

There’s an option for curl to ignore cert validation

Tried that first, apparently only works with OpenSSL and the Windows binary is linked to some OS SSL library instead.

Probably SCHANNEL then.

OS must reach out crl.microsoft.com for CRL checks. https://social.technet.microsoft.com/wiki/contents/articles/...

Yes, that's the one. I wanted to start with a fully firewalled system and explicitly allow URLs as I go along. I needed to eventually allow that one through to get to a functional state (with Windows Update and MS Store running).

Reply on news.ycombinator.com