Hi daniel--
On Mon 2015-06-08 05:51:06 -0400, daniel Azuelos wrote:
> I switched to a new gpg2 environnment and would like to check if it
> will interroperate fully with the most recent versions of Enigmail >= 1.8.
> Could someone send me a signed E-mail, I would like to get one from :
> - CentOS,
> - Debian,
> - Ubuntu,
> - Mavericks,
> - Yosemite,
> - Windows 7
> - Windows 8,
I agree with Robert that this isn't a great use of the mailing list.
For one thing, it's too much data for other people on the list to sift
through or filter out -- we'd like to keep the signal-to-noise ratio
high here.
On the other hand, it's not enough data for you to draw any useful
conclusions about "interoperability" writ large. For instance, you've
listed only two versions of Windows and Mac OS, and only one each of
three different GNU/Linux distros. You also aren't testing any sort of
e-mail encryption, you're not comparing PGP/MIME, you haven't specified
what sort of public key algorithms, symmetric ciphers, digest
algorithms, etc. you're interested in interoperating with, and you
haven't mentioned what versions of OpenPGP implementations you're
interested in testing against, or what mail user agents, whether you
want attachments, character set encodings, etc. And of course:
addressing all of these concerns would make the earlier concern about
signal-to-noise on the mailing list even worse!
That said, your interest in interoperability is a laudable one, and
something that the community could really use if you want to step up to
the challenge.
Here are some steps that might be useful for creating such an interop
test suite:
a) set up a couple secret keys that are encryption-capable.
b) request e-mails from clients who want to participate. Maybe each
participating client should send two mails: one signed, and one
signed and encrypted. (or maybe, like you've proposed, you just
start with signed for now)
c) specify what data each e-mail should include (OS+version, OpenPGP
implementation+version, MUA+version, signing key fingerprint, etc),
and indicate how that data should be structured (perhaps provide an
example e-mail)
d) collate the e-mails received (scoring them somehow?(, and make them
indexable by the parameters supplied
e) publish the archive of received mails in usable form(s) -- tgz'ed
maildir, mbox, or .pst file, for example, along with a keyring that
contains all the public OpenPGP certificates belonging to the
submitters
f) publish a dyamically-updated web site that makes it easy to figure
out which MUAs (on which platforms) have not submitted messages, and
which can help identify developers who might be promptable to submit
such messages.
g) encourage (and archive?) test suites for various MUAs (on various
platforms) which process the published set of sample messages and
verify the results.
This would be an ongoing process, but it could be a great resource for
implementors, as well as a way to identify problematic software.
--dkg
_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
