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

[Carl L. Gilbert]

--=-tMP+iV/z+g+iLq/rkcJr
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
>=20
> runs OK in bash but fails in cron job.
>=20

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
>=20

That error message is probably incorrect.

> How can I fix this?
>=20
> Mike Hsu (mhsu@nglm.com)
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users@gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
--=20
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
9:16

GnuPG Key Fingerprint:
82A6 8893 C2A1 F64E A9AD  19AE 55B2 4CD7 80D2 0A2D
GNU Privacy Guard http://www.gnupg.org (Encryption and Digital
Signatures)

--=-tMP+iV/z+g+iLq/rkcJr
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/M7CLVbJM14DSCi0RAgE4AKC9KsTZbCNFGW4AU49BnJxdD+ibvACcC0kC
oEo0PPwP0p3f6EPrQSucgGA=
=1bGi
-----END PGP SIGNATURE-----

--=-tMP+iV/z+g+iLq/rkcJr--