Remove keyType from ENCRYPTED_FIELDS in ssh_data set
Remove keyType from ENCRYPTED_FIELDS in ssh_credentials set
Problem
keyType was being incorrectly encrypted as if it were sensitive data. However, keyType only contains non-sensitive metadata values like "rsa", "ed25519", or "auto".
This caused SSH connection failures with the error:
## Summary
- Remove `keyType` from ENCRYPTED_FIELDS in `ssh_data` set
- Remove `keyType` from ENCRYPTED_FIELDS in `ssh_credentials` set
## Problem
`keyType` was being incorrectly encrypted as if it were sensitive data. However, `keyType` only contains non-sensitive metadata values like "rsa", "ed25519", or "auto".
This caused SSH connection failures with the error:
```
Cannot parse privateKey: Unsupported OpenSSH private key type: slh-rsa
```
The SSH client library was receiving an encrypted JSON string instead of the simple key type string it expected.
## Test plan
- [x] Verified metrics collection returns real data (CPU, memory, disk, uptime)
- [x] SSH terminal connections work correctly
- [x] File manager functional
🤖 Generated with [Claude Code](https://claude.com/claude-code)
LukeGus
(Migrated from github.com)
reviewed 2026-01-03 04:30:41 +11:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
keyTypefrom ENCRYPTED_FIELDS inssh_datasetkeyTypefrom ENCRYPTED_FIELDS inssh_credentialssetProblem
keyTypewas being incorrectly encrypted as if it were sensitive data. However,keyTypeonly contains non-sensitive metadata values like "rsa", "ed25519", or "auto".This caused SSH connection failures with the error:
The SSH client library was receiving an encrypted JSON string instead of the simple key type string it expected.
Test plan
🤖 Generated with Claude Code