--===============60257372893566608==
Content-Type: multipart/signed;
  protocol="application/pkcs7-signature";
  micalg=sha1;
  boundary="Boundary-02=_Nc4V/6wLI2+uLCu";
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit


--Boundary-02=_Nc4V/6wLI2+uLCu
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Monday 25 August 2003 22:06, George Staikos wrote:
>    Well the biggest problem right now is that the "plugin" architecture is
> only designed to support one plugin: the gpg based one.=20

I'm not sure this can ever be changed for the crypto functionality.
It is likely that its integration with KMail code will be deep.
Thus calling this "plug-in" is giving the false impression that there
could be a one interface for S/MIME or OpenPGP crypto code.
It is more like a prepared loadable module.

>    I suspect we will have a fully working PKCS#11 sometime over the next
> year and it would be nice if our plugin worked so we could use it.

As far as I've understood PKCS#11, this interface not useful=20
for Free Software applications, because we can more directly access
tokens like ICCs. The access itself is not posing the problem
and will not just make the tokens work.
You need to control the devices and that is not part of PKCS#11,
but will be the problem.

>    I still believe that this licence complaining is a load of crap.  If t=
he
> licencer and the licencee both agree that the licence is acceptable to
> eachother, then that must be sufficient. =20

That is being naive.
You can't  prove that "silent" agreement in court
thus making anybody depending on the change of the mind=20
of any of the right owners (which there are many).

> KMail will not be linking against
> OpenSSL (it never does, really, though it does use KSSL).  The plugin can
> be in a separate directory.  At that point, the only person concerned must
> be the plugin author.

It is running in the same address space if I understand that technical
construction correctly. And even if it doesn't, it most likely will
be a derived work, because of the unique depencency.

>    If the plugin system can actually be turned into a *plugin* system and
> not a hardcoded library path to ~, then I propose we finish up the KSSL
> S/MIME plugin and commit it to kdepim or kdeaddons.

Beside the licensing problem this most likely will not make KMail=20
SPHINX (German subset of =C4gypten) compatible, because of details
and official testings needed.


--Boundary-02=_Nc4V/6wLI2+uLCu
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Description: signature
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIG5zCCA24w
ggLXoAMCAQICAQEwDQYJKoZIhvcNAQEEBQAwPTELMAkGA1UEBhMCREUxGDAWBgNVBAoMD0ludGV2
YXRpb24gR21iSDEUMBIGA1UEAwwLV3VyemVsIFpTIDMwHhcNMDMwNjI4MTczMjAxWhcNMDgwNjI3
MTczMjAxWjA2MQswCQYDVQQGEwJERTEYMBYGA1UECgwPSW50ZXZhdGlvbiBHbWJIMQ0wCwYDVQQD
DARaUyA0MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD43bxDYhcb0rC4InYfDPX+TCd+TBVU
fzCjsS4e6LS3Xmf3kC9W0LtcvBtYDhwU1pjYgAQUZy3qEOkicQcgP6CzileDs9uzZ15n+Nd1Ye6g
xAoEtxY4TDm9J1FsNRycuHPNvOVcF8X/TtWGG1Fw1H+w4RBNUTvm6wKdRc+E1DXSlQIDAQABo4IB
gzCCAX8wDwYDVR0TAQH/BAUwAwEB/zALBgNVHQ8EBAMCAQYwawYDVR0fBGQwYjBgoF6gXIZabGRh
cDovL2NhLmludGV2YXRpb24ub3JnL2NuPVd1cnplbCBaUyAzLCBvPUludGV2YXRpb24gR21iSCwg
Yz1ERT9jZXJ0aWZpY2F0ZVJldm9jYXRpb25MaXN0MB0GA1UdDgQWBBTpC2Y1APybXfobl6bvbeei
CAqfFjBlBgNVHSMEXjBcgBSg1pV9tld6qf8t9ZykEbqfB+8Jz6FBpD8wPTELMAkGA1UEBhMCREUx
GDAWBgNVBAoMD0ludGV2YXRpb24gR21iSDEUMBIGA1UEAwwLV3VyemVsIFpTIDOCAQAwNQYDVR0R
BC4wLIEQY2FAaW50ZXZhdGlvbi5kZYYYaHR0cDovL2NhLmludGV2YXRpb24ubmV0MDUGA1UdEgQu
MCyBEGNhQGludGV2YXRpb24uZGWGGGh0dHA6Ly9jYS5pbnRldmF0aW9uLm5ldDANBgkqhkiG9w0B
AQQFAAOBgQCnwZPGbBIMrPLMXW3Z6w4JPiW/Crd8hR3He8BPY5N7u3ZRSo+mdkAzZ8YwfIJ9Fipj
cl2IxQstvE38NAWFdsogdTMOJODVdJpjFEVcVK/u8bZOKismP4eo8X9Y4m0p+WMCG7C6PNMM/+l/
uawHwEbZs4Lp1leIeI8v2/QFP6nMWDCCA3EwggLaoAMCAQICAQEwDQYJKoZIhvcNAQEEBQAwNjEL
MAkGA1UEBhMCREUxGDAWBgNVBAoMD0ludGV2YXRpb24gR21iSDENMAsGA1UEAwwEWlMgNDAeFw0w
MzA2MzAxNjE3MzVaFw0wNTA2MjkxNjE3MzVaMEExCzAJBgNVBAYTAkRFMRgwFgYDVQQKEw9JbnRl
dmF0aW9uIEdtYkgxGDAWBgNVBAMTD0Jlcm5oYXJkIFJlaXRlcjCBnzANBgkqhkiG9w0BAQEFAAOB
jQAwgYkCgYEAxfEm4PybLti0jk+zmKPB+9Qu+nyjfsOf+VQ2/q5wPlGgQlAmA1xfjfAWCfS7KR1i
3BZmsx/HzW1dv1gNAVqYIk0V0Ls9TGJr8Z0IW1hR0UXY7qRCGAFJwiIKj0kwJepMpH22K/jHjQcn
RX8VOdBo8dXyJPQcWcHkj2W8vdonrzUCAwEAAaOCAYIwggF+MAwGA1UdEwEB/wQCMAAwDgYDVR0P
AQH/BAQDAgXgMGQGA1UdHwRdMFswWaBXoFWGU2xkYXA6Ly9jYS5pbnRldmF0aW9uLm9yZy9jbj1a
UyA0LCBvPUludGV2YXRpb24gR21iSCwgYz1ERT9jZXJ0aWZpY2F0ZVJldm9jYXRpb25MaXN0ME8G
CWCGSAGG+EIBDQRCFkBFLU1haWwgQ2VydGlmaWNhdGVzIGZvciBJbnRldmF0aW9uIGFuZCBmcmll
bmRzIChub24tcHJvZHVjdGlvbikuMB0GA1UdDgQWBBSkusKJJedJL1PF+eXAiDJj6tJ9sDBlBgNV
HSMEXjBcgBTpC2Y1APybXfobl6bvbeeiCAqfFqFBpD8wPTELMAkGA1UEBhMCREUxGDAWBgNVBAoM
D0ludGV2YXRpb24gR21iSDEUMBIGA1UEAwwLV3VyemVsIFpTIDOCAQEwIQYDVR0RBBowGIEWYmVy
bmhhcmRAaW50ZXZhdGlvbi5kZTANBgkqhkiG9w0BAQQFAAOBgQAd4yqTmH1n1flB/7NtXTlYh5nl
x/dS6qALdMLB0ZdSuPKsargeb+Nb7VQ2uL8+N9c1N2unMn6mTeNtrXx98/gkGgQlLAyfEZ7JRX2y
28zFpAM/n1nay//M6Q+nUC28QwvfaxzPsIZo3t5+wC1RZcRndCOlBMSbmpmHwcf72Log7TGCATww
ggE4AgEBMDswNjELMAkGA1UEBhMCREUxGDAWBgNVBAoMD0ludGV2YXRpb24gR21iSDENMAsGA1UE
AwwEWlMgNAIBATAHBgUrDgMCGqBdMCMGCSqGSIb3DQEJBDEWBBRic0ApXq8qAxoMGLLSKpMEv0Ra
OzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wMzA5MDQxODQwMTBa
MAsGCSqGSIb3DQEBAQSBgFtMqbsDqMqeJv4t45X7vIXt8bKsbUqyNSG8NWMgzUIbq+ofkTwmN4tL
y7tvirmDPwhCPuxqPW3T+ynde3fZt9uufIY5KFNVd2SLjUQ8EEyXwEaRqiuTBFoRfmSrithALYhl
UPACFd1SZun1GTnVgiX6hfebOcGZJuk8ZGfeKN+QAAAAAAAA

--Boundary-02=_Nc4V/6wLI2+uLCu--


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

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail

--===============60257372893566608==--