Closed teknowledgist closed 3 years ago
OMG ! Not again :)
Au actually does that:
Do you use latest master version ? Can't remember if this is published... :S
Ha! I guess I'm trying to reinvent what's already been fixed.
Well, kinda fixed. The latest AU Chocolatey package version (which I'm using) does not have that fix, and I'd prefer to upgrade that way than via git. Any idea when the next release will come out?
Thanks.
I don't know... couple of weeks to months. Working on test package sandbox feature as time permits so I will publish when it is done.
You should probably go manual in this case.
Understood. At least the fix is in place and will be available at some point. Thanks.
No problem, sorry for the delay.
update.ps1
works great on my Win10 systems, but recently I have a need to update packages on a Server 2019 system, and every time, I get an error message:If I run that line,
[System.Net.ServicePointManager]::SecurityProtocol = 'Tls,Tls11,Tls12,Tls13'
by itself, I get the same error, but if I modify it:[System.Net.ServicePointManager]::SecurityProtocol = 'Tls,Tls11,Tls12'
, it works just fine.I have not been able to find any information on how to enable TLS1.3 in Server 2019. If someone else can, could a link to that information be included in the documentation for AU?
Maybe AU could check what protocols are supported before setting what it will use? Something like:
Thanks.