Bug 24902 - pine's filters fail to properly encrypt mail sent to multiple recipients (using gpg)
pine's filters fail to properly encrypt mail sent to multiple recipients (usi...
Status: CLOSED DUPLICATE of bug 21271
Product: Red Hat Linux
Classification: Retired
Component: pine (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-01-24 21:18 EST by Stiphane Doyon
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-01-24 21:18:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2001:042 high SHIPPED_LIVE : Updated pine packages available 2001-03-31 00:00:00 EST

  None (edit)
Description Stiphane Doyon 2001-01-24 21:18:33 EST
Interaction between pine and gnupg: pine sending-filters (see /etc/pine.conf) and /usr/bin/pinegpg.
gpg-encrypt and gpg-sign+encrypt -> pinegpg are called by pine as filters with the mail addresses of the recipients on the command-line. gpg is supposed to encrypt the message for these recipients.
But the filter command and pinegpg script do not call gpg correctly: there should be a -r option for each recipient, but only one is given.
Example: mail to addresses addr1@example1.com and addr2@example.com should call gpg -at -e -r addr1@example.com -r addr2@example.com. Currently, the second -r is missing.
So gpg thinks the second and following addresses are filenames. The error message thus produced (something like "no such file or directory") is not easily interpreted in the context by a user who has not read the script...

This basically prevents sending encrypted mail to more than one recipient.
Comment 1 Mike A. Harris 2001-01-28 13:37:43 EST

*** This bug has been marked as a duplicate of 21271 ***

Note You need to log in before you can comment on or make changes to this bug.