Skip to content
This repository was archived by the owner on Mar 1, 2025. It is now read-only.

Commit 8a90032

Browse files
committed
Better notes about 1Password accounts in readme
1 parent 287f4cf commit 8a90032

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

README.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Utilities for storing and loading SSH keys with 1Password. Use a unique key for
1111

1212
These executables (`op` and `jq`) must be available on `PATH`.
1313

14-
You should run `op signin` at least once before using these scripts in order to cache your basic account information. See `op signin --help` for more information.
14+
You should run `op signin` at least once before using these scripts in order to cache your basic account information. See ["1Password Accounts"](#1password-accounts) for more information.
1515

1616
[1password-cli]: https://support.1password.com/command-line-getting-started/
1717
[jq]: https://stedolan.github.io/jq/
@@ -71,9 +71,13 @@ The location where keys and the temporary SSH config file are stored is given by
7171

7272
Within this location, the SSH config file is stored in `ssh_config`, and key pairs are stored in the `keys` subdirectory according to the UUID of their associated 1Password item.
7373

74-
## Using a different 1Password account
74+
## 1Password Accounts
7575

76-
Normally, running `op signin` at least once before using these scripts caches some of your 1Password account details in your home directory. This cached account is what this script will attempt to log in as by default. If you would like to use a different account for this script than the cached one, you can pass additional arguments to `op-ssh-fetch` and `op-ssh-create` which will be passed through directly to `op signin`. For example:
76+
Normally, running `op signin` at least once before using these scripts caches some of your 1Password account details in your home directory. This cached account is what this script will attempt to log in as by default. The full invocation may look something like this:
77+
78+
eval $(op signin my.1password.com [email protected] YOUR-SECRET-KEY)
79+
80+
If you would like to use a different account for this script than the cached one, you can pass additional arguments to `op-ssh-fetch` and `op-ssh-create` which will be passed through directly to `op signin`. For example:
7781

7882
op-ssh-fetch my.1password.com [email protected] YOUR-SECRET-KEY
7983

0 commit comments

Comments
 (0)