gpg script in cron failed with "stdin must be a tty"

Carl L. Gilbert
Fri Aug 8 16:14:03 2003

Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2003-08-07 at 13:07, Mike Hsu wrote:
> A simple gpg script with no passphrase needed:
> gpg --output junk.txt --decrypt junk2.gpg
> runs OK in bash but fails in cron job.

cron uses bash.  You mean it runs OK while you are logged in, but fails
when you attempt to do it without being logged in.

> I get the following message in mail:
> stdin must be a tty

That error message is probably incorrect.

> How can I fix this?
> Mike Hsu (
> _______________________________________________
> Gnupg-users mailing list
Thank you,

CL Gilbert
"Then said I, Wisdom [is] better than strength: nevertheless the poor
man's wisdom [is] despised, and his words are not heard." Ecclesiastes

GnuPG Key Fingerprint:
82A6 8893 C2A1 F64E A9AD  19AE 55B2 4CD7 80D2 0A2D
GNU Privacy Guard (Encryption and Digital

Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

Version: GnuPG v1.2.2 (GNU/Linux)