-
-
Notifications
You must be signed in to change notification settings - Fork 103
Home
Welcome to the Pass for iOS wiki!
Table of Contents
Before using Pass for iOS, please make sure that you have your "password store" set up properly. To set up your "password store", please refer to the official Password Store homepage, or our Quick-start guide for pass.
- Git repository URL:
https://gitlab.com/passforios-demo/demo.git
- Username:
passforios-demo
- Supported authentication Method: Password, SSH Keys
- Git repository URL:
ssh://git@gitlab.com/passforios-demo/demo.git
(original isgit@gitlab.com:passforios-demo/demo.git
)- remember to include username in the url
- remember to change ":" to "/"
- Username:
git
- Supported authentication Method: SSH Keys
The valid SSH URL should be ssh://server:port/url/to/repository.git
(ssh://github.com:22/mssun/pass.git
) and the username should be put in the next field under URL (e.g., git).
There are various ways to set up PGP keys.
First, upload your keys to a temporary server. Make sure the uploaded key can be accessed by https connection (e.g., test via wget
). Then, fill in URLs for your public and private keys, tap "Save" and fill in your passphrase. Finally, remember to remove the key from the server. Here goes one quick example:
$ gpg --export -a D4763C61 > key.pub
$ gpg --export-secret-keys -a D4763C61 > key
$ scp key.pub key yourtemporaryserver
$ wget https://...yourtemporaryserver.../key # make sure the key can be accessed by https connection
$ wget https://...yourtemporaryserver.../key.pub
Adding PGP key in ASCII armored format is supported. Just copy and paste. Here are some example codes to generate the ASCII-armored key.
$ gpg --export -a D4763C61 # copy to the app
$ gpg --export-secret-keys -a D4763C61 # copy to the app
You may also use iTunes file sharing function to upload your keys with names gpg_key.pub
and gpg_key
to the document root directory. The app will automatically use the keys for encryption and decryption.
Go to the "Passwords" tab in Pass for iOS, pull down to sync your passwords with the remote git (git pull
).
Pass for iOS provides support for Time-based One-time password (TOTP) and HMAC-based one-time password (HOTP). It is compatible with password entries (files) generated by pass-otp, a pass extension for managing one-time-password (OTP) tokens. Pass for iOS generates TOTP/HOTP for a password entry if all related fields are found.
To generate one-time passwords for TOTP tokens, the password entry should contain fields otp_secret
and otp_type
. And the value for otp_type
should be totp
(case insensitive). An example (decrypted) TOTP password entry is as follows.
otp_secret: AAAAAAAAAAAAAAAAAAAAA
otp_type: totp
otp_algorithm: sha1
otp_period: 30
otp_digits: 6
These lines could be in any order. It is ok if there are other none-related lines. Fields otp_algorithm
(case insensitive), otp_period
, and otp_digits
are optional. Their default values are sha1
, 30
(seconds), and 6
(digits), respectively.
To generate one-time passwords for HOTP tokens, the password entry should contain fields otp_secret
, otp_counter
, and otp_type
. And the value for otp_type
should be htop
(case insensitive). An example (decrypted) HOTP password entry is as follows.
otp_secret: AAAAAAAAAAAAAAAAAAAAA
otp_type: hotp
otp_counter: 1
otp_digits: 6
These lines could be in any order. It is ok if there are other none-related lines. Fields otp_algorithm
(case insensitive) and otp_digits
are optional. Their default values are sha1
and 6
(digits), respectively. (For a new HTOP password, if you do not know otp_counter
, it is probably 1
.)
Currently, to insert a new TOTP/HOTP entry via Pass for iOS, user have to manually type all mandatory fields. A better UI is on its way (e.g., inserting entries by scanning QR codes), stay tuned. :-)
Table of contents generated with markdown-toc.