Request to add native SSH key management with automatic SSH agent integration. This would turn PearPass into a secure, unified hub for SSH authentication, handling key lifecycle safely in the system agent.
Proposed Features:
πΉ 1. Entry-Level Key Management
Attach private key files directly to vault entries.
Auto-decrypt on agent load if the key is password-protected (use credentials from the entry).
Display metadata: public key, fingerprints (MD5, SHA256), and key comment.
πΉ 2. Lifecycle & Security Controls
Add keys to the SSH agent automatically on vault unlock.
Remove keys from the agent on vault lock/close.
Optional "require confirmation" flag for key usage.
Auto-remove timeout after last use (default: 600s, configurable).
πΉ 3. UI
Dedicated tab/window "Active SSH Keys" showing which keys are currently loaded in the agent.
"Clear Agent" button to instantly remove all PearPass-managed keys.
πΉ 4. Implementation Notes
Integrate with the system OpenSSH agent (Win/Linux/macOS) and/or Pageant (PuTTY).
Ensure compatibility with MobaXterm, WinSCP, PuTTY, native OpenSSH, VS Code Remote, etc.
Keys must never be written to disk: operate exclusively in memory via the standard SSH agent protocol.
Benefits: β Unified password & SSH key manager β Enhanced security: keys reside only in memory, auto-expire, and clear on lock β Seamless workflow with any terminal, IDE, or SSH client
Happy to provide feedback or assist with testing. Thanks for your great work! π‘οΈ
Please authenticate to join the conversation.
Feature Requests
About 3 hours ago

Dotpwnpewpew
Get notified by email when there are changes.
Feature Requests
About 3 hours ago

Dotpwnpewpew
Get notified by email when there are changes.