Package Details: 1password 8.10.72-27

Git Clone URL: https://aur.archlinux.org/1password.git (read-only, click to copy)
Package Base: 1password
Description: Password manager and secure wallet
Upstream URL: https://1password.com
Keywords: manager onepassword password
Licenses: LicenseRef-1Password-Proprietary
Conflicts: 1password-beta, 1password-beta-bin
Submitter: rew1red
Maintainer: 1Password
Last Packager: 1Password
Votes: 112
Popularity: 1.09
First Submitted: 2020-08-04 23:11 (UTC)
Last Updated: 2025-04-15 17:42 (UTC)

Pinned Comments

1Password commented on 2021-07-27 21:07 (UTC) (edited on 2021-09-13 17:52 (UTC) by 1Password)

1Password for Arch Linux - Stable

The source is signed with the GPG key 3FEF9748469ADBE15DA7CA80AC2D62742012EA22 and can be seen on the install-linux guide.

Getting Started

Our getting started guide can be found at https://support.1password.com/install-linux/#arch-linux

Support

Our Linux support discussion is available at https://1password.community/categories/linux

Beta Releases

Our beta releases can be found at 1password-beta. Beta releases are more likely to have regressions than our stable releases.

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

whynothugo commented on 2021-11-27 02:53 (UTC)

You don't need to chmod the helper via the install script (e.g.: at install time), you can just do this when packaging.

Here's a diff:

diff --git a/1password.install b/1password.install
index e752514..156badc 100755
--- a/1password.install
+++ b/1password.install
@@ -9,12 +9,6 @@ app_group_exists() {
     fi
 }

-set_chromesandbox_permissions() {
-    # chrome-sandbox requires the setuid bit to be specifically set.
-    # See https://github.com/electron/electron/issues/17972
-    chmod 4755 /opt/1Password/chrome-sandbox
-}
-
 setup_browser_helper() {
     # Setup the Core App Integration helper binary with the correct permissions and group
     HELPER_PATH="/opt/1Password/1Password-KeyringHelper"
@@ -46,12 +40,10 @@ pre_upgrade() {
 }

 post_install() {
-    set_chromesandbox_permissions
     setup_browser_helper
 }

 post_upgrade() {
-    set_chromesandbox_permissions
     setup_browser_helper
 }

diff --git a/PKGBUILD b/PKGBUILD
index 2e5a93e..680429f 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -46,4 +46,8 @@ package() {
     # Symlink /usr/bin executable to opt
     install -dm0755 "${pkgdir}"/usr/bin
     ln -s /opt/1Password/1password "${pkgdir}"/usr/bin/1password
+
+    # chrome-sandbox requires the setuid bit to be specifically set.
+    # See https://github.com/electron/electron/issues/17972
+    chmod 4755 "${pkgdir}"/opt/1Password/chrome-sandbox
 }

I noticed there's some gitlab CI set up in the repo. Is there somewhere better to send an MR instead of a patch here?

tonkku107 commented on 2021-10-22 21:24 (UTC)

Please stop flagging this package as out-of-date for beta releases. If you want the beta versions go to 1password-beta

seaboard_hiccoug commented on 2021-09-05 22:28 (UTC)

It would be great to get an arm Linux build for rPi and Pinebook users. Thank you for all the great work!

1Password commented on 2021-07-27 21:07 (UTC) (edited on 2021-09-13 17:52 (UTC) by 1Password)

1Password for Arch Linux - Stable

The source is signed with the GPG key 3FEF9748469ADBE15DA7CA80AC2D62742012EA22 and can be seen on the install-linux guide.

Getting Started

Our getting started guide can be found at https://support.1password.com/install-linux/#arch-linux

Support

Our Linux support discussion is available at https://1password.community/categories/linux

Beta Releases

Our beta releases can be found at 1password-beta. Beta releases are more likely to have regressions than our stable releases.

jcf commented on 2021-07-07 08:50 (UTC)

I'm seeing a .gitlab-ci.yml file in this package, which I'm guessing isn't supposed to make it in? It contains an include statement that references dev/core/1password-archlinux-aur-ci…

thiagowfx commented on 2021-06-28 21:54 (UTC)

1password support page with signature now lives here: https://support.1password.com/command-line-getting-started/

Dreadman commented on 2021-06-19 10:34 (UTC)

I think this is flagged out-of-date incorrectly. The link provided in the flag comment refers to a beta release, while this package probably tracks the stable releases.

kshlm commented on 2021-04-14 20:59 (UTC)

You know what this seems to have been only an issue with Brave-beta. Everything else is just working without my manifests. Also, I may have been using the non-beta extension in Chromium at first, which doesn't work with the native app, so I may have mistakenly believed it wasn't working too.

It appears that the 1Password app creates the manifests in the browser config directories it finds on startup. I didn't have Brave installed, but had a config directory lying around from a previous install, and it had the manifest created in the users config directory.

kshlm commented on 2021-04-14 20:38 (UTC) (edited on 2021-04-14 20:41 (UTC) by kshlm)

I mainly use Chromium and Brave-beta. I only today realized that native app integration was supposed to be enabled on Linux, and got about finding why it wasn't working for me.

The integration started working after I added these manifests, in Chromium and Brave. I only checked Chrome afterwards, and assumed it wouldn't have been working before.

Aranom commented on 2021-04-14 20:34 (UTC)

That's weird, I didn't have to do anything for 1password to integrate with the google-chrome-stable package.

Manifests can be written in user directory, which the app should do (haven't checked myself: did you enable browser integration in the settings?)

« First ‹ Previous 1 2 3 4 5 Next › Last »