[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: [PATCH] Fix loose ends in crypto support: pt.4+5/??: config
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2004-05-31 15:05:52
Message-ID: 200405311705.53595 () erwin ! ingo-kloecker ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Sunday 30 May 2004 21:23, Marc Mutz wrote:
> Hi!
>
> This patch contains the configure dialog's Security Page rework. The
> only thing outside of that page is the config option for composer
> autosave.
>
> This patch adds GUI config for:
> - specifying the composer autosave interval (can be 0).
>   I know this is controversial, but most programs allow the save
> interval to be configured, I don't see the point in not adding this
> option. Since it's controversial, however, I've made it a separate
> patch file.

No problem.

> - specifying whether or not to import attached 
> certificates automatically. This is currently only implemented for
> S/MIME (see later patches), but is dead easy to implement for
> OpenPGP, too.
>   This sounds like more than it actually is, since gpgsm imports
> certs in signatures anyway, to be able to check the sigs. This is
> just the way S/MIME works. We still make it configurable, mainly b/c
> project management couldn't establish a position on whether or not it
> should happen automatically :)

So what happens if the user disables automatic import? The user's wish 
is ignored (because gpgsm doesn't care for the user's wish anyway)?

> - Remove the GUI for 
> enabling/disabling DSNs.
>   We never generated standards-conformant DSNs anyway; in addition to
> that, this is an MTA-level feature. We simply lack the envelope data
> to create them. Since we now have MDNs, which _are_ MUA-level, I'm on
> a quest to phase out the KMail-pseudo-DSN support "bouncing". This is
> one part of it. Why is this here? We needed the space occupied by
> that groupbox otherwise :)

Okay.

> - Add an option to suppress any MDN 
> sending in case of encrypted messages. We always sent an MDN,
> regardless of whether or not the decryption actually succeeded,
> apparently some Win SW doesn't do it this way, which makes them an
> Oracle. We never were one, but this is an option for the paranoid, of
> which we have a few (HTML sidebar, attachment icons in the message
> list, etc)

Okay.

> - Reorganise the Security Page:
>   (General,PGP,CryptPlug(Crypto Backends),individual CryptPlug
> config) ->(Reading,Composing,S/MIME Validation,Crypto Backends,
>      individual Crypto Backend configs)

Okay.

> These patches depend on: (nothing (I know of)).

The patch is lacking some whitespace, e.g. between parentheses and their 
contents. (I know, not before the merge. But they should've been there 
in the first place.)

Regards,
Ingo

[Attachment #5 (application/pgp-signature)]

_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel


[prev in list] [next in list] [prev in thread] [next in thread]