2 ms·
Distribution package maintainers generally vet the packages they make avaliable and updates to repositories are typically PGP signed with cryptographically secu
by ryao 2y ago
Distribution package maintainers generally vet the packages they make avaliable and updates to repositories are typically PGP signed with cryptographically secure hashes for the files. I say typically because I am only familiar with Gentoo and to a lesser extent, the Debian family.
As for Windows, there is no signing requirement according to Microsoft:
> Windows doesn't require software developers to digitally sign their code
https://learn.microsoft.com/en-us/windows/security/application-security/application-control/app-control-for-business/deployment/use-code-signing-for-better-control-and-protection https://learn.microsoft.com/en-us/windows/security/applicati...
You are the one making stuff up.
- itvision 2y agoTry to run an unsigned installer in Windows 10/11 and tell me how it worked for you. This is how it works and looks: https://docs.anythingllm.com/installation-desktop/windows https://docs.anythingllm.com/installation-desktop/windows https://github.com/gitextensions/gitextensions/issues/7738 https://github.com/gitextensions/gitextensions/issues/7738 I never said it was a requirement. What's more you can enable GPO policies to prevent the user from running any new/unknown apps. https://learn.microsoft.com/en-us/windows-server/identity/software-restriction-policies/administer-software-restriction-policies https://learn.microsoft.com/en-us/windows-server/identity/so... Good luck implementing that in Linux. Continue to use a crap pseudo-OS with no security and believe everyone around is a geek who is willing to learn CLI, bash, vi, git bisect, reading mans, etc. just to use it. You have now accused me of saying something I'd never said, you crossed the line and goodbye.
- ryao 2y agoYou said: > Windows 10/11 both mandate that installers are signed before you can even launch them The word mandate means that it is a requirement.