Re: How to deal with encrypted messages
Felix Tiede <[email protected]> Wed, 21 Sep 2022 12:55:29 +0200
| Newsgroups | gmane.comp.kde.devel.pim |
|---|---|
| Message-ID | <1811150.MHEki62Tyu@pip> |
Am Mittwoch, 21. September 2022, 12:33:18 CEST schrieb Axel Braun: > Hi, > > I wonder if there is some plan to improve the handling of encrypted messages > in KMail. > > Currently each encrypted message has to be clicked individually to see the > content. Messages are excluded from search by this, and it is in fact not > possible to work efficiently with encryption. > > In short - KMail is not useable for this. > > How about automatic decryption? GnuPG key might be entered once at start of > KMail, or even stored in kwallet (despite of security considerations). > > Any other ideas or plans? Just my 2ยข on this: First, the GPG passphrase is cached, not indefinitely long, but it works for some time without re-entering. Second, I work with KMail and encrypted messages on a laptop. I actually prefer KMail to not automatically display an encrypted message on screen - the system doesn't know if or if not someone else is looking at the screen at the time of switching between mails. And at last, a message can be stored decrypted in another folder and, security considerations aside, I assume (I've never tried), in that case, the message is indexed by Akonadi and can be searched. While I do see the inconveniences caused by those limitations I don't see how this can be changed without inherently compromising security for other users. It might be worth to consider an option to do the decryption/decrypted storing automatically, based on an option somewhere in KMail's settings. -- BOFH Excuse #8: static buildup
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEJijiGzDq8UDHCPC0QGDR0So3spMFAmMq7aEACgkQQGDR0So3 spNi9BAAlLw+waxhm5JoNo2I0f64rqdrqhdg5eH9Hh7l/+wqPM42vw0WNLg1jT4b SXXfTDHPPOqtFyhjXEHNQ3GqyEPUcWKGSZlnpjJ4LCSUHPRB045KihaRRiw1moHu YLxwVrzfmToknSZFU+zAR5O3G8KdjeOjab0gITuKjGyrjFTT0upE+KQjDbAmk3kc 82u/8TcMzBVTtnf4KFidT2Hg9eqPwEXp8OuDNXMnUasUqNPilP/yMfAJuMnq7bK0 3accBnlNrfc1MfbAWGvIfK87MWrZ492oLk/ePijZB0ZukdEUR6lyxm3amQREH2Sm rsrEL0JO5DhmsRZf85s5Pxi+EJHt9hs4sqx4Bs+Iuzo3nmi9g9BxoSVDGSRepSlq LHruNI0vfC9rVVqiKAJkcwc00vDBprV+dlwGLmuXL5L15DEVWtCOvIiBd9LZXovQ rg0LqRIUORM1r5dazZ2yn/QS7o75mvDoagTuUkh7haXxP7G12VGL/3KBgvprqtHI lMPCLOnnkUosB4f8r7uVa9ivWcbkePgZd5jnVlgasH8JIJ3lhvriEXqqW5tmHB+Z h6TUfNam164X05TmQS+bDesDmKQ+BzCx1U9/djtLO4Qz+OV4viweAK/Kn+SVHgk7 aw7X0P/CdlF8evX3UJssl0OECpur8hrahNY/If8mb6rrY3K+SWc= =7t3F -----END PGP SIGNATURE-----