Protect what matters – even after you're gone. Make a plan for your digital legacy today.
linux
16 TopicsAdministrators, get a sneak peek at the new sidebar
Starting this month, we’re rolling out a redesigned admin sidebar to create a more consistent and intuitive experience across 1Password products. We’d love your feedback to make sure we’re reaching that goal. Note that this change will only apply to administrators using 1Password for business. What’s changing? Sidebar location: The sidebar has been moved from the right side of the screen to the left side so it's more consistent with the 1Password apps. Improved navigation: Each section of the sidebar now has an icon and we've improved the organization of the pages with tabs. Product switcher: If your team also uses Device Trust or SaaS Manager, you can easily switch to those products from the menu in the top left. What’s the timeline? April 23–May 7: Admins will see an in-product banner inviting you to try the updated sidebar. May 7: The new sidebar becomes the default experience for all accounts. Can we switch back? Yes – if your team prefers to stick with the existing sidebar for now, you can revert to the old design through your settings during the early access period. Here’s how: Select your account name in the top right, then select Manage Account. Toggle “Admin console design updates” off. Please reply below with any thoughts, ideas, or questions! Your feedback is invaluable in helping us continue to improve 1Password.199Views6likes2Commentsdebsig package signing issue for 1password & 1password-cli
Problem: I have already raised this issue by email (no response from 1password yet), and BitBot has given this matter reference CKQ-37366-878. 1Password uses the weak, deprecated algorithm SHA1, with debsig, to sign its Debian packages (this affects both 1password [gui app package], and 1password-cli, each in their deb package form). Way back in Nov-2021, debsig v0.24 deprecated SHA1 as an acceptable way to sign packages. This is because a practical collision attack for SHA1 was first demonstrated in 2017. debsig release announcement: https://lists.debian.org/debian-dpkg/2021/11/msg00006.html#:~:text=*%20reject%20weak%20ripemd160%20and%20sha1%20algorithms Any Ubuntu or Debian distro using debsig >= v0.24 will by default not verify 1password or 1password-cli packages, due to the use of weak SHA1 packages. To further prove it is use of weak SHA1 algo for signing that is root cause of debsig-verify failing, and nothing else, you can put "allow-weak-digest-algos" (without quotes) into /etc/gnupg/gpg.conf and then debsig-verify command will confirm that latest 1password or 1password-gui deb package was signed appropriately in "_gpgorigin" file. Yes, an SHA1 collision is still hard, and so SHA1 signing is still better than nothing, and Debian packages is a smaller subset of an already small linux user base for 1password, but it still disappoints me that 1password appears not on top of ensuring all of it crypto algorithm use, are strong, secure, not depricated ones! It makes me wonder and worry where else depricated crypto cyphers are in use, and should I switch to something with more open source code that I can check for myself, like Proton or Bitwarden. Fix required: Please restore my faith in 1password by switching your signing algorithm for all Debian packages, from using SHA 1 (digest algo 2) to SHA 256 (digest algo 8), or even better, SHA 512 (digest algo 10), for debsig. This does not need to change the keys you use, and changes nothing about the underlying packages for 1password or 1password-cli. It is just a change to the deb packages. Steps to reproduce and analyse the issue: (1) Fire up an Ubuntu or Debian instance with debsig >= v0.24 (I used Debian 13 Trixie) (2) wget -O "1password-latest.deb" https://downloads.1password.com/linux/debian/amd64/stable/1password-latest.deb This gets you a suitable package to test the problem on. (3) debsig-verify -d 1password-latest.deb This runs debsig-verify, with debug output visible, on the just downloaded deb package. You can see the signature failure message on the final output line. Higher you can see complaints about an invalid digest algorithm as the root cause (4) Add "allow-weak-digest-algos" (without quotes) into /etc/gnupg/gpg.conf and then re-run the debsig-verify command from step 3 above. Now that we move away from default secure config to reject old, weak depriecated algorithms, such as SHA1, the 1password deb package successfully shows as signed. You could keep all the same keys, and just switch the signing algorithm used by debsig, to SHA256 or even better SHA512 (SHA512 is 64-bit words, so no slower on 64-bit architectures than SHA256, but larger and more secure), and you would fix this problem. If you are still using SHA1 here, and had not noticed until user pointed it out, you should probably (re-)audit where else you are using weak, old, deprecated cyphers in your codebase too, as a good step to continuously improve 1password security!50Views0likes1CommentRequest for Zen Browser communication to app Support in 1Password (linux)
The 1Password browser extension cannot connect to the 1Password desktop application when using Zen Browser, despite native messaging being correctly configured. This results in fingerprint and other quality of life not working on Zen. The connection fails because 1Password's BrowserSupport binary rejects Zen as an "UnknownBrowser". - OS: Linux (Arch-based) - 1Password: Version 8.x (Linux desktop app) - Zen Browser: Version 1.16.3b (Firefox-based, using Gecko 143.0.4) - Extension ID: `{d634138d-c276-4fc8-924b-40a0ea21d284}` (1Password extension version 8.11.12.27) 1. : The native messaging host configuration (`com.1password.1password.json`) is correctly placed in all standard locations: - `~/.mozilla/native-messaging-hosts/` - `/usr/lib/mozilla/native-messaging-hosts/` - `~/.zen/native-messaging-hosts/` 2. When the 1Password extension in Zen attempts to connect, the BrowserSupport binary IS successfully invoked with the correct parameters. 3. **Failure Point**: The BrowserSupport binary immediately returns: ```json {"type":"Notification","content":{"type":"BrowserVerificationFailed","content":"UnknownBrowser"}} ``` Exit code: 1 4. The BrowserSupport binary appears to have a whitelist of supported browsers and doesn't recognize Zen Browser's identity, despite Zen being a Firefox-based browser. Please consider adding Zen Browser to the list of supported browsers in 1Password's BrowserSupport binary. The browser's application identifier is: - **Name**: Zen - **RemotingName**: zen - **Application ID**: `{ec8030f7-c20a-464f-9b0e-13a3a9e97384}` If you need any additional technical details or testing assistance for Zen Browser support, I'd be happy to help provide that information. NB! Fingerprint works fine on Firefox on the same machine. Just not on Zen, because apparently "unknown browser" on your side. Also I am not sure, but its possible same issue occurs on MacOS(too lazy to test)Solved55Views0likes4CommentsShow favorites on Quick Access
It would be a great feature to show the user's favorites on the Quick Access panel. Then you could press your keyboard shortcut and arrow down to the favorite you want to auto type. This was the flow I used to use with KeePassXC and it worked nicely. Additionally, a button below the favorites to browse the whole list of items would be nice. That way, if you didn't remember what you called something and you pressed the Quick Access key you could scroll and find it.53Views1like3CommentsFirefox & Chromium on Linux Issues with windows.cloud.microsoft
This has been annoying me so much lately I had to post something about it. When working in an azure virtual machine with a browser that has the 1Password extension enabled the extension is detecting a password event for some actions I do within the virtual machine which aren't password related. I'm working off Linux but I'm sure it would happen on a wintel box as well. Triggers for this behaviour I've encountered so far: Entering a UNC value into the file explorer address bar Entering a search term or URL into a browser address bar Entering text into a search provider like Bing As you can imagine this is pretty annoying when you're trying to get work done. If I could also suggest that if you are targetting MSPs you want to detect which username the user has picked when doing an auth with O365/Azure and give them the appropriate password, as they will have a LOT of O365 accounts.22Views0likes1CommentMissing agent.sock: 1Password on Arch Linux (AUR) Prevents CLI Desktop Integration
1Password CLI in Distrobox Container Can't Connect to Host App On CachyOS (an Arch-based distribution), the native 1Password desktop application installed from the AUR does not create the necessary agent.sock file and its containing directory for CLI integration. While the CLI on the host machine works, this missing socket makes it impossible to connect the CLI from inside a Distrobox (Ubuntu) container to the host's 1Password application. Steps to Reproduce: Install CachyOS. Install the 1password package via the recommended AUR method. Launch the 1Password desktop app, unlock it, and enable "Integrate with 1Password CLI" in the Developer settings. Install distrobox and podman. Attempt to create a new Ubuntu container with the 1Password socket directory mounted: distrobox create -n my-container -i ubuntu:22.04 --volume "$XDG_RUNTIME_DIR/1Password:$XDG_RUNTIME_DIR/1Password" Expected Behavior: The 1Password host application should create the socket directory at $XDG_RUNTIME_DIR/1Password containing agent.sock. The distrobox create command should succeed, and the op CLI inside the container should then be able to communicate with the host's 1Password app. Actual Behavior: The host application fails to create the socket directory. Checking for it results in an error: ls: cannot access '/run/user/1000/1Password': No such file or directory Consequently, the distrobox create command fails with the error: statfs /run/user/1000/1Password: no such file or directory. The CLI inside the container cannot be used with desktop app integration. System Details: Operating System: CachyOS (Arch-based) 1Password Version: 2.31.1 Installation Method: AUR CLI Version: 2.31.1 Container Image: Ubuntu (via Distrobox) Troubleshooting Steps Taken: Confirmed CLI integration is enabled in the app settings. Confirmed the CLI works correctly on the host machine itself. Performed a full system update and rebooted. Confirmed via pacman -Qi 1password that this is a native package, not a Flatpak or Snap. Searched the entire filesystem for agent.sock using the find command, and no relevant socket file was found.76Views0likes1Comment1Password linux install proxy fail
Hello, While installing 1Password on linux (Ubuntu 24.04), following the official guide (using .deb method here: https://support.1password.com/install-linux/#debian-or-ubuntu) and with a corporate proxy to access public internet, the installation fails at the end (1Password app configuration step): sudo apt upgrade Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Calcul de la mise à jour... Fait 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour. 1 partiellement installés ou enlevés. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] O Paramétrage de 1password (8.11.4) ... Installing the debian auto-update channel curl: (28) Failed to connect to downloads.1password.com port 443 after 300004 ms: Timeout was reached gpg: aucune donnée OpenPGP valable n'a été trouvée. dpkg: erreur de traitement du paquet 1password (--configure) : le sous-processus paquet 1password script post-installation installé a renvoyé un état de sortie d'erreur 2 Des erreurs ont été rencontrées pendant l'exécution : 1password E: Sub-process /usr/bin/dpkg returned an error code (1) My proxy is defined in the system configuration, variables HTTP|S_PROXY are set and I also have the proxy conf for apt in /etc/apt/apt.conf.d/proxy.confSolved80Views0likes3Comments1Password Linux desktop proxy
Hello, I've just installed latest version of 1Password Linux app on Ubuntu 24.04 on the computer of my company. I'm behind a corporate proxy, the proxy is already set in Ubuntu settings, and the env variables HTTP_PROXY / HTTPS_PROXY are correctly defined. But 1Password cannot connect to internet as soon as I am on the proxy, and I don't see Proxy settings in 1Password app. What am I missing ?49Views0likes1Comment1Password dev ressources vs IPO
Hello, since 2024, when 1Password started looking into/considered an IPO, i have the feeling all development ressources were focused solely on growing the userbase and everything else was deprioritized. For example: The terraform provider didn't get any updates (e.g. Ephemeral Values) Simple improvements are deep in the backlog: Collapsible tags Displaying the user on the "last edited" line Improvements for managing vaults/users in an enterprise context are missing: Admins still can delete Owners Vaults can be deleted by any admin without "four-eye-principle" ... There is no way to export vaults encrypted Maybe some ressources could be assigned to improvements instead of new features... /rant over243Views1like1CommentLinux Desktop Application hangs when logging in via MS Office365 SSO
Hello everyone, I am using 1Password for work to store the related Logins and things there. I would like to use the Linux Client on my Arch Linux machine. But the authentication through the MS Office365 on the desktop application hangs. I do the following to try to sign into 1password. Select "Sign In" Select "1password.eu" Enter my company e-mail and the respective sign-in address Select "Next" Select "Sign in with Microsoft" I see "Redirect Complete You may now close this page." in my browser I see in the 1Password Desktop Application the loading icon spinning and nothing happening. The authentication on the browser extension in Chromium works sometimes. Sometimes I have to kill all Chromium processes to make the authentication work. But I would like to fix the desktop application first. About my system: Linux kernel: 6.15.8-arch1-1 1Password version: 8.11.2 (installed via AUR: https://aur.archlinux.org/packages/1password) Desktop: SwayWM (Wayland) Command to start 1Password: 1password -ozone-platform=wayland -enable-features=WaylandWindowDecorations --disable-gpu --log trace How can this be fixed? Where can we start debugging? Best regards!Solved39Views0likes2Comments