Dear All,
this is something between a technical inquiry and a consultancy
request (if someone is interested).

I am writing here after contacting Kaspar Brand which said me that
there is the place where mozilla crypto experts talk :)

I am writing a thunderbird plug-in.
It's required a thunderbird plug-in to download a digital certificate,
install it in thunderbird certificate store and configure it to be
used for an account.

The plug-in should:
- connect to https server (already working)
- provide login and password (already working)
- download a digital certificate in .p12 format (password protected)
- import it using the password used for the https download (without
any prompt)
- setup it to be used for email (configured for a specific account or
identity)
- import a public key from an x509v3 public certificate "on-the-fly"

If a new certificate is remotely available it should:
- download the new certificate
- unlock it with the password used for https download
- substitute the already available certificate

I need also to implement a function "remove_all_certificate_stuff()"
that delete and unconfigure all the data relevant to the digital
certificate.

Then i need to be able to "hook" the events of:
- Writing to drafts
- Writing to Sent
- Sending an email

In order to make a decision on 'how to encrypt/sign' (with which key)
that email messages.

The hook should allow me to specify an arbitrary number of x509 keys
with which encipher the message beeing sent or stored in a remote
folder (Sent/Drafts) .

I want to know if someone already have done something like that, if
know if it's feasible by only writing a XUL extension or if it require
writing custom DLL c++ code.

Instead if someone is interested in a consultancy, we could be
interested on it, please write an email to cv * khamsa.net .

We could also evaluate to opensource all the code managing those
functionality.

A brief analysis we received from Kaspar is here:
=========================================================
I think most of these should be doable in the frontend (i.e., with
JavaScript and XPConnect, without the necessity of having to write
your
own XPCOM component).

Step 4 (import w/o password prompt) requires some twisting, but you
can
achieve that by overriding the onload attribute of getp12password.xul,
like this:

onload="params=window.arguments[0].QueryInterface(nsIDialogParamBlock);params.
SetString(2,'your_secret_password');params.SetInt(1,1);window.close();return
true;"

(See
http://lxr.mozilla.org/seamonkey/source/security/manager/pki/resources/content/getp12password.xul#50,
of course you don't have to hardcode the password... You can override
onload by means of a XUL overlay, but in any case, you must use
chrome://pippki/content/getp12password.xul, as this URI is hardcoded
in
PSM, cf.
http://lxr.mozilla.org/seamonkey/source/security/manager/pki/src/nsNSSDialogs.cpp#626.)
=========================================================

Regards

_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto

Reply via email to