Bias Analysis
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides examples for both Linux/macOS (known_hosts) and Windows (WinSCP registry key), but the Windows-specific client (WinSCP) and its registry storage are given a dedicated section, while no equivalent is given for Linux GUI SFTP clients. Windows-specific file paths (C:\Users\<user>/.ssh/known_hosts) are shown in error messages before the Linux/macOS equivalents. The registry key example is Windows-only, and the code sample uses a .NET library (SSH.NET), which is cross-platform but most commonly used on Windows.
Recommendations
- Add examples for popular Linux/macOS GUI SFTP clients (e.g., FileZilla, Cyberduck) and how they store host keys.
- When showing file paths, present Linux/macOS paths first or alongside Windows paths (e.g., ~/.ssh/known_hosts and C:\Users\<user>/.ssh/known_hosts).
- Clarify that the registry key example is specific to Windows and provide parity for Linux/macOS client configuration.
- Consider including a Python paramiko example, which is widely used on Linux/macOS.
- Explicitly mention that the known_hosts file location and format applies to Linux/macOS and Windows (with OpenSSH), and highlight differences if any.
Create Pull Request