-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 13 Nov 2000, Bill Carlson wrote:
> If you're a pine user like myself and want to upgrade to the latest
> 4.30 pine (which you should for the security fix), you'll find the update
> RPM wants a bunch of things installed that you probably don't want.
Has anybody found that it seems to break filters? For example, I have a
gpg-sign filter defined:
#!/usr/local/bin/bash
cat /dev/stdin ~/.work_signature | gpg --clearsign
which worked perfectly until I upgraded to 4.30. Now, when this filter
runs, it results in a blank message (ie. had I not used an older version
of Pine to send this message to this list, my act of signing my message
would have resulted in thousands of redhat-list members potentially
getting violently angry at getting a blank message from me).
I'd sort of like to fix it. Any ideas?
- --------------< LINUX: The choice of a GNU generation. >--------------
Steve Frampton <[EMAIL PROTECTED]> interQ (Japan), Inc.
Systems Administrator/Software Developer http://www.interq.or.jp/
GNU Privacy Guard ID: D055EBC5 (see http://www.gnupg.org for details)
GNU-PG Fingerprint: EEFB F03D 29B6 07E8 AF73 EF6A 9A72 F1F5 D055 EBC5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (SunOS)
Comment: For info see http://www.gnupg.org
iD8DBQE6E6/smnLx9dBV68URAhzsAKCBnf0dGmskzxU3exESIWWfluozDgCghKCU
06lyPjWg9UVp7AEJq1ccfIU=
=RSHA
-----END PGP SIGNATURE-----
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
