Test this in CRON and let me know what happens:
=====cut here=====
#!/bin/bash
cd /tmp
cat >/tmp/.pass <<EOF
password
EOF
cat thefile | gpg -z9 --no-version --textmode --comment "JLF Sends..."
--batch --yes --passphrase-fd 2 -a -v -v -c 2<.pass
=====cut here=====
--
Jean L. Francois - JLF SEnds...
- Enterprise OS (LINUX) Load Development and Integration Engineering
Group
- Linux Counter Registered User #8863 1994-12-13 06:39:24
The decline of any democracy begins when the plebs,
recognizing they have the power to vote themselves bread and circuses,
go ahead and vote themselves bread and circuses. --Robert A. Heinlein
>-----Original Message-----
>From: plug-discuss-admin@lists.plug.phoenix.az.us
>[mailto:plug-discuss-admin@lists.plug.phoenix.az.us] On Behalf
>Of Lynn David Newton
>Sent: Friday, September 03, 2004 1:39 PM
>To: PLUG
>Subject: GNUGPG problem
>
>
>
>Esteemed experts,
>
>Any GNUPG experts out there?
>
>I've acquired the task of encrypting a file with gpg.
>This must take place within a script that is run as a
>cron process.
>
>The script I've created works perfectly when run from a
>command line. When run as a cron process, it acts as
>though the line that creates the encrypted file is
>simply skipped over. There is no trace of any output,
>error or otherwise. The .gpg file is never created.
>
>Sparing you the details of the script, the essence of
>what it does is this:
>
>echo $(</path/to/file) | gpg --passphrase-fd=0 --symmetric thefile
>
>There's lots of stuff before and after. Never mind what
>it does. It all works.
>
>Yes, I'm aware that the man page says don't use
>--passphrase-fd if it can be avoided. Assume that it
>can't be.
>
>I've tried *everything* I know for the past two days to
>try to figure out what's going on, to no avail. The
>only thing I can guess is that because it runs as a
>cron process, cron does something funny with the file
>descriptors. Or else cron is possessed by an evil spirit.
>
>I tried also --passphrase-fd=- in case file descriptor
>zero is explicitly somehow something different from
>stdin at that point, though I don't see how it could
>be. Didn't work. Grasping at straws at this point.
>
>Help!? Many thanks.
>
>--
>Lynn David Newton
>Phoenix, AZ
> ... a.k.a. clueless on a Friday morning
>---------------------------------------------------
>PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>To subscribe, unsubscribe, or to change you mail settings:
>http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)