We provide security updates and patches for the following versions:
| Version | Supported |
|---|---|
| 2.x.x | ✅ Supported |
| < 2.0.0 | ❌ Not Supported |
Please ensure you are running the latest supported release to receive active security fixes.
If you discover a security vulnerability, please report it privately rather than opening a public issue.
- GitHub Private Vulnerability Reporting (Preferred): Navigate to the Security Tab of this repository and click "Report a vulnerability".
- Email: If you prefer direct email or cannot use GitHub Security Advisories, contact xuanlian@mac.com.
To help us triage and resolve the issue quickly, please include:
- A detailed description of the vulnerability and its potential impact.
- Affected version(s) and environment details (macOS version, Xcode version, architecture).
- Clear, reproducible step-by-step instructions or a minimal Proof of Concept (PoC).
- Acknowledgement: We will acknowledge receipt of your report within 48 hours.
- Investigation: We will investigate and assess severity.
- Fix & Disclosure: We will prepare a security patch and coordinate a coordinated disclosure or release notes update. Please allow reasonable time to remediate before public disclosure.
- Zero Plaintext Storage: Private keys, passphrases, and session credentials are encrypted and stored exclusively in macOS Keychain Services (
kSecClassGenericPassword). - Direct SSH Protocol: MacSSH establishes direct encrypted sockets to your destination SSH hosts; there are no intermediary telemetry, relay, or cloud proxy servers.
- Known Hosts Verification: Host keys are strictly verified against standard OpenSSH
known_hostsspecifications to prevent Man-in-the-Middle (MitM) risks.