Recent changes to feature-requests

disable "wait for key" after encrypt

2001-12-13T19:06:20Z

I have line #180 commented out in pgpenevelope_encrypt to avoid having to press return two times to encrypt or sign a message. does this hide any critical information from my eyes?

if not, i suggest adding a config option to disable that.

Password caching

2001-07-23T21:21:16Z

Ideally the system would remember my password for the
duration of my pine session or for some timeout period
within that session (IE if I don't use it for 10
minutes, flush the pw).

remember passphrase during session

2001-05-18T12:02:27Z

Would be nice if you could include pine's
_PREPENDKEY_ feature to support passphrase caching:
create a symmetrically encrypted file named after
_DATAFILE_ to strore the passphrase in and use it
instead of asking for a passphrase over and over
again.

I'm not shure, if this implies major security holes,
but in my opinion managability of encrypted messages
should be as easy and fast as unencrypted ones.
Otherwise they will never replace the unencrypted
email traffic.

Regards, Mark.

auto-encrypt to known recipients

2001-03-30T17:55:46Z

encrypt by default if all recipients have a vailid+trusted public key
don't encrypt by default if at least one recipient doesn't have a public key

remember passphrase

2001-03-30T17:49:18Z

this would make it a whole lot easier to browse through a folder of encrypted messages. i know that remember (=saving) the passphrase may be a security problem, but it thing many people could live w/ that.