Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Pietro Giorgianni <giorgian@gmail.com>
To: info-gnus-english@gnu.org
Cc: Daiki Ueno <ueno@unixuser.org>
Subject: pgg-epg.el and pgg (was: epg? easypg? how?)
Date: Mon, 16 Apr 2007 14:27:22 +0200	[thread overview]
Message-ID: <87647wv711.fsf_-_@giorgian.widge.org> (raw)
In-Reply-To: <4eeb279c-a457-4567-95fc-bc78ee40ae03@well-done.deisui.org>


[-- Attachment #1.1: Type: text/plain, Size: 647 bytes --]

Daiki Ueno <ueno@unixuser.org> writes:

> It does not support easypg natively.  v0.5 was released about a year ago
> and unfortunately v0.6 is not yet released.
>
>> or should i use a different gnupg frontend?
>
> Try pgg-epg.el and pgg.

ok,
my .gnus now contains:
(require 'pgg)
(require 'pgg-epg)
(setq pgg-scheme 'epg)

so i'm able to sign messages; but, i've also:

(setq gnus-treat-x-pgp-sig t
      mm-verify-option 'always
      mm-decrypt-option 'always)

this doesn't work: i cannot even see if a message is signed or not. if i
enter W p nothing happens.

what can i do?

thanks

p.s. should i prefer sign=pgp or sign=pgpmime?

giorgian

[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
http://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2007-04-16 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12  8:53 epg? easypg? how? Pietro Giorgianni
2007-04-16  9:15 ` Daiki Ueno
2007-04-16 12:27   ` Pietro Giorgianni [this message]
2007-04-16 19:50     ` pgg-epg.el and pgg Daiki Ueno
2007-04-16 22:29       ` Pietro Giorgianni
2007-04-17  0:27         ` Daiki Ueno
2007-04-17  0:38           ` Pietro Giorgianni

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=87647wv711.fsf_-_@giorgian.widge.org \
    --to=giorgian@gmail.com \
    --cc=info-gnus-english@gnu.org \
    --cc=ueno@unixuser.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).