Commit 3dea9208 authored by epriestley's avatar epriestley
Browse files

Fix an issue where passphrase-protected private keys were stored without discarding passphrases

Ref T13454. See <>.

After changes to distinguish between invalid and passphrase-protected keys, SSH private key management code incorrectly uses "-y ..." ("print public key") when it means "-p ..." ("modify input file, removing passphrase"). This results in the command having no effect, and Passphrase stores the raw input credential, not the stripped version.

We can't recover the keys because we don't store the passphrase, so no migration here is really possible. (We could add more code to detect this case, but it's presumably rare.)

Also, correct the behavior of the "Show Public Key" action: this is available for users who can see the credential and does not require edit permission.

Test Plan:
  - Created a new credential with a passphrase, then showed the public key.

Maniphest Tasks: T13006, T13454

Differential Revision:
parent df139f04
......@@ -80,7 +80,7 @@ final class PhabricatorAuthSSHPrivateKey extends Phobject {
if (!$err) {
if ($passphrase) {
'ssh-keygen -y -P %P -N %s -f %R',
'ssh-keygen -p -P %P -N %s -f %R',
......@@ -154,7 +154,6 @@ final class PassphraseCredentialViewController extends PassphraseController {
->setName(pht('Show Public Key'))
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment