Bug 24902

Summary: pine's filters fail to properly encrypt mail sent to multiple recipients (using gpg)
Product: [Retired] Red Hat Linux Reporter: Stiphane Doyon <s.doyon>
Component: pineAssignee: Mike A. Harris <mharris>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0J   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-01-25 02:18:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stiphane Doyon 2001-01-25 02:18:33 UTC 
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 and addr2 should call gpg -at -e -r addr1 -r addr2. 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 18:37:43 UTC 

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