Skip to content
View in the app

A better way to browse. Learn more.

Enpass Discussion Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

WhiteApfel

Members
  • Joined

  • Last visited

  1. Hi, I’ve been using Enpass for a while now, and I really appreciate the work you've done. However, there’s one feature I feel is missing: support for the Secret Service API via DBus, similar to what's available in KeePass or Gnome Keyring. Implementing this would allow Enpass to integrate more seamlessly with various desktop environments and applications on Linux. By adding this, Enpass could act as a Secret Service provider, allowing users to securely store and retrieve passwords using the standardized Secret Service API (as specified here: Freedesktop Secret Service API). This feature would be highly beneficial for those of us who rely on Linux for our daily workflow. I hope you’ll consider adding it in a future update. Thank you for your hard work and continued support for the Linux community! Best regards, Eugene Mayer
  2. I'm making a form for card details. I haven't found a universal guide on how to make a good form. I want autofill to work for all popular password managers and autofill services. Here's what I found in MDN (https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete): * The `input` field has an `autocomlpete` attribute * `cc-number` is used for card number * `cc-csc` is used for cvc/cvv * For expiration date `cc-exp` or `cc-exp-month` and `cc-exp-year ` But I ran into a problem, Enpass doesn't target these options for autocomplete. num: yes, exp: no, csc: no <form> <input type="text" autocomplete="cc-number" x-autocompletetype="cc-number"> <input type="text" autocomplete="cc-exp" x-autocompletetype="cc-exp"> <input type="text" autocomplete="cc-csc" x-autocompletetype="cc-csc"> </form> num: yes, exp: no, csc: no <form> <input type="text" id="cc-num" autocomplete="cc-number" x-autocompletetype="cc-number"> <input type="text" id="cc-exp" name="cc-exp" autocomplete="cc-exp" x-autocompletetype="cc-exp"> <input type="text" id="cc-csc" name="cc-csc" autocomplete="cc-csc" x-autocompletetype="cc-csc"> </form> num: yes, exp-m: no, exp-y: no, csc: no <form> <input type="text" autocomplete="cc-number" x-autocompletetype="cc-number"> <input type="text" autocomplete="cc-exp-month" x-autocompletetype="cc-exp-month"> <input type="text" autocomplete="cc-exp-year" x-autocompletetype="cc-exp-year"> <input type="text" autocomplete="cc-csc" x-autocompletetype="cc-csc"> </form> num: yes, exp-m: yes, exp-y: yes, csc: no <form> <input type="text" id="cc-num" autocomplete="cc-number" x-autocompletetype="cc-number"> <input type="text" id="cc-exp-month" name="cc-exp-month" autocomplete="cc-exp-month" x-autocompletetype="cc-exp-month"> <input type="text" id="cc-exp-year" name="cc-exp-year" autocomplete="cc-exp-year" x-autocompletetype="cc-exp-year"> <input type="text" id="cc-csc" name="cc-csc" autocomplete="cc-csc" x-autocompletetype="cc-csc"> </form> num: yes, exp-m: yes, exp-y: yes, csc: yes <form> <input type="text" id="cc-num" autocomplete="cc-number" x-autocompletetype="cc-number"> <input type="text" id="cc-exp-month" name="cc-exp-month" autocomplete="cc-exp-month" x-autocompletetype="cc-exp-month"> <input type="text" id="cc-exp-year" name="cc-exp-year" autocomplete="cc-exp-year" x-autocompletetype="cc-exp-year"> <input type="text" id="cc-csc" name="cvv" autocomplete="cc-csc" x-autocompletetype="cc-csc"> </form> Conclusions: * It is necessary to specify `cc-*` in `name` * `cc-exp` does not work, `cc-exp-month` and `cc-exp-year` are needed. * For secure code you must specify `cvv` or `cvc` I do not agree with these points. This creates an overload. And calling secure code one of the proprietary names (visa cvv or mastercard cvc) is not correct. I would like to get a guide from the Enpass team on how to make it perfect.
  3. You [Enpass] have few icons in your collection. And they cannot even be called basic, since there are too few of them. There is a function to get icons from Favicon. But you could create your own base and expand it at the request of clients, as Rocketbank did. Or display the "top" sites without a stylized icon on the forum so that people can draw what they need. I personally am ready to stylize more than 300 icons for Enpass-style. Be Rocket :rocket: :sparkles:

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.