We operate PRM via another controlling process (a web app) that does not have access to tty. However, without access to tty, gpg fails, and the release is not signed - leading to all kinds of problems. This was also experienced here, it seems:
An unprotected key doesn't seem to mind if you pass it the wrong password, so it's possible to eliminate the third branch entirely, but that seems sloppy.
We operate
PRM
via another controlling process (a web app) that does not have access to tty. However, without access totty
, gpg fails, and the release is not signed - leading to all kinds of problems. This was also experienced here, it seems:https://github.com/dnbert/prm/issues/69
While adding the tty flag, we found that though
gpg_passphrase
is set tofalse
byClamp
, the logic seems to be predicated on it beingnil
.Result of a prm invocation without a passphrase:
An unprotected key doesn't seem to mind if you pass it the wrong password, so it's possible to eliminate the third branch entirely, but that seems sloppy.