Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Integration between Linux app and Snap Firefox
Some days ago it was released the support for Native Messaging (still experimental) with Snap Firefox. I checked, but the integration between Linux app and Snap Firefox still doesn't work. I was wondering if the integration uses Native Messaging or other way to implement, and if it is using other way, if it could be ported to use Native Messaging, so Linux app could work with Snap Firefox. We are discussing this matter here 1Password Version: 8.9.0~1.BETA Extension Version: 2.3.7 OS Version: Ubuntu Kinetic Browser:_ Firefox
New item login field already populated
Hi, When I create a new item in the Linux, Android and iOS 1Password apps, the login field is already populated with an email address and focus is set on the password field. How to change that? I would like it to be empty. It is especially annoying because in my case, it is filled with a an email address I am not using that often. This change of behavior seems to be relatively recent. Thanks for your help. Spacehog
1Password Shortcuts on Wayland
1Password is an application that works very well when users can invoke it from anywhere. Quick Access in particular is a feature that is meant to be invoked from anywhere on your desktop. However, as many of you know, the Wayland developers made a deliberate choice to not allow applications to set global shortcuts. To my knowledge, all Wayland implementations have continued to honor this choice. The reasoning is valid, though: global shortcuts make keyloggers trivial. 1Password can run as a native Wayland application, and defaults to XWayland. This, however, does not help since the primary desktop environment is itself Wayland. For a variety of reasons, we have provided command line options for several of the most useful 1Password commands. In this article, I'll describe how to use those options to set up global shortcuts for 1Password with both Gnome Shell and Sway. It is, fortunately, very easy. Gnome Shell For this example, I'm running Gnome Shell 40.4.0, Wayland mode, on Fedora Core 34. Start by finding Keyboard > Customize Shortcuts in your Settings application. Next, select Customize Shortcuts Your list of custom shortcuts may start empty, but you will want to get to something like this: Press the + button at the bottom to create a new shortcut, and you'll get a screen like this: As you create each shortcut, name each one in a way that makes sense to you. In the Command field, you will write a trivial script that invokes 1Password with the option that you want. Once you have created that invocation, set the keyboard shortcut as you desire. I recommend multiple key bindings that all work together. The following is the 1Password defaults set on other platforms, and on XOrg-based displays. Name Command Shortcut Open or Toggle 1Password 1password --toggle Ctrl + p Lock 1Password 1password --lock Ctrl + Shift + L Open Quick Access 1password --quick-access Ctrl + Shift + Space note: there is no default for Open or Toggle 1Password, so I made something up. Sway Sway does not have a GUI configurator, but instead does everything in the configuration file at ~/.config/sway/config . Fortunately, this is very easy to set up: bindsym Ctrl+Shift+l 1password --lock byndsym Ctrl+Shift+space exec 1password --quick-access KDE Plasma coming soon
We're the team behind 1Password’s latest product enhancements. Ask us anything! (Wednesday, February 12th)
Hey everyone! 👋 We're the team behind 1Password’s latest product enhancements. Ask us anything! We’ll be hosting an AMA right here on February 12th at 9AM PT / 12AM ET with 1P_MattG - 1Password’s Senior Director of Product, End User Experience. This round of product enhancements includes exciting updates like a smoother mobile experience, better item creation and navigation, new ways to stay secure, and much more. Starting today, you can RSVP to the AMA and drop your questions here in this thread, and then we’ll answer them live during the AMA on February 12th at 9AM PT / 12PM ET! We can’t wait to chat with you and kick off our first AMA in the new 1Password Community! Check out our blog to find out more about our new and improved features. EDIT: The AMA has now officially concluded. Thank you to everyone for taking the time to chat with us! If you have any follow-up questions or feedback, feel free to drop them here. This thread will remain open until February 14th, 2025, at 5:00 PM ET, so you still have time to continue the discussion. Thanks again for making our first AMA in the 1Password Community a great one! 💙 Our AMA Host Matt Grimes Senior Director of Product, End User Experience, 1Password
Add ARM version to default distributions (Asahi Linux)
Asahi Linux (the de-facto Linux distribution for Apple silicon Macs) https://asahilinux.org/fedora/, and Linux on ARM in general is increasing in popularity. However, installing 1Password on ARM-based Linux machines is still unnecessarily complicated compared to it's x86 counterpart. This is a request to add support for the ARM architecture directly to the https://support.1password.com/install-linux/#get-1password-for-linux, and especially Fedora (considering it's official status through Asahi Linux), rather than offering it as a separate distribution with an inferior user experience. Other vendors such as Microsoft are already shipping Electron-based apps (e.g. Visual Studio Code) with ARM bundled binaries. I've been a loyal customer and evangelist of 1Passport due to it's forward thinking approach in features, especially with great features that enhance the developer experience. And I am hoping that this remains true here. For more information, see https://1password.community/discussion/123176/1password-for-linux-aarch64-m1-for-linux on the forum. 1Password Version: 8.10 OS Version: Fedora Asahi RemixUsability Digest Dec. 2023: Improved autofill reliability, lock state, and item title generation
Hey folks! As 2023 is coming to an end, we hope all your holiday preparations are coming together well. I’m happy to say we have a few end of year gifts to unveil to start 2024 off strong! We’ve always been committed to making 1Password a more intuitive and easy product for you. Throughout this past year and moving into next, we have and will continue to raise the bar of our user experiences across the browser, desktop and mobile apps. When it comes to the 1Password Browser Extension, we’ve been making hundreds of improvements in the last couple of months to make your day-to-day lives with 1Password better. All of these updates are now live, and we can’t wait for you to try them! Check out our release notes here for a full list of everything that’s been improved. Otherwise, here are five of our favorite improvements we’ve made, brought to you by the developers who created them. Feel free to give us your feedback or suggestions on what you’d like to see next in the comments below. Cheers to the end of 2023, and we look forward to building a better product with you in 2024! Better Performance with Pending Chrome Update - Rudy Richter, Staff Developer Sometimes, the connection between the 1Password Browser Extension and desktop app stops and you’ll be required to unlock both separately until you perform a pending Chrome update. This can become quite annoying especially during the work day where updating Chrome isn’t at the top of your to-do list. This occurs because on macOS, there are two code signatures at work for any given application: an on-disk and an in-memory. When Chrome issues an update, it does an in-place update — it replaces its on-disk files directly while still running and relies on you relaunching the application to “update” the application. Until you restart Chrome, the on-disk and in-memory code signatures no longer match. In choosing a path forward for our signature check, we needed to weigh the risk of relying on the on-disk signature as a means of determining if we should trust Chrome when it's in this “updated but not yet restarted” state. Now, when Chrome is in a state where an update is pending, we will initially perform a dynamic check. When that fails, we will then do a static code signature check to see if that at least meets its designated requirements and that its code signature is intact before trusting it. This change will result in unlocking the extension and the desktop separately much less often. Improved Item Title Generation - Michael Carlyle, Junior Developer For some time, 1Password has had existing logic to determine the best title for an item when saving a new login from a website, but it hasn’t been without its limitations. The web is vast, and there’s no forced standard to which we can expect all web developers to adhere to 100% of the time. Previously, we looked at a combination of things when saving an item title via our browser extension, like the page title itself, domain, or capitalization of the page title. But this isn’t perfect. Now the 1Password browser extension has default item titles for the top 900+ sites online – no guesswork required. It turns out that the ability to craft titles given a list of domains is something AI is well suited for. We gave a large language model a prompt with our requirements, and it returned a nice JSON file that we could then work with directly in our Rust code that generates item titles. This brings you the benefits of better titles for the most popular websites like American Airlines (previously titled AA), improved international title support, and better differentiation for logins with different subdomains like Google. Offline Browser Extension Improvements - Chris Burgin, Senior Developer If you've ever experienced the frustration of an unreliable internet connection, you'll appreciate the offline improvements we've made to the 1Password Browser Extension. In the past, recognizing offline and online states posed a challenge, impacting the ability to save passwords after your connection was re-established. We now check network status more regularly ensuring we have the most up-to-date information. In addition, we also gracefully recover when you come back online. No longer will you be told that your password can not be saved while offline when you are, in fact, online. Improved Autofilling for Sites with Shadow DOM Elements - Darrell Roberts, Senior Developer We are pleased to announce that the 1Password Browser Extension will now recognize and autofill more efficiently on a larger number of sites that leverage Shadow DOMs. This will make sites like Reddit, CVS, Royal Caribbean and more perform like butter. But what was the issue previously? Web components are a set of technologies for creating reusable custom DOM elements when building a website. One of those technologies is the Shadow DOM. As the name suggests, elements inside the Shadow DOM are private and rendered separately from the main document DOM. Websites that have forms, input fields or any other element that could be autofilled defined inside a Shadow DOM would not be accessible to 1Password extension. This would result in the 1Password autofill menu not showing up when a user interacted with an input field. As a result, we would not be able to offer autofill suggestions and consequently were incapable of filling a user's desired 1Password item. To be able to work with sites that use Shadow DOMs, we had to augment and, in some areas, alter the way we would analyze the site to be able to include all Shadow DOMs that could be defined on the website. As of today, you should have a much easier time autofilling these types of pages. Improved Autofilling for Login Forms Using Focus Traps - Jeff Cleary, Staff Developer There has been a long-standing issue with “focus traps” on website login forms. These are implemented as accessibility improvements to help contain browser focus during login actions, but would cause 1Password to close before autofill actions could occur. Because of this, we explored several approaches to fix this issue. These fix ideas ran the gamut – from changing our autofill menu injection strategy to “listening to the listeners,” i.e. detecting when an unwelcome focus switch was about to happen and preventing it. A drawback that many of these ideas suffered from was adding additional complexity that could compete, and potentially interfere, with the logic and intent of the host website. In the end, a simpler solution presented itself: by preventing the default focus event on the mousedown action on our inline menu, we were able to perform the click handling logic and complete the autofill before the completion of the click event that ultimately triggers a focus change. This small change was enough to fix the issue for the vast majority of reported cases on sites like Disney, TikTok, ESPN, Walmart, Domino’s and a whole lot more - enjoy!
I can't start wayland-native version of 1Password.
When I try to run 1password with the well-known OzonePlatform, I get the following: ``` INFO 2023-08-07T22:51:44.006 ThreadId(14) [client:typescript] Client starting. INFO 2023-08-07T22:51:44.114 ThreadId(14) [1P:op-localization/src/lib.rs:227] system locale detected as 'en-US' INFO 2023-08-07T22:51:44.114 ThreadId(14) [1P:op-localization/src/lib.rs:253] selected translations for EN_US based on detected locale en-US INFO 2023-08-07T22:51:44.114 ThreadId(14) [status:op-app/src/app.rs:519] App::new(1Password for Linux/81009046 (EN_US), /$USER/.config/1Password/1password.sqlite) INFO 2023-08-07T22:51:44.117 ThreadId(14) [1P:data/op-db/src/db.rs:446] Table Integrity Check Succeeded INFO 2023-08-07T22:51:44.118 ThreadId(14) [1P:data/op-db/src/db.rs:462] DB Integrity Check Succeeded INFO 2023-08-07T22:51:44.118 ThreadId(14) [1P:data/op-db/src/db.rs:137] Starting DB at version: 29 INFO 2023-08-07T22:51:44.187 ThreadId(14) [1P:ssh/op-ssh-config/src/lib.rs:248] agent not configured INFO 2023-08-07T22:51:44.188 tokio-runtime-worker(ThreadId(9)) [1P:native-messaging/op-native-core-integration/src/lib.rs:281] Mute native core integration is waiting for Shared Lock State to be enabled INFO 2023-08-07T22:51:44.189 tokio-runtime-worker(ThreadId(9)) [1P:ssh/op-agent-controller/src/desktop.rs:433] Starting filesystem watcher for SSH agent configuration directories... ERROR 2023-08-07T22:51:44.189 tokio-runtime-worker(ThreadId(9)) [1P:/builds/dev/core/core/ssh/op-agent-controller/src/desktop.rs:434] Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }) ERROR 2023-08-07T22:51:44.209 tokio-runtime-worker(ThreadId(1)) [1P:op-global-shortcuts/src/lib.rs:69] AppError at /builds/dev/core/core/op-global-shortcuts/src/node.rs:62:6 binding shortcut Caused by: BindRefused Stack backtrace: 0: op_global_shortcuts::node::bind::{{closure}} 1: op_executor::spawn_no_span::{{closure}} 2: tokio::loom::std::unsafe_cell::UnsafeCell ::with_mut 3: std::panicking::try 4: tokio::runtime::task::harness::Harness ::poll 5: tokio::runtime::scheduler::multi_thread::worker::Context::run_task 6: tokio::runtime::scheduler::multi_thread::worker::Context::run 7: tokio::macros::scoped_tls::ScopedKey ::set 8: tokio::runtime::scheduler::multi_thread::worker::run 9: tokio::loom::std::unsafe_cell::UnsafeCell ::with_mut 10: std::panicking::try 11: tokio::runtime::task::harness::Harness ::poll 12: tokio::runtime::blocking::pool::Inner::run 13: std::sys_common::backtrace::__rust_begin_short_backtrace 14: core::ops::function::FnOnce::call_once{{vtable.shim}} 15: alloc::boxed::Box<F,A as core::ops::function::FnOnce >::call_once at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/alloc/src/boxed.rs:1973:9 alloc::boxed::Box<F,A as core::ops::function::FnOnce >::call_once at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/alloc/src/boxed.rs:1973:9 std::sys::unix::thread::Thread::new::thread_start at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/std/src/sys/unix/thread.rs:108:17 16: 17: ERROR 2023-08-07T22:51:44.209 tokio-runtime-worker(ThreadId(10)) [1P:op-global-shortcuts/src/lib.rs:69] AppError at /builds/dev/core/core/op-global-shortcuts/src/node.rs:62:6 binding shortcut Caused by: BindRefused Stack backtrace: 0: op_global_shortcuts::node::bind::{{closure}} 1: op_executor::spawn_no_span::{{closure}} 2: tokio::loom::std::unsafe_cell::UnsafeCell ::with_mut 3: std::panicking::try 4: tokio::runtime::task::harness::Harness ::poll 5: tokio::runtime::scheduler::multi_thread::worker::Context::run_task 6: tokio::runtime::scheduler::multi_thread::worker::Context::run 7: tokio::macros::scoped_tls::ScopedKey ::set 8: tokio::runtime::scheduler::multi_thread::worker::run 9: tokio::loom::std::unsafe_cell::UnsafeCell ::with_mut 10: std::panicking::try 11: tokio::runtime::task::harness::Harness ::poll 12: tokio::runtime::blocking::pool::Inner::run 13: std::sys_common::backtrace::__rust_begin_short_backtrace 14: core::ops::function::FnOnce::call_once{{vtable.shim}} 15: alloc::boxed::Box<F,A as core::ops::function::FnOnce >::call_once at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/alloc/src/boxed.rs:1973:9 alloc::boxed::Box<F,A as core::ops::function::FnOnce >::call_once at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/alloc/src/boxed.rs:1973:9 std::sys::unix::thread::Thread::new::thread_start at /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/std/src/sys/unix/thread.rs:108:17 16: 17: INFO 2023-08-07T22:51:44.479 invocation_loop(ThreadId(21)) [1P:op-app/src/app/backend/lock_screen.rs:72] System unlock is enabled: true INFO 2023-08-07T22:51:44.487 tokio-runtime-worker(ThreadId(10)) [1P:op-app/src/app/backend/lock_screen.rs:88] Sys auth status NotSetup ``` X11 version (via Xwayland) works fine. What should I do to get a wayland-native version running? 1Password Version: 8.10.9 Extension Version: Not Provided OS Version: Not Provided Browser: Not Provided
