Gnus development mailing list
 help / color / mirror / Atom feed
From: Daiki Ueno <ueno@unixuser.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Bad usage of pgg-gpg-* functions in allout.el
Date: Fri, 07 Apr 2006 12:46:07 +0900	[thread overview]
Message-ID: <2595ece8-1a2b-48e5-a905-b37bd890ecae_-_@well-done.deisui.org> (raw)
In-Reply-To: <2cd46e7f0604061550j44c97f68v4c6cffda79a4e0ce@mail.gmail.com> (Ken Manheimer's message of "Thu, 6 Apr 2006 18:50:11 -0400")

>>>>> In <2cd46e7f0604061550j44c97f68v4c6cffda79a4e0ce@mail.gmail.com> 
>>>>>	"Ken Manheimer" <ken.manheimer@gmail.com> wrote:
> thank you!  allout's encryption seems to be working with your reversion.

Aside from the reversion of pgg-gpg.el, when I looked into allout.el's
encryption stuff, I found that 4 undocumented non-interface functions
of pgg-gpg are used:

pgg-gpg-lookup-key-owner
pgg-gpg-symmetric-key-p
pgg-gpg-select-matching-key
pgg-gpg-key-id-from-key-owner 

Fortunately, the latter 3 functions do _not_ call "gpg".  Ken, would you
please copy these functions from pgg-gpg.el into allout.el and replace
s/pgg-gpg/allout/?  Otherwise, these functions may be abolished again in
the future version of PGG.

pgg-gpg-lookup-key-owner needs to be implemented as an interface
function.  I'm now working on this.

Regards,
-- 
Daiki Ueno

  reply	other threads:[~2006-04-07  3:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07  8:09 PGG updates Daiki Ueno
     [not found] ` <27877.1144257571@norvel.baumann-gauting.site>
     [not found]   ` <87odze8tth.fsf@pacem.orebokech.com>
2006-04-06 18:47     ` pgg-gpg stalls Reiner Steib
2006-04-06 19:10       ` Romain Francoise
2006-04-06 22:50         ` Ken Manheimer
2006-04-07  3:46           ` Daiki Ueno [this message]
2006-04-07  9:43             ` Bad usage of pgg-gpg-* functions in allout.el Daiki Ueno
2006-04-07 12:46         ` pgg-gpg stalls Thomas Baumann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2595ece8-1a2b-48e5-a905-b37bd890ecae_-_@well-done.deisui.org \
    --to=ueno@unixuser.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).