Bug 25512 - [patch] Pine does not decrypt messages.
[patch] Pine does not decrypt messages.
Product: Red Hat Linux
Classification: Retired
Component: pine (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
Florence Gold
Depends On:
  Show dependency treegraph
Reported: 2001-02-01 14:31 EST by Sue Taylor
Modified: 2007-04-18 12:31 EDT (History)
1 user (show)

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

Attachments (Terms of Use)
pine-4.32-quote.patch (310 bytes, patch)
2001-02-02 07:55 EST, Tim Waugh
no flags Details | Diff

  None (edit)
Description Sue Taylor 2001-02-01 14:31:33 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.0-0.99.11 i586)

Messages that are sent encrypted (using Pine) do not get decrypted at the
other end (using Pine).

Reproducible: Always
Steps to Reproduce:
1.Send encrypted message to self using Pine.
2.Read message.  Note that it is encrypted and you can not read it.

Actual Results:  An encrypted message is shown.

Expected Results:  It should ask for your password and decrypt the message.
Comment 1 Tim Waugh 2001-02-01 14:35:42 EST
Verified.  Last worked in pine-4.31-2.
Comment 2 Glen Foster 2001-02-01 14:45:23 EST
We (Red Hat) should really try to fix this before the next release.
Comment 3 Tim Waugh 2001-02-02 07:55:05 EST
Created attachment 8722 [details]
Comment 4 Tim Waugh 2001-02-02 07:56:15 EST
I think the above patch is right.  get_pair _used_ to strip quotes from labels,
at least.
Comment 5 chappa 2001-02-02 18:32:28 EST
This is a known problem in pine4.32 and it was fixed in the release of Pine4.33
yesterday. The fix is different from the proposed here and I would recommend to
use the pine team solution. The funxtion get_pair is called from several
different places and I'm not quite sure this solution will fix all calls. In any
case 4.33 is out and fixes the bug
Comment 6 Tim Waugh 2001-02-03 06:31:58 EST
(Confirmed; 4.33 works for me.)

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