I wonder what privacy guidelines would say about this type of program. They seem to give windows better privacy.
privacy.sexy
1 Like
I would strongly advise against these.
4 Likes
You don’t think about those.
A strong NO.
I would avoid these and similar projects.
If you are going to use a highly non-private operating system like Windows, and you plan to make it more private, you should know what’s actually being changed to protect your privacy. That necessitates going through settings, group policies, etc. and doing it yourself, learning as you go.
For starters, using an automated approach somebody else designed means you won’t understand what the limitations of your system actually are, which will make proper opsec impossible.
Similar to why we recommend following Arkenfox configuration guides with Firefox, instead of using rando poorly-tested forks like Librewolf.
Actually, privacy.sexy isn’t necessarily bad, because it does let you configure it individually and it shows you exactly what is happening. But if you don’t understand the script it is generating, or if you don’t understand what the options do, then I wouldn’t recommend it. It is not something where you can/should just blindly switch all the options on. I would not use the “Standard / Strict / All” pre-selections.
2 Likes
Running somebody else’s script is ofcourse dangerous, pettaining to windows, you have these options:
Run LTSC iso taken directly from mixrosoft’s official site.
Configure windows group policies yourself, I have my own config that isn’t public but this one is nice, that you can refer.
For updates, I myself use and trust ntlite, though you can just install only security updates.
1 Like
I’d refer to this thread if you’re stuck using those for any reasons.