Files

undergroundwires 8c17396285 Fix script cancellation with new dialog on Linux

This commit improves the management of script execution process by
enhancing the way terminal commands are handled, paving the way for
easier future modifications and providing clearer feedback to users when
scripts are cancelled.

Previously, the UI displayed a generic error message which could lead to
confusion if the user intentionally cancelled the script execution. Now,
a specific error dialog will appear, improving the user experience by
accurately reflecting the action taken by the user.

This change affects code execution on Linux where closing GNOME terminal
returns exit code `137` which is then treated by script cancellation by
privacy.sexy to show the accurate error dialog. It does not affect macOS
and Windows as curret commands result in success (`0`) exit code on
cancellation.

Additionally, this update encapsulates OS-specific logic into dedicated
classes, promoting better separation of concerns and increasing the
modularity of the codebase. This makes it simpler to maintain and extend
the application.

Key changes:

- Display a specific error message for script cancellations.
- Refactor command execution into dedicated classes.
- Improve file permission setting flexibility and avoid setting file
  permissions on Windows as it's not required to execute files.
- Introduce more granular error types for script execution.
- Increase logging for shell commands to aid in debugging.
- Expand test coverage to ensure reliability.
- Fix error dialogs not showing the error messages due to incorrect
  propagation of errors.

Other supported changes:

- Update `SECURITY.md` with details on script readback and verification.
- Fix a typo in `IpcRegistration.spec.ts`.
- Document antivirus scans in `desktop-vs-web-features.md`.

2024-04-30 15:04:59 +02:00

4.8 KiB

Raw Blame History

Security Policy

Security is a top priority at privacy.sexy. Please report any discovered vulnerabilities responsibly.

Reporting a Vulnerability

Efforts to responsibly disclose findings are greatly appreciated. To report a security vulnerability, follow these steps:

For general vulnerabilities, open an issue using the bug report template.
For sensitive matters, contact the developer directly.

Security Report Handling

Upon receiving a security report, the process involves:

Confirming the report and identifying affected components.
Assessing the impact and severity of the issue.
Fixing the vulnerability and planning a release to address it.
Keeping the reporter informed about progress.

Security Practices

Application Security

privacy.sexy adopts a defense in depth strategy to protect users on multiple layers:

Link Protection: privacy.sexy ensures each external link has special attributes for your privacy and security. These attributes block the new site from accessing the privacy.sexy page, increasing your online safety and privacy.
Content Security Policies (CSP): privacy.sexy actively follows security guidelines from the Open Web Application Security Project (OWASP) at strictest level. This approach protects against attacks like Cross Site Scripting (XSS) and data injection.
Host System Access Control: The desktop application segregates and isolates code sections based on their access levels through sandboxing. This provides a critical defense mechanism, prevents attackers from introducing harmful code into the app, known as injection attacks.
Auditing and Transparency: The desktop application improves security and transparency by logging application activities and retaining files of executed scripts This facilitates detailed auditability and effective troubleshooting, contributing to the integrity and reliability of the application. Recognizing that some users prefer not to keep these records, privacy.sexy provides specialized scripts for deletion of these logs.
Privilege Management: The desktop application operates without persistent administrative or sudo privileges, reinforcing its security posture. It requests elevation of privileges for system modifications with explicit user consent and logs every action taken with high privileges. This approach actively minimizes potential security risks by limiting privileged operations and aligning with the principle of least privilege.
Secure Script Execution/Storage:
- Antivirus scans: Before executing any script, the desktop application stores a copy to allow antivirus software to perform scans. This step allows confirming that the scripts are secure and safe to use.
- Tamper protection: The application incorporates integrity checks for tamper protection. If the script file differs from the user's selected script, the application will not execute or save the script, ensuring the processing of authentic scripts. This safeguards against any unwanted modifications.
- Clean-up: Recognizing that some users prefer not to keep these records, privacy.sexy provides specialized scripts for deletion of these scripts. This allows users to maintain their privacy by removing traces of their usage patterns or script preferences.

Update Security and Integrity

privacy.sexy benefits from automated update processes including security tests. Automated deployments from source code ensure immediate and secure updates, mirroring the latest source code. This aligns the deployed application with the expected source code, enhancing transparency and trust. For more details, see CI/CD Documentation.

Every desktop update undergoes a thorough verification process. Updates are cryptographically signed to ensure authenticity and integrity, preventing tampered versions from reaching your device. Version checks are conducted to prevent downgrade attacks.

Testing

privacy.sexy's testing approach includes a mix of automated and community-driven tests. Details on testing practices are available in the Testing Documentation.

Support

For help or any questions, submit a GitHub issue. Addressing security concerns is a priority, and we ensure the necessary support.

Support privacy.sexy's commitment to security by making a donation ❤️. Your contributions aid in maintaining and enhancing the project's security features.

Active contribution to the safety and security of privacy.sexy is thanked. This collaborative effort keeps the project resilient and trustworthy for all.

4.8 KiB Raw Blame History