Re: [bug-anubis] Questions about gpg-encrypt

[Sergey Poznyakoff]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Dominique,

Please, notice that the mail server mail.gnu.org is experiencing
intermediate problems due to which the delivery of postings to
address@hidden may suffer substantial delays. So, please make
sure your postings contain "Cc:" to Wojciech <address@hidden>
and Sergey <address@hidden>. We apologize for the inconvenience.

Now, to the matter:

> I wrote a rule in which I was calling in sequence gpg-sign and
> gpg-encrypt but the result seems to be different from what I expected:
> The mozilla plugins enigmail was recognizing that the e-mail was

Yes, the fact is that signing and encrypting a message in one
operation (gpg -se) produces different results compared
to sequentially signing it (gpg -s) and then encrypting it (gpg -e).
Unfortunately, we have not yet provided a special command in Anubis
that would allow you to encrypt and sign a message at once. However,
this can be done using external-body-processor directive. The rule for
that would look like

rule "se:(.[^;]*);"
  external-body-processor /usr/local/bin/gpg --armor --batch -se -r \1
done

Then, any message whose "Subject:" header ends with "@@se:RECIPIENT;" will
be signed and encrypted using gpg (of course, you will have to
adjust the actual path to the utility).

I would also suggest you to try to use alpha version of Anubis. It
contains a lot of improvements. If you wish to give it a try,
please download it from anonymous

   ftp://mirddin.farlep.net/pub/alpha/anubis-3.9.91.tar.gz

(the official location alpha.gnu.org is not fully operational
yet). Please read the file NEWS and accompanying docs for the
information about the user-visible changes. We would appreciate
your comments on this release.

> I can understand -and I respect- your reluctance to answer to a guy if 
> you have the impression that he is a slacker.

I'm afraid you have misinterpreted Wojciech's reply. There was surely
no reluctance to help you.

> If I don't get the answer, I'll tell you and if I really don't get the
> answer, I'll drop the ball and somebody else will pick it.

Be sure you will always get the proper answer. Notice, however,
my remark at the start of this letter: for pure technical reasons
we may fail to receive your letters if we weren't mentioned in
the Cc list. We hope these problems will soon be solved.

> The impression I had on the documentation was that it was "javadocish":
> all the features are documented, clearly, simply, cleanly, but at the
> atomic feature level.
> For users like me -what I mean by that is not having the intimacy you
> have neither with the domain nor with the tool itself-, a few examples,
> use case driven, would be really helpful.

I agree. That is a good point. Again, please take a look at the
new documentation. Does it look better?

> I really mean that it is not my intention to offend you by adding the
> following comment:
> I volunteer to write the little part relating to the use case I am
> trying to address.

Your help will be highly appreciated.

Regards,
Sergey



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iD8DBQE/Q4KQNgKwf1XQxzIRAkIdAJ99D3Yaz6JzR6evI6sYnsuLcQVVbQCghgAD
e66VBYMYNszKNTWj+0merys=
=0r+0
-----END PGP SIGNATURE-----