Windows Hello unlock support for PearPass Desktop on Windows
Hi PearPass team, I would like to request Windows Hello support for the PearPass Desktop app on Windows. Requested feature Please consider adding an option to unlock PearPass Desktop on Windows using Windows Hello, including fingerprint, face recognition, or Windows Hello PIN where available. Suggested behavior: After the user unlocks the vault with the master password once, allow enabling Windows Hello unlock in Settings. On subsequent unlocks, allow the user to unlock the vault with Windows Hello instead of typing the master password every time. Keep the master password as the fallback and primary recovery method. Require the master password again after security-sensitive events, for example: system reboot; app restart, depending on the chosen security model; failed or cancelled Windows Hello attempts; Windows Hello being disabled or changed in Windows settings; vault timeout or manual lock, depending on the configured policy. Add a clear setting such as: Unlock with Windows Hello optional timeout controls, for example Require master password after X minutes / after restart. Security expectations Since PearPass is a password manager, Windows Hello should only be used as a local unlock mechanism and should preserve the existing vault security model. Ideally: Unlock material should be protected using Windows-native secure storage mechanisms where appropriate, for example Windows Hello / TPM-backed APIs / platform-protected key storage. The master password should not be stored, logged, or exposed in plaintext. The renderer process should not be able to bypass the Windows Hello gate. Users should be able to disable Windows Hello unlock at any time. If Windows Hello is unavailable, fails, or is cancelled, PearPass should fall back to the vault master password. Why this matters PearPass already focuses on local-first, privacy-preserving password management. Windows Hello unlock would make the Windows desktop experience much more practical for everyday use, especially when the vault locks frequently. This would also bring Windows closer to the biometric unlock experience available on mobile platforms and to the Touch ID support being discussed for macOS. Thanks for considering this.
Evgeniy about 2 months ago
Windows Hello unlock support for PearPass Desktop on Windows
Hi PearPass team, I would like to request Windows Hello support for the PearPass Desktop app on Windows. Requested feature Please consider adding an option to unlock PearPass Desktop on Windows using Windows Hello, including fingerprint, face recognition, or Windows Hello PIN where available. Suggested behavior: After the user unlocks the vault with the master password once, allow enabling Windows Hello unlock in Settings. On subsequent unlocks, allow the user to unlock the vault with Windows Hello instead of typing the master password every time. Keep the master password as the fallback and primary recovery method. Require the master password again after security-sensitive events, for example: system reboot; app restart, depending on the chosen security model; failed or cancelled Windows Hello attempts; Windows Hello being disabled or changed in Windows settings; vault timeout or manual lock, depending on the configured policy. Add a clear setting such as: Unlock with Windows Hello optional timeout controls, for example Require master password after X minutes / after restart. Security expectations Since PearPass is a password manager, Windows Hello should only be used as a local unlock mechanism and should preserve the existing vault security model. Ideally: Unlock material should be protected using Windows-native secure storage mechanisms where appropriate, for example Windows Hello / TPM-backed APIs / platform-protected key storage. The master password should not be stored, logged, or exposed in plaintext. The renderer process should not be able to bypass the Windows Hello gate. Users should be able to disable Windows Hello unlock at any time. If Windows Hello is unavailable, fails, or is cancelled, PearPass should fall back to the vault master password. Why this matters PearPass already focuses on local-first, privacy-preserving password management. Windows Hello unlock would make the Windows desktop experience much more practical for everyday use, especially when the vault locks frequently. This would also bring Windows closer to the biometric unlock experience available on mobile platforms and to the Touch ID support being discussed for macOS. Thanks for considering this.
Evgeniy about 2 months ago
Safari extension support for PearPass
Hi PearPass team, I would like to request an official Safari extension for PearPass. Requested feature Please consider adding Safari support for the PearPass browser extension, ideally for macOS first, and iOS/iPadOS if technically feasible. The Safari extension should support the same core workflows as the existing browser extension where possible: Autofill saved logins and identities. Detect login forms and suggest matching vault entries. Create and use passkeys on websites that support WebAuthn. Generate strong passwords. Communicate with PearPass Desktop through the native app bridge or an equivalent Safari-compatible mechanism. Respect the existing local-first and end-to-end encrypted PearPass security model. Suggested implementation direction Since Safari supports Web Extensions, it may be possible to reuse part of the existing PearPass browser extension codebase and adapt the packaging, permissions, native messaging / app bridge, and distribution flow for Safari. The minimum useful version would be: Safari extension for macOS. Works with the PearPass Desktop app. Supports autofill for logins and identities. Supports vault unlock / vault selection flow consistently with the existing extension. Provides clear setup instructions for pairing the Safari extension with the desktop app. Future improvements could include: iOS/iPadOS Safari support, if Apple platform constraints allow it. Passkey creation and authentication parity with the existing browser extension. App Store distribution for easier installation and updates. Why this matters Safari is the default browser on macOS, iOS, and iPadOS. Without Safari support, users in the Apple ecosystem need to switch browsers just to use PearPass autofill and passkey workflows. An official Safari extension would make PearPass more viable as a daily password manager for Mac users and would improve browser coverage alongside Chrome/Chromium and Firefox-related work. Thanks for considering this.
Evgeniy about 2 months ago
Safari extension support for PearPass
Hi PearPass team, I would like to request an official Safari extension for PearPass. Requested feature Please consider adding Safari support for the PearPass browser extension, ideally for macOS first, and iOS/iPadOS if technically feasible. The Safari extension should support the same core workflows as the existing browser extension where possible: Autofill saved logins and identities. Detect login forms and suggest matching vault entries. Create and use passkeys on websites that support WebAuthn. Generate strong passwords. Communicate with PearPass Desktop through the native app bridge or an equivalent Safari-compatible mechanism. Respect the existing local-first and end-to-end encrypted PearPass security model. Suggested implementation direction Since Safari supports Web Extensions, it may be possible to reuse part of the existing PearPass browser extension codebase and adapt the packaging, permissions, native messaging / app bridge, and distribution flow for Safari. The minimum useful version would be: Safari extension for macOS. Works with the PearPass Desktop app. Supports autofill for logins and identities. Supports vault unlock / vault selection flow consistently with the existing extension. Provides clear setup instructions for pairing the Safari extension with the desktop app. Future improvements could include: iOS/iPadOS Safari support, if Apple platform constraints allow it. Passkey creation and authentication parity with the existing browser extension. App Store distribution for easier installation and updates. Why this matters Safari is the default browser on macOS, iOS, and iPadOS. Without Safari support, users in the Apple ecosystem need to switch browsers just to use PearPass autofill and passkey workflows. An official Safari extension would make PearPass more viable as a daily password manager for Mac users and would improve browser coverage alongside Chrome/Chromium and Firefox-related work. Thanks for considering this.
Evgeniy about 2 months ago
Distributed backup and recovery
Implement a feature to allow users (opt-in) to distribute their vaults encrypted to the network and recover them from a fresh install using a mnemonic phrase or something other deterministic approach.
Alberto Valero 7 months ago
Distributed backup and recovery
Implement a feature to allow users (opt-in) to distribute their vaults encrypted to the network and recover them from a fresh install using a mnemonic phrase or something other deterministic approach.
Alberto Valero 7 months ago
YubiKey Support
U2F-enabled Security Key, such as the YubiKey, user login is bound to the origin, meaning that only the real site can authenticate with the key. The authentication will fail on the fake site even if the user was fooled into thinking it was real. This greatly mitigates against the increasing volume and sophistication of phishing attacks and stops account takeovers. Standard https://www.yubico.com/authentication-standards/fido-u2f-standard/
William K Santiago 7 months ago
YubiKey Support
U2F-enabled Security Key, such as the YubiKey, user login is bound to the origin, meaning that only the real site can authenticate with the key. The authentication will fail on the fake site even if the user was fooled into thinking it was real. This greatly mitigates against the increasing volume and sophistication of phishing attacks and stops account takeovers. Standard https://www.yubico.com/authentication-standards/fido-u2f-standard/
William K Santiago 7 months ago
Add an option to select a default Vault that opens automatically after authenticating.
Selecting the Vault every time, especially when the user has only one, is a drag. This UX is also confusing as it gives the impression that the primary expected action here is to create a Vault. Perhaps add a configurable modifier key (like the option key on macOS, as a default) that shows the list of vaults to select from if pressed when authenticating. Alternatively, add another button to view the Vault list to select from.
Tiger 7 months ago
Add an option to select a default Vault that opens automatically after authenticating.
Selecting the Vault every time, especially when the user has only one, is a drag. This UX is also confusing as it gives the impression that the primary expected action here is to create a Vault. Perhaps add a configurable modifier key (like the option key on macOS, as a default) that shows the list of vaults to select from if pressed when authenticating. Alternatively, add another button to view the Vault list to select from.
Tiger 7 months ago
SSH Key Support with Automatic SSH Agent Integration (OpenSSH / Pageant)
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! π‘οΈ
Dotpwnpewpew 2 months ago
SSH Key Support with Automatic SSH Agent Integration (OpenSSH / Pageant)
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! π‘οΈ
Dotpwnpewpew 2 months ago
Link device similar to Keet
Where all your vaults from one device and master password sync to another device. So you can just scan a QR or paste a link on another device and you have the exact same Pearpass on one device as another
kikkarokki 7 months ago
Link device similar to Keet
Where all your vaults from one device and master password sync to another device. So you can just scan a QR or paste a link on another device and you have the exact same Pearpass on one device as another
kikkarokki 7 months ago
Option to sync master password between devices
If any of the devices change master password it changes it for all devices with this enabled
kikkarokki 7 months ago
Option to sync master password between devices
If any of the devices change master password it changes it for all devices with this enabled
kikkarokki 7 months ago
Reduce taps to log in via biometrics and select vault before credentials displayed for android autofill
Request: Reduce the screen taps and options to completing an autofill credential selection using Android autofill. Currently to select an autofill credential a user has to tap "use fingerprint", provide fingerprint then select a vault and finally make the credential selection Please consider having the fingerprint option as default login when opening the app, instant log in. Then have a vault option as default when log in is complete getting you straight to the credential. One fingerprint provided instead of 3 interactions
vanhoopstallion 7 months ago
Reduce taps to log in via biometrics and select vault before credentials displayed for android autofill
Request: Reduce the screen taps and options to completing an autofill credential selection using Android autofill. Currently to select an autofill credential a user has to tap "use fingerprint", provide fingerprint then select a vault and finally make the credential selection Please consider having the fingerprint option as default login when opening the app, instant log in. Then have a vault option as default when log in is complete getting you straight to the credential. One fingerprint provided instead of 3 interactions
vanhoopstallion 7 months ago
Autofill on IOS does not work
Autofill doesn't work on IOS Worked on version 1.5 and 2.0 Enviromental: appVersion: 2.1.0 platform: ios platformVersion: 26.4
Dotpwnpewpew about 2 months ago
Autofill on IOS does not work
Autofill doesn't work on IOS Worked on version 1.5 and 2.0 Enviromental: appVersion: 2.1.0 platform: ios platformVersion: 26.4
Dotpwnpewpew about 2 months ago
Filter/category for entries that contain passkeys
Feature suggestion: Could you please add a filter/category for entries that contain passkeys (similar to existing filters like Recovery Phrases, WiβFi, etc.)? This would help to: Quickly find accounts set up with passkey login; Manage those entries more easily (edit, export, delete); Get an overview of passwordless authentication usage across my vault. If this is technically straightforward, it would be a very welcome addition. Thanks again for your great work!
Dotpwnpewpew 2 months ago
Filter/category for entries that contain passkeys
Feature suggestion: Could you please add a filter/category for entries that contain passkeys (similar to existing filters like Recovery Phrases, WiβFi, etc.)? This would help to: Quickly find accounts set up with passkey login; Manage those entries more easily (edit, export, delete); Get an overview of passwordless authentication usage across my vault. If this is technically straightforward, it would be a very welcome addition. Thanks again for your great work!
Dotpwnpewpew 2 months ago
π full-text search in notes
A full-text keyword search across note titles and content is required to use PearpPa ss as a single note-taking app, eliminating every other note app.
Sebastiano 7 months ago
π full-text search in notes
A full-text keyword search across note titles and content is required to use PearpPa ss as a single note-taking app, eliminating every other note app.
Sebastiano 7 months ago
BUG: Extension loses autofill after Passkey is added to an existing entry
Summary When a Passkey is added to an existing vault entry, the browser extension stops recognizing that entry for autofill β showing "No records found" β until a new separate entry is created for the same site. Steps to reproduce 1.Create a vault entry with a username + password for a site. 2.Verify the extension autofills credentials correctly. 3.Add a Passkey to the same entry. 4.Navigate to the site's login page and trigger autofill via the extension. Actual Extension shows "No records found" β entry is no longer matched to the site. Workaround Creating a new separate entry for the same site restores autofill Root cause hypothesis Adding a Passkey may alter the entry's internal type, URI matching logic, or record structure in a way that causes the extension's site-matching query to exclude entries that contain a Passkey credential. Requested fix Ensure that adding a Passkey to an entry does not break existing username/password autofill matching. Both credential types should coexist in a single entry and be independently discoverable by the extension. I checked on the Dropbox website After creating a new record
Dotpwnpewpew about 2 months ago
BUG: Extension loses autofill after Passkey is added to an existing entry
Summary When a Passkey is added to an existing vault entry, the browser extension stops recognizing that entry for autofill β showing "No records found" β until a new separate entry is created for the same site. Steps to reproduce 1.Create a vault entry with a username + password for a site. 2.Verify the extension autofills credentials correctly. 3.Add a Passkey to the same entry. 4.Navigate to the site's login page and trigger autofill via the extension. Actual Extension shows "No records found" β entry is no longer matched to the site. Workaround Creating a new separate entry for the same site restores autofill Root cause hypothesis Adding a Passkey may alter the entry's internal type, URI matching logic, or record structure in a way that causes the extension's site-matching query to exclude entries that contain a Passkey credential. Requested fix Ensure that adding a Passkey to an entry does not break existing username/password autofill matching. Both credential types should coexist in a single entry and be independently discoverable by the extension. I checked on the Dropbox website After creating a new record
Dotpwnpewpew about 2 months ago
Flexible Word Count for Recovery Phrase Records
1. Overview Pearpass currently supports Recovery Phrase records with a fixed word count of 12 or 24 words (BIP-39 standard). However, various services and platforms use recovery phrases, mnemonic codes, and backup codes with different word counts. This feature request proposes extending the Recovery Phrase record type to support a configurable, user-defined word count. 2. Problem Statement Users who store recovery credentials for services outside the BIP-39 ecosystem (cryptocurrency wallets) are forced to use workaround solutions such as free-text notes, which lack the structured UX, copy-per-word functionality, and validation benefits of the dedicated Recovery Phrase record type. Known services with non-standard word counts: Service Word / Code Count Format Notes Bitcoin / Ethereum wallets (BIP-39) 12 or 24 words Currently supported Steam Guard ~30 words Recovery code list Dropbox 10 words Account recovery phrase GitHub 16 codes
Dotpwnpewpew about 2 months ago
Flexible Word Count for Recovery Phrase Records
1. Overview Pearpass currently supports Recovery Phrase records with a fixed word count of 12 or 24 words (BIP-39 standard). However, various services and platforms use recovery phrases, mnemonic codes, and backup codes with different word counts. This feature request proposes extending the Recovery Phrase record type to support a configurable, user-defined word count. 2. Problem Statement Users who store recovery credentials for services outside the BIP-39 ecosystem (cryptocurrency wallets) are forced to use workaround solutions such as free-text notes, which lack the structured UX, copy-per-word functionality, and validation benefits of the dedicated Recovery Phrase record type. Known services with non-standard word counts: Service Word / Code Count Format Notes Bitcoin / Ethereum wallets (BIP-39) 12 or 24 words Currently supported Steam Guard ~30 words Recovery code list Dropbox 10 words Account recovery phrase GitHub 16 codes
Dotpwnpewpew about 2 months ago
Trash / Recently Deleted Folder
When a user deletes an item, it should not be permanently removed immediately. Instead, deleted items should be moved to a Trash (or Recently Deleted) folder where they remain for a limited period (for example, 30 days) before being permanently deleted. This would allow users to restore items that were accidentally deleted, improving safety and reducing the risk of losing important credentials. Users should also have the option to manually restore items or permanently delete them from the Trash at any time.
Constantine Mindiashvili 5 months ago
Trash / Recently Deleted Folder
When a user deletes an item, it should not be permanently removed immediately. Instead, deleted items should be moved to a Trash (or Recently Deleted) folder where they remain for a limited period (for example, 30 days) before being permanently deleted. This would allow users to restore items that were accidentally deleted, improving safety and reducing the risk of losing important credentials. Users should also have the option to manually restore items or permanently delete them from the Trash at any time.
Constantine Mindiashvili 5 months ago
Per vault passwords also syncable between devices
So for example you can share a group of vaults and give selective access to them. Say you want family members to have access to your pearpass but only some of the vaults. Another way this might be solved is multiple master passwords each with a different profile and vaults etc
kikkarokki 7 months ago
Per vault passwords also syncable between devices
So for example you can share a group of vaults and give selective access to them. Say you want family members to have access to your pearpass but only some of the vaults. Another way this might be solved is multiple master passwords each with a different profile and vaults etc
kikkarokki 7 months ago
Export and import of embedded file contents (Attachments)
Problem: Current export only saves attachment metadata (id, name). File content is missing, making backups incomplete. "attachments": [ { "id": "00000000-3b5a-4638-8b01-3ddb93f974d0", "name": "recovery.txt" } ] Goal: Enable full export & import of attachment Export: Include attachments toggle. Reads files β Base64 + SHA-256 β JSON β encrypt. Limits: 10 MB/file, 50 MB total. Import: Decodes Base64, verifies sha256, restores to local storage.
Dotpwnpewpew about 2 months ago
Export and import of embedded file contents (Attachments)
Problem: Current export only saves attachment metadata (id, name). File content is missing, making backups incomplete. "attachments": [ { "id": "00000000-3b5a-4638-8b01-3ddb93f974d0", "name": "recovery.txt" } ] Goal: Enable full export & import of attachment Export: Include attachments toggle. Reads files β Base64 + SHA-256 β JSON β encrypt. Limits: 10 MB/file, 50 MB total. Import: Decodes Base64, verifies sha256, restores to local storage.
Dotpwnpewpew about 2 months ago