After the update it asked me for my GPG password again (it was saved before) and no matter what I enter, it fails to decrypt the key. I made sure the entered password is indeed correct.

Hi folks,

i am getting this error at trying to clone a git repo via ssh-key which i had uploaded:

Failed to clone repository .... Underlying error: Failed to start SSH session: Unable to exchange encryption keys

Does anyone here have a tip for me?

thanks

hartmut

Tested environments

• the beta version pass for iOS 0.12.0 (8) from testflight on iOS 14.4 (has this issue)
• the stable version pass for iOS 0.11.0 (11) from App Store on iOS 14.4 (has this issue)
• iOS 11.4 running Pass for iOS 0.9.0 (21) (works without this issue)

Steps to reproduce:

1. Set up a remote https git repo at gitlab via username and password (id_rsa 4096 key and id_ed25519 keys don't seem to be supported... but that is irrelevant to this).
2. Also exported the gpg keys via local server URL (using ruby -run -e httpd . -p 8080 and then http://<local ip>:8080/a.asc etc.). The import seemed fine, except it warned me not to use http but use https instead.
3. Then I clicked on one pass item in the Passwords menu. It asked for the PGP secret key Passphrase.
4. I filled in the password correctly (I tried 20+ times, even via a bluetooth keyboard); the same password unlocks my gpg on my computer fine).

Result

However, once I finish inserting my password and click OK, I get:

Cannot show password
gopengp: unable to add locked key to a keyring

Expected results:

The item opens, and shows the item view, where I could copy or show the password.

Things I have tried to fix/rule out:

• Guessing it may have been talking about iOS keychain, I checked my keychain. It is synced fine with iCloud, and works fine.
• Tried several times after deleting the GPG key and several ways to export the gpg key (via key id, or the email etc.).
• Also tried importing via iTunes (dropped the keys into the Pass Beta app then clicked iTunes import which showed a prompt saying "success").
• Tried deleting the app (along with its data) and completely setting up afresh.

None of those worked. Not sure what went wrong here.

Let me know what more info I can provide to help debug or resolve this issue with better documentation.

Not sure if it is relevant, but I was using an old iOS 11.4 running Pass for iOS 0.9.0 (21) before which worked (and still works) fine; I just migrated (via backing up to iTunes, ehm, it is called Music now and works directly from within Finder) from that to iOS 14.4.

I am running a git server on my NAS that hosts a copy of my passwords repo. My NAS uses a custom port for ssh (2200) and i cannot seem to get the repo to be cloned in the app. I've tried specifying the port in the URL (ssh://my-nas.local:2200/git/passwords.git) and this fails as well. Since the instructions and error message i'm presented with (failed to clone repo) are not very much help; is there any information about this on setup?

Hi,

thanks for your great work on Pass for iOS.

I noticed a problem with the application on my iPhone 6 that was recently updated to iOS 10.3.1. After cloning my Pass data through SSH, the application instantly crashes and fails to start again unless deleted. I'm using password-based authentication for SSH and a self hosted, bare git repository (which was worked fine before).

I'm also using the latest TestFlight build.

These changes eliminate the need for glue code, upgrade to the new GopenPGP API and improve error handling. The code could probably be a bit cleaner (I'm not a Swift dev so I don't know what would be the idiomatically correct way) but it works. The fix for #287 is also implemented so IDs are displayed correctly.

Hi,

I’ve just upgraded to v0.4.0 (4) on my iPhone and discovered an error that my Git remote URL does not seem to work anymore. I’m using the SSH variant: ssh://git@host/pass.git with an SSH key.

When I try to clone, I get an error message: Faild to clone repository from ssh://git@host/pass.git to file:///... Underlying error: unsupported URL protocol.

Maybe this has something to do with the updated dependencies? Nothing has changed at the server side, as the pass CLI is working normally.

Please let me know, if I can provide further information to help solving this bug. For now I leave the state as is (broken).

@apfohl

Environment

iOS Version: 10.2.1 (14D27) Pass for iOS: 0.2 (24)

Steps

1. Export PGP public and private key (4096 RSA key generated by GnuPG) in ASCII-Armor format using the instructions:

gpg --export -a <keyname>
gpg --export-secret-keys -a <keyname>

2. Paste the key into the two edit controls of "PGP Key" window

3. Press "Save" in the upper right corner

4. Enter passphrase in the "PassPhrase" dialog, and press "OK", then press "Save"

Expected Result

The PGP key is saved

Got Result

The program crashed

Crash Log

pass_ios_crash_log.txt

Since updating to 0.8.0 (2), I've tried 0.8.0 (3) as well, I can't decrypt any secrets.

Found this due to not being able to AutoFill any passwords. Later found that as soon as I try to decrypt a secret (click on it in the Pass app) the screen goes black and Pass crashes.

Reverting to 0.7.0 (15) everything is working again.

Phone iPhone SE iOS version 12.4.1 (16G102) Pass 0.8.0 (2) and 0.8.0 (3)

Happy to provide any more information if needed.

The current methods for setting PGP key are insufficient.

1. Linux users do not have iTunes, so iTunes file sharing is unavailable.
2. I personally couldn't get asc-key-to-qr-code-gif working. It produced gifs, but Pass wouldn't recognize them.
3. Not everyone has a domain with which to host HTTPS (some people use their home computer and local network as the Git server). Plus, I know gpg-serve-key has several protections to make sure it's not a problem, but letting the keys be accessible on the web just seems stupid to me.

I suggest at least the following two methods:

1. Allow getting the key from Files, so that users can get the key from wherever they want. Plus Files now allows you to access smb shares, so they could be accessed that way too.
2. SSH. We use SSH for Git, so we should be able to use SSH to SCP the key from the server.
3. Non-secure HTTP. When on a trusted WiFi network like a home network, this is acceptable.

When selecting passwords from the keyboard to auto insert into the username and password, keyboard does not appear. You don't have the ability to type or search for a password.

The only way you can type to search is to open the PASS app directly then copy the password and then go back to the app you need it for.

I'd like to propose a PR that adds support for command chaining for Yubikeys, which should resolve some issues reported in #42 in particular "Failed to execute decipher" when using large keys.

These changes, however will force dropping support for iOS 12.x and moving to 13.0 as a minimum supported version, due to use of async/await, etc.

Hi 🤗

I wanted to ask if there is a way to fund development of features. Specifically I would be interested in support for passage instead of pass as I would like to use age instead of gpg. Unfortunately I'm not an iOS developer, just a regular user. So I'd like to contribute financially 💰 Also, I have no idea how much effort this would take. So feel free to dismiss this feature request Thank you for this great app! 😊

Cheers, David

apologies if there's already an issue for this, i wasn't able to find one .

i'd like to be able to use a local repo, like one synced with mobius (syncthing) not with git

is this possible ?

I am trying to get Passforios set up for my password store which is hosted in AWS CodeCommit.

I have it working OK with pass locally, but when I try and set it up in passforios I get the above error. Does anyone have any ideas ?

A while ago I changed my email address for my PayPal login, and consequently updated the entry in Pass as well.

However, whenever I go to PayPal to login, it still suggests the old email address. No such entry exists anymore, and I already deleted the website data for PayPal from Safari. What else would be caching this?

Also, if I select the key icon to show other logins, it does list both the wrong and new one, but it lists them all dozens of times.

Choosing the correct one here works for this particular login, but next time it'll suggest the wrong one again.