4ef16cea56
This commit groups scripts related to disabling protocols under same category, streamlining the process for disabling protocols like NetBios, SMBv1, and various TLS/SSL versions. It improves the documentation and scripts of the related scripts. Key changes: - Introduce new category for disabling insecure protocols and move related scripts under it. - Remove .NET configuration from TLS 1.0 disabling to prevent unwanted side effects on .NET applications, maintaining system integrity. - Remove the script disabling DTLS 1.1 as this protocol does not exist. - Recommend previously not recommended scripts: - SSL 2.0 in 'Standard' because it's already removed from Windows. - SSL 3.0 in 'Standard' because it's already disabled by default. - TLS 1.0 in 'Strict' as it's deprecated on Windows. - TLS 1.1 in 'Strict' as it's deprecated on Windows. - Rename and reorder scripts for consistency and enhanced readability. - Fix revert codes to accurately reflect successful operations, by adding `2>nul` on `reg delete` commands. - Expand documentation to include detailed precautions and references, aiding users in understanding the implications of their actions (addressing user feedback from #57, #131, #183, #185). Other supporting changes: - Convert hexadecimal values to decimal to enhance script readability. - Refactor scripts to utilize shared functions, improving maintainability. - Add detailed comments within the scripts to aid in comprehension. - Minor updates to other crypto scripts for consistency. - Reorganize protocol listing by age for a logical script flow. - Standardize comments across various TLS configuration scripts for clarity. - Fix enabling DTLS 1.3 being categorized as disabling insecure connection.
privacy.sexy — Privacy is sexy
Enforce privacy & security best-practices on Windows, macOS and Linux, because privacy is sexy.
Get started
- 🌍️ Online: https://privacy.sexy.
- 🖥️ Offline: Download directly for: Windows, macOS, Linux. For more options, see here.
See also:
- Desktop vs. Web Features: Differences and unique aspects of desktop and web versions.
- System Requirements: Hardware and software requirements for the desktop version.
💡 Regularly applying your configuration with privacy.sexy is recommended, especially after each new release and major operating system updates. Each version updates scripts to enhance stability, privacy, and security.
Features
- Rich: Hundreds of scripts that aims to give you control of your data.
- Free: Both free as in "beer" and free as in "speech".
- Transparent. Have full visibility into what the tweaks do as you enable them.
- Reversible. Revert if something feels wrong.
- Accessible. No need to run any compiled software on your computer with web version.
- Secure: Security is a top priority at privacy.sexy with comprehensive safeguards in place.
- Open. What you see as code in this repository is what you get. The application itself, its infrastructure and deployments are open-source and automated thanks to bump-everywhere.
- Tested. A lot of tests. Automated and manual. Community-testing and verification. Stability improvements comes before new features.
- Extensible. Effortlessly extend scripts with a custom designed templating language.
- Portable and simple. Every script is independently executable without cross-dependencies.
Support
Sponsor 💕. Consider sponsoring on GitHub Sponsors, or you can donate using other ways such as crypto or a coffee.
Star 🤩. Feel free to give it a star ⭐ .
Contribute 👷. Contributions of any type are welcome. See CONTRIBUTING.md as the starting point. It includes useful information like how to add new scripts.
Additional Install Options
- Check the releases page for all available versions.
- Other unofficial channels (not maintained by privacy.sexy) for Windows include:
-
Scoop 🥄 (latest version):
scoop bucket add extras scoop install privacy.sexy -
winget 🪟 (may be outdated):
winget install -e --id undergroundwires.privacy.sexyWith winget, updates require manual submission; the auto-update feature within privacy.sexy will notify you of new releases post-installation.
-
Development
Refer to development.md for Docker usage and reading more about setting up your development environment.
Check architecture.md for an overview of design and how different parts and layers work together. You can refer to application.md for a closer look at application layer codebase and presentation.md for code related to GUI layer. collection-files.md explains the YAML files that are the core of the application and templating.md documents how to use templating language in those files. In ci-cd.md, you can read more about the pipelines that automates maintenance tasks and ensures you get what see.
docs/ folder includes all other documentation.
Security
Security is a top priority at privacy.sexy. An extensive commitment to security verification ensures this priority. For any security concerns or vulnerabilities, please consult the Security Policy.