--===============0489952629==
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="Boundary-02=_RDiNAt3izivQYJf";
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

--Boundary-02=_RDiNAt3izivQYJf
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Edwin, first of all many thanks for working on this.

On Thursday 19 February 2004 03:50, Don Sanders wrote:
> > - signing/encryption of HTML messages
>
> I think traditional GnuPG Signing/Encrypting doesn't make sense for
> HTML mails. Because there is no significant body part, HTML mails
> only consist of alternative attachments, (and traditional GnuPG
> signing/encryption doesn't support encrypting/signing attachments).
>
> I think if KMail is configured for traditional GnuPG support then
> signing/encryption should be completely disabled, anything else would
> be dangerous and a security flaw.

Edwin's solution to ask the user in this case is a very good solution.=20
(See his reply and my reply to Andreas' reply to Edwin's reply.)

> S/MIME support should be possible, but it doesn't seem to make sense
> working on that now with the S/MIME code being modified in the
> aegypten_branch and pending merging.

OpenPGP/MIME and S/MIME do already work since KMail 1.5 with the crypto=20
plugins. The changes in the aegypten_branch which aim for obsoleting=20
the crypto plugins don't change that much code.

> > I hope these issues won't stop my patch going into cvs.
>
> Ingo, Cornelius I'd appreciate a comment on the S/MIME
> signing/encryption and HTML editing situation. Wait for the aegypten
> merge or commit before?

That's the wrong question. The HTML editting patch can be committed as=20
soon as it's possible to sign HTML messages with OpenPGP/MIME (then=20
signing with S/MIME should automatically work as well). If I understood=20
Marc's reply correctly then it won't be that easy to accomplish this=20
without either introducing a very ugly hack or a redesign of KMail's=20
message and body part classes (i.e. merge KMMsgPart and PartNode (to=20
e.g. KMail::MessagePart) and make KMMessage inherit from=20
KMail::MessagePart.

Regards,
Ingo

--Boundary-02=_RDiNAt3izivQYJf
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBANiDRGnR+RTDgudgRAu90AJ9ISncoOFVz193Ox48nwEXSsUSzhwCgyiy3
9GUhYvdX40H+qKTpCxgmUEM=
=eqik
-----END PGP SIGNATURE-----

--Boundary-02=_RDiNAt3izivQYJf--

--===============0489952629==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0489952629==--