Ivarson

I like the the new theme, it catches up the design from the initial simple UWP design language, also making the UIs of Linux and Windows more similar (you ditched dark theme for classic theme on windows few years ago for some reason) I still agree with @bu11etpr00f on the unnecessary extra click for Copy, and the expand button for Note fields seems unneeded too. Good job that you allow Notes to get more space when windows is maximized though. (once expanded). I do miss the one-column view that you got rid of (now you can only have a two or three column view) I would like to be able to to hide the menu-bar, it clutters the nice ui and I never use it.

in the new beta-version for Windows 11, when you search an item, once you stop typing and Enpass starch searching your vaults 1 second later. When the result shows up, focus shifts to the Home category. This forces you to again focus the searchbar to continue searching. change this to remain focus on the searchbar even when the search-process has completed

Ping.

Perplexity just released Comet for Android. Autofill via keyboard does not kick in. Android 16 Samsung A54 Enpass 6.11.16.1201

When you're setting up sync for a vault in enpass for Android, you don't need to enroll the whole phone with that account. You'll be redirected to the Google Account page in Google chrome, just make sure to "login with another account", entering the credentials for the shared Google account. Once the sync is ongoing, you can logout from that account in Google Chrome (account.google.com) so you're not accidentally use it for other stuff when surfing. If you're insecure of this, you might consider using a Dropbox or Microsoft account instead. The shared account (whichever provider) should be used only for the shared enpass vault (IMHO). Also, make sure to store the credentials for the shared vault in both yours and your wife's _primary_ vault, so it's not being lost in the shared vault (catch 22)

Any news on this @Amandeep Kumar? Also tried on: Kali Linux Enpass 6.10.1 Chrome 127.0.6533.99 Still doesn't work. I was able to create a PassKey in Enppas for Android android, but obviously can't use it on desktops. Is LinkedIn enforcing hardware-bound passkeys that Enpass is unable to process?

That's fine, but can you at least confirm that there _are_ plans to upgrade it?

Upgrade portable already. It's way behind

Workaround confirmed working. Is this something that can be addressed from Enpass side or do we have to wait for Google to sort Chrome out?

Only text and images has the open-option in enpass (if I remember correctly) so having only Save for a pdf is expected, should apply whether an item was imported or created originally in Enpass. The limitation for pictures and text is due to enpass not wanting to dump the file outside the app, since it might be left in a temporary folder or cached in a external application.

All of a sudden, webauthn (passkeys) requests in Chrome are not being redirected and picked up by enpass. Chrome 125.0.6422.72 Enpass 6.10.2.986 Android 14/Samsung a54 Passkeys still works in (the few) native Android apps that supports passkeys.

I know, it's supposed to :-) I was asking about how the shared data _looked_ like, when you could share without AES-256 encrypting it. Pretty sure it was plaintext fields on each row, and a .ENPASSCARD-file with non-encrypted base64. anyway, wouldnt a "Copy All"-option sort your needs? The clipboard would contain all populated fields in the item, and would be intended for human-to-human sharing or external copying. (base64 is in essenence made for normalized transportation) --- Title: XCV Username: XCV Password: XCV Website: <URL> --- i also recall talking to enpass support one or two years ago about a web-based service for external password sharing, and they were "working on it" something like Bitwarden Send or Lastpass password sharing where you could have either password- or limited accessattempts on a generated weblink, not sure if that took of or not.

I was asking about the per-item 'Share'-function, not the 'Export' and how the non-PSK shared data looked like

I dont remember what the unprotected sharing looked like, but think it was All fields in plaintext, and a enpasscard in base64? @Amandeep Kumar If you want the Share-function to be a secure Enpass-only thing where there are no shared vaults involved, you could instead add a "Copy All Fields" for the items (you already have Copy Username, Copy Password, Copy URL, Copy OTP, Copy Email.. adding a Copy All wouldn't reduce security _that much_, possibly the fact that all fields resides in clipboard at thesame time, but atlest the clipboard would still be protected by the builtin timer that wipes records after some time by default. As a sidenote, in the Windows-app, there's a Print function where Enpass generates PDF-files. This can be used in some cases, but it's clunky, the content cant be highlighted and copied from and so forth, but if you want to share several fields at once, and the password isn't too long and complex, you can select an item, hit the Burger-menu (not the items three dots) -> File -> Print -> selected items. Then make sure that "Microsoft Print to PDF" is selected, which creates a local PDF instead of going to a physical printer. Due to a glitch i guess, the "selected items" is only available if you're viewing ONE vault, when All Vaults are selected (i.e you have many vaults) you can only select ALL ITEMS. I dont recommend the print-thing as a sharing-concept, just pointing out its there for the Windows Desktop app.

It's missing from your release notes, but Wear OS companion app has finally got it's facelift in 6.10.2, with way clearer layout and fixed scrolling issues. well done, but add it do the changelog