On Tue, May 28, 2019 at 06:48:47AM +0200, Matthias Apitz wrote:
In the moment of reply it is asking me
Enter keyID for u...@bin.org.in
This might be caused by $crypt_replyencrypt which defaults set.
Perhaps this was caused by a block in the incoming mail of:
Openpgp: preference=signencryp
Hello,
I'm using GnuPG (with an OpenPGP smartcard) to sign my mails or decrypt
mails if they have been encrypted with my pub key. For this I have in
~/.muttrc:
set crypt_use_gpgme
set crypt_autosign
and all this is fine. Yesterday I got a mail which was encrypted with my
pub key and
Hi Mutt Users,
GnuPG just released an important security fix involving injection into
the status-fd channel. The details are at
<https://lists.gnupg.org/pipermail/gnupg-announce/2018q2/000425.html>.
If you are using the suggested values in contrib/gpg.rc, it should NOT
be necessary to swi
On Wed, Mar 02, 2016 at 03:17:25PM -0800, Kevin J. McCarthy wrote:
> On Tue, Feb 16, 2016 at 11:43:16PM -0800, Will Yardley wrote:
> > On Tue, Feb 16, 2016 at 04:32:34PM -0800, Kevin J. McCarthy wrote:
> > > On Mon, Feb 15, 2016 at 10:35:35PM -0800, Will Yardley wrote:
> > > > Additionally, after
On Tue, Feb 16, 2016 at 11:43:16PM -0800, Will Yardley wrote:
> On Tue, Feb 16, 2016 at 04:32:34PM -0800, Kevin J. McCarthy wrote:
> > On Mon, Feb 15, 2016 at 10:35:35PM -0800, Will Yardley wrote:
> > > (without passphrase already cached by GPG), use 'limit' to find an
> > > encrypted, *traditional
On Tue, Feb 16, 2016 at 04:32:34PM -0800, Kevin J. McCarthy wrote:
> On Mon, Feb 15, 2016 at 10:35:35PM -0800, Will Yardley wrote:
> > (without passphrase already cached by GPG), use 'limit' to find an
> > encrypted, *traditional* (not pgp-MIME) message in a folder. In some
> > cases, not completel
On Mon, Feb 15, 2016 at 10:35:35PM -0800, Will Yardley wrote:
> (without passphrase already cached by GPG), use 'limit' to find an
> encrypted, *traditional* (not pgp-MIME) message in a folder. In some
> cases, not completely reproducible, I then only see the 'S' in the index
> lines that show up (
On Thu, Feb 11, 2016 at 09:13:42AM -0800, Kevin J. McCarthy wrote:
> Thanks for the suggestion - that was the problem: I forgot to try it
> with gpgme! With gpgme, I can reproduce "Invoking PGP..." being stuck
> in the message after decryption. I'll get a patch in for that. Please
> let me kno
On Thu, Feb 11, 2016 at 09:13:42AM -0800, Kevin J. McCarthy wrote:
> On Wed, Feb 10, 2016 at 10:09:54PM -0800, Will Yardley wrote:
> >
> > System: FreeBSD 9.3-RELEASE-p33 (amd64)
> > ncurses: ncurses 5.7.20081102 (compiled with 5.7)
> >
> > Are you using:
> > set crypt_use_gpgme=yes
> > or are yo
On Wed, Feb 10, 2016 at 10:09:54PM -0800, Will Yardley wrote:
> On Tue, Feb 09, 2016 at 06:52:29PM -0800, Kevin J. McCarthy wrote:
> > With the latest mutt tip built there, I'm not seeing any problems after
> > decryption. The pinentry-curses completely clears the screen when it
> > shows the prom
On Tue, Feb 09, 2016 at 06:52:29PM -0800, Kevin J. McCarthy wrote:
> With the latest mutt tip built there, I'm not seeing any problems after
> decryption. The pinentry-curses completely clears the screen when it
> shows the prompt, and then afterwards the status bar shows "PGP message
> successful
On Sun, Dec 27, 2015 at 07:11:04PM -0800, Will Yardley wrote:
> On Sun, Dec 27, 2015 at 07:06:37PM -0800, Will Yardley wrote:
> > Some are annoying, but haven't been able to articulate them well enough
> > to file a bug.
>
> So one issue involves redraw, but the easier one to reproduce is that
> w
On Sun, Dec 27, 2015 at 07:11:04PM -0800, Will Yardley wrote:
> On Sun, Dec 27, 2015 at 07:06:37PM -0800, Will Yardley wrote:
> > Some are annoying, but haven't been able to articulate them well enough
> > to file a bug.
>
> So one issue involves redraw, but the easier one to reproduce is that
> w
sphrase for
the first time, I still have:
Invoking PGP...
in the status bar while viewing the message, even after the message has
been successfully decrypted.
This should be with the curses, vs. tty, interface to pinentry.
gpg (GnuPG) 2.1.2
Mutt 1.5.23 (2014-03-12)
Copyright (C) 1996-2009 Michae
On Fri, Dec 25, 2015 at 08:11:34AM +0100, Matthias Apitz wrote:
> One small problem remains:
[...]
> i.e. the \n at the end of each line is not interpreted anymore as \n+\r;
> also the ENTER key sends only a \r to the STDIN of pinentry which is not
> understood either as the end of the keyed-in pas
El día Sunday, December 27, 2015 a las 07:12:43AM -0800, Kevin J. McCarthy
escribió:
> Ah... I was wrong. For signing/encrypting when we're about to send an
> email, mutt exits curses mode (calls endwin()). But when displaying a
> message, we stay in curses mode the whole time.
>
> From your e
On Sat, Dec 26, 2015 at 07:57:09PM +0100, Matthias Apitz wrote:
> El día Saturday, December 26, 2015 a las 08:34:58AM -0800, Kevin J. McCarthy
> escribió:
>
> > For gpgme, mutt is just making gpgme function calls,
> > e.g. gpgme_op_decrypt_verify(), and then setting a flag to do a redraw
> > afte
El día Saturday, December 26, 2015 a las 08:34:58AM -0800, Kevin J. McCarthy
escribió:
> Mutt uses cbreak mode, but doesn't toggle raw/cooked mode anywhere as
> far as I can tell. In this case, the "Invoking PGP..." message is
> output before starting to display an encrypted message. It's
> gen
On Sat, Dec 26, 2015 at 06:32:03AM +0100, Matthias Apitz wrote:
> El día Friday, December 25, 2015 a las 06:57:05PM -0800, Ian Zimmerman
> escribió:
>
> > On 2015-12-25 08:11 +0100, Matthias Apitz wrote:
> >
> > > In the mutt' terminal (a uRxvt) the screen is a bit mangled:
> > > ...
> > > i.e.
f, which hands over
> > the tty in this state
>
> Ah, right. Do you see the "Invoking GPG" message also in the second
> (good) case? If not, maybe the code issuing it is responsible.
>
> I myself use the "obsolete" pre-gpgme code, so I can't help
On 2015-12-26 06:32 +0100, Matthias Apitz wrote:
> > Looks like raw vs. cooked mode issue. Should be fixable with stty.
>
> Ofc, but I think, this must be done inside mutt itsef, which hands over
> the tty in this state
Ah, right. Do you see the "Invoking GPG" message also in the second
(good)
El día Friday, December 25, 2015 a las 06:57:05PM -0800, Ian Zimmerman escribió:
> On 2015-12-25 08:11 +0100, Matthias Apitz wrote:
>
> > In the mutt' terminal (a uRxvt) the screen is a bit mangled:
> > ...
> > i.e. the \n at the end of each line is not interpreted anymore as \n+\r;
> > also the
On 2015-12-25 08:11 +0100, Matthias Apitz wrote:
> In the mutt' terminal (a uRxvt) the screen is a bit mangled:
> ...
> i.e. the \n at the end of each line is not interpreted anymore as \n+\r;
> also the ENTER key sends only a \r to the STDIN of pinentry which is not
> understood either as the end
El día Thursday, December 24, 2015 a las 08:58:55AM +0100, Matthias Apitz
escribió:
> Hello,
>
> ...
> it turned out, after bringing them up in the GnuPG mailing-list, that
> one only needs one(!) single value in .muttrc; and this works very
> nicely; I'm attaching the
On Thu, Dec 24, 2015 at 08:58:55AM +0100, Matthias Apitz wrote:
> I got off-list some hints (thanks for them); after setting a bunch of
> pgp_* values in ~/.muttrc I run into some GnuPG 2.1.x related problems;
> it turned out, after bringing them up in the GnuPG mailing-list, that
> o
El día Wednesday, December 23, 2015 a las 08:04:26AM +0100, Matthias Apitz
escribió:
>
> Hello,
>
> I'm using on my FreeBSD 11-CURRENT netbook gnupg-2.1.6 to encrypt my
> files and will now use this as well together with mutt to sign mails or
> encrypt them with public
Hello,
I'm using on my FreeBSD 11-CURRENT netbook gnupg-2.1.6 to encrypt my
files and will now use this as well together with mutt to sign mails or
encrypt them with public keys of the recipients;
I search around to get a tutorial for the correct settings in .muttrc,
but the things seem
Hey,
On 2014-11-29 21:10:16 -0500, Gilles-Philippe Morin wrote:
> I'm using Arch Linux ARM on a Raspberry Pi.
>
> Version: 1.5.23-1
> GnuPG: 2.1.0-6
>
> When I sign ('p' then 'a') an email, then send (y) the email, mutt
> asks for my PGP passphra
Operation cancelled
> gpg: symmetric encryption of '01 - Vangelis - Chariots of fire -
> Titles.mp3' failed: Operation cancelled
>
> Would it be an issue with gpg-agent?
I don't use that and I am not sure what it does. Perhaps ask on the gnupg
list. Once you can encrypt an
p3' failed: Operation cancelled
Would it be an issue with gpg-agent?
On Sun, Nov 30, 2014 at 12:58 AM, John Long wrote:
> On Sat, Nov 29, 2014 at 09:10:16PM -0500, Gilles-Philippe Morin wrote:
>> I'm using Arch Linux ARM on a Raspberry Pi.
>>
>> Version: 1.5.23-1
>
On Sat, Nov 29, 2014 at 09:10:16PM -0500, Gilles-Philippe Morin wrote:
> I'm using Arch Linux ARM on a Raspberry Pi.
>
> Version: 1.5.23-1
> GnuPG: 2.1.0-6
>
> When I sign ('p' then 'a') an email, then send (y) the email, mutt
> asks for my PGP pass
I'm using Arch Linux ARM on a Raspberry Pi.
Version: 1.5.23-1
GnuPG: 2.1.0-6
When I sign ('p' then 'a') an email, then send (y) the email, mutt
asks for my PGP passphrase. After I enter it, I get this output in the
console:
gpg: signing failed: Operation cancelled
gpg:
also sprach Kyle Wheeler [2009.12.05.0146 +0100]:
> >I haven't checked recently either; when I get some time, I'll fire up
> >the ole XP virtual machine to check it out.
>
> Unfortunately, all I have is MS Office 2000, which is too old to work
> with GPG4Win.
I tried it, and GpgOL does indeed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wednesday, December 2 at 12:07 PM, quoth Kyle Wheeler:
>On Monday, November 30 at 08:04 PM, quoth martin f krafft:
>> This is going off-topic, but I'd appreciate a response. GpgOL might
>> be able to decipher PGP/MIME, which would be a grand ste
also sprach Michael Wagner [2009.12.03.0847 +0100]:
> JFTR: Today was an upgrade of the 'mutt' package in Debian unstable and
> now it works very well.
I know: http://bugs.debian.org/558813 ;)
Thanks for letting the list know!
--
martin | http://madduck.net/ | http://two.sentenc.es/
stupidi
* martin f krafft 29.11.2009
> also sprach David J. Weller-Fahy
> [2009.11.29.1631 +0100]:
> ro this means that your mutt 1.5.20 on Darwin correctly splits the
> message and only passes to gnupg what it must, while "our" 1.5.20 on
> Debian sid does not. Very stra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Monday, November 30 at 08:04 PM, quoth martin f krafft:
> This is going off-topic, but I'd appreciate a response. GpgOL might
> be able to decipher PGP/MIME, which would be a grand step,
Apparently it can.
> but last I checked, it couldn't crea
also sprach Derek Martin [2009.11.30.1921 +0100]:
> My Mutt is Mutt 1.5.20hg (2009-06-23), only slightly newer than yours,
> but it clearly does have code to handle the case of pgp-mixed text
> bodies (in pgp_application_pgp_handler() in pgp.c). So it would seem
> the discussion is moot.
Indeed.
also sprach Kyle Wheeler [2009.11.30.1638 +0100]:
> ...Or if you deal with (Al)Pine+PGP people, because (Al)Pine cannot
> deal with PGP-MIME or any MIME format where one MIME component must be
> interpreted differently based on the contents of another MIME
> component.
>
> As for Outlook... I
On Sun, Nov 29, 2009 at 09:59:32AM +0100, martin f krafft wrote:
> also sprach David J. Weller-Fahy
> [2009.11.28.2236 +0100]:
> > I then entered ':exec check-traditional-pgp' in mutt, and viewed
> > the message. The text preceding the digitally signed portion of
> > the message was still visibl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Monday, November 30 at 09:58 AM, quoth martin f krafft:
> The problem comes when they aren't your peers (but e.g. your boss),
> or when you deal with Outlook+PGP people, because as far as I know,
> there is no way to do PGP-MIME with Outlook.
.
also sprach Derek Martin [2009.11.30.0811 +0100]:
> Yes, I mean with any MIME. PGP predates MIME by about a year, as
> far as I can tell. So-called "traditional" PGP was intended to be
> used entirely within the message body, because at the time it was
> created there was *only* a message body.
On Fri, Nov 27, 2009 at 10:06:31PM -0500, Todd Zullinger wrote:
> If you call check-traditional-pgp on this message, is this text lost?
No, actually...
> It is for me and I would call it a bug.
I can see why you'd say that, but I don't agree (regardless of the
fact it's not happening for me).
also sprach David J. Weller-Fahy
[2009.11.29.1631 +0100]:
> * Michael Wagner [2009-11-29 07:59 -0500]:
> > * martin f krafft 29.11.2009
> > > This *could* be due to gnupg. Do you see the unsigned portions of
> > > the text if you run
> > >
> > >
* Michael Wagner [2009-11-29 07:59 -0500]:
> * martin f krafft 29.11.2009
> > This *could* be due to gnupg. Do you see the unsigned portions of
> > the text if you run
> >
> > gpg < ~/test
I do *not* see the text preceding the digitally signed portion of the
me
me with mutt from Debian sid (1.5.20 (2009-06-14)),
> then I definitely do not see the unsigned portions.
>
> This *could* be due to gnupg. Do you see the unsigned portions of
> the text if you run
>
> gpg < ~/test
Hello Martin,
I can reproduce this behaviour here on my D
ec check-traditional-pgp' in mutt, and viewed
> the message. The text preceding the digitally signed portion of
> the message was still visible.
If I do the same with mutt from Debian sid (1.5.20 (2009-06-14)),
then I definitely do not see the unsigned portions.
This *could* be due to
* Todd Zullinger [2009-11-27 21:07 -0500]:
> If you call check-traditional-pgp on this message, is this text lost?
> It is for me and I would call it a bug. It might also be some subtle
> difference between our configurations, gpg versions, etc.
FWIW I copied your message into ~/test, and then o
unsigned content
then will feed all 7 lines to GPG, and GPG
will swallow the first and the last lines.
Either gnupg needs to learn to emit unsigned content, and visually
distinguish signed from unsigned content, e.g
unsigned content
-- begin signed content --
signed content
-- end si
that, check-traditional-pgp is not intended to work with
> MIME messages...
I've seen this problem when there is no PGP-MIME involved. Or did you mean any
MIME?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iQFDBAEBCAAtBQJLEI+SJhhodHRwOi8vd3d3LnBvYm94LmNvbS9+dG16L3BncC
So, a couple of things...
On Fri, Nov 27, 2009 at 11:55:52AM +0100, martin f krafft wrote:
> You won't see this text if mutt automatically verifies signed text
> (if pgp_auto_decode is set). Run ':exec
> check-traditional-pgp' if you see it to get the described
> effect.
I have pgp_auto_decode se
; but if you configured mutt with pgp_auto_decode, then it filters the
> entire message through gnupg, which swallows all the unsigned text.
Indeed. I've noticed this as well. A more annoying case is if
someone replies to a clearsigned PGP message and leaves the entire
message intact (as thos
7;s a bit of text preceding the "Hello," up top of this mail,
but if you configured mutt with pgp_auto_decode, then it filters the
entire message through gnupg, which swallows all the unsigned text.
- --
martin | http://madduck.net/ | http://two.sentenc.es/
"i always choose my friend
Hello Martin,
It seems there is a misunderstanding from you of course the parser from
because normaly the "Debian Signature Parser" cut off the GPG
signed message and packe it into a new one with the signature attached,
which mean, it change te Header from "gpg-signed" to "multipart" put the
e to illustrate what
I think is a bug in the mutt-gpg integration. There's a bit of text
preceding this mail, but if you configured mutt with
pgp_auto_decode, then it filters the entire message through gnupg,
which swallows all the unsigned text.
A similar case happens when a mailing list manager
* On 30.10.2009 13:30, Viktor Rosenfeld wrote:
> Hi,
>
> maybe your uni SMTP server is mangling the message body.
There are no header you described. Everything seems normal.
### Header of mail with "bad signature"
X-Authenticated: #17130798
X-Provags-ID: V01U2FsdGVkX1+HT55pDw2H/x3W/0HU8t/R/JNs
Hi,
maybe your uni SMTP server is mangling the message body. If they do,
the headers should contain a record of the action. For example, some of
my incoming mails have the following header:
X-MIME-Autoconverted: from quoted-printable to 8bit by ...
Anything to that effect in your headers?
Hi listmates,
i have a problem with mutt and gnupg. I have set the gpg-options
described here: http://WIKI.mutt.org/?MuttGuide/UseGPG
I use mutt with getmail/procmail and msmtp to receive/send mail. And i
have two mail-accounts (gmx.de and my university account).
If i send me a signed mail from
was very easy
> to
> get it working with the ncurses interface :)
>
> Just set
>
> GPG_TTY=`tty`
>
> in your SHELL environment and use
>
> pinentry-program /usr/bin/pinentry-curses
>
> in your ~/.gnupg/gpg-agent.conf
That did it. N
tly well-trained folks
though. ;)
> Does anyone here know what the differences between the two are?
In a nutshell, GnuPG-2 is more modular and has support for S/MIME.
But GnuPG-1.4 isn't going anywhere for a while.
There wre a few threads on the gnupg-users list about this in the last
m
pinentry-program /usr/bin/pinentry-curses
in your ~/.gnupg/gpg-agent.conf
But this doesn't answer Kyles question ...
Greetz
Stefan
On Wed, Sep 03, 2008 at 11:56:16AM -0500, Kyle Wheeler wrote:
> Does anyone here know what the differences between the two are? Why
> gnupg2 is recommended for "desktop" use moreso than gnupg1?
On gentoo at least, gnupg2 gets real pissy when there is no X
environment. I don't use it all that mu
able above and beyond my standby Gnupg
1.4.9. The www.gnupg.org website says that Gnupg2 is more suited for
desktop use, and that got me curious: what's the difference between
the two? What's the advantage of using one over the other? I have both
installed now, but neither the man pa
On Wed, Sep 12, 2007 at 02:28:25PM -0500, Kyle Wheeler wrote:
> On Wednesday, September 12 at 09:10 PM, quoth sigi:
> >If I type the command (gpg --recv-keys X) manually, it receives
> >the key correctly, and adds it to my keyring. I tried several
> >keyservers, and they all didn't catch the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, September 12 at 09:10 PM, quoth sigi:
>If I type the command (gpg --recv-keys X) manually, it receives
>the key correctly, and adds it to my keyring. I tried several
>keyservers, and they all didn't catch the key within mutt, but
>
and they all didn't catch the key within mutt, but manually they did.
There are no firewall-restrictions on http/s on my computer/router.
I'm using
gpg (GnuPG) 1.4.6 and
Mutt 1.5.16 - the problem existed in mutt 1.5.15, too.
I couldn't find anything useful in the web - so I h
visd-group. Integrate amavisd-new as content filter into
Postfix. The amavisd-website has documentation on how to do this.
> - -signing and reading encrypted mails with gnupg should be part of the
> config
To be done within mutt. There are many examples only you can work from.
> - -spamassassi
gnupg should be part of the
config
- -spamassassin should check and handle incoming mail
Best regards
- -signing and reading encrypted mails with gnupg should be part of the
config
- -spamassassin should check and handle incoming mail
Best regards
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG46WdSAoi
Quoting Omen Wild <[EMAIL PROTECTED]> on Wed, Sep 25 10:37:
>
> I'll look into this. If that's the cause, then the problem is between
> my keyboard and chair, not yours. ;-)
For anyone following this, the problem was indeed on my end. I have an
updated patch, available from
http://descolada.da
Quoting Ren? Clerc <[EMAIL PROTECTED]> on Wed, Sep 25 15:01:
>
> Typically PEBCAK. The segfault was a result of not setting this
> variable. Strange side-effect, of course, but it works now!
I'll look into this. If that's the cause, then the problem is between
my keyboard and chair, not yours.
* René Clerc <[EMAIL PROTECTED]> [25-09-2002 14:47]:
> * René Clerc <[EMAIL PROTECTED]> [25-09-2002 14:25]:
>
> > * René Clerc <[EMAIL PROTECTED]> [25-09-2002 10:30]:
> >
> > > This patch makes mutt segfault right after sending the e-mail. Despite
> > > of this, it works: both recipient and I a
* René Clerc <[EMAIL PROTECTED]> [25-09-2002 14:25]:
> * René Clerc <[EMAIL PROTECTED]> [25-09-2002 10:30]:
>
> > This patch makes mutt segfault right after sending the e-mail. Despite
> > of this, it works: both recipient and I are able to decrypt and read
> > the message.
> >
> > A clue, anyo
* René Clerc <[EMAIL PROTECTED]> [25-09-2002 10:30]:
> This patch makes mutt segfault right after sending the e-mail. Despite
> of this, it works: both recipient and I are able to decrypt and read
> the message.
>
> A clue, anyone?
Let me be more specific: like I've already mailed Omen, I appli
* Omen Wild <[EMAIL PROTECTED]> [24-09-2002 21:24]:
> Quoting Ren? Clerc <[EMAIL PROTECTED]> on Tue, Sep 24 19:08:
> >
> > I'm looking for the S/MIME equivalent of the GnuPG option:
> >
> > encrypt-to
>
> As far as I could tell, it doesn&#
Quoting Ren? Clerc <[EMAIL PROTECTED]> on Tue, Sep 24 19:08:
>
> I'm looking for the S/MIME equivalent of the GnuPG option:
>
> encrypt-to
As far as I could tell, it doesn't exist. This patch add that
functionality. Set $smime_encrypt_self to true and S/MIME encr
Hi all,
I'm looking for the S/MIME equivalent of the GnuPG option:
encrypt-to
Because now I'm unable to read the encrypted e-mails I have sent to
some recipients...
I was not able to find it in TFM...
Thanks,
--
René Clerc - ([EMAIL PROTECTED])
If you
On Thu, Aug 29, 2002 at 03:03:01PM -0700, Will Yardley wrote:
> Markus Nißl wrote:
> >
> > I will do so! Thanks again.
> >
> > BTW: no "cc:" to my address necessary, I'm subscribed to this
> > list for a year now.
>
> well you're the one who has:
> Mail-Followup-To: Markus Nißl <[EMAIL PROTECTE
* Will Yardley <[EMAIL PROTECTED]> [020829]:
> Markus Nißl wrote:
> >
> > I will do so! Thanks again.
> >
> > BTW: no "cc:" to my address necessary, I'm subscribed to this
> > list for a year now.
>
> well you're the one who has:
> Mail-Followup-To: Markus Nißl <[EMAIL PROTECTED]>,
> [E
Markus Nißl wrote:
>
> I will do so! Thanks again.
>
> BTW: no "cc:" to my address necessary, I'm subscribed to this
> list for a year now.
well you're the one who has:
Mail-Followup-To: Markus Nißl <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
set.
perhaps you want 'subscribe mutt-users' in
Hi David!
On Wed, Aug 28, 2002 at 08:35:31PM -0700, David Ellement wrote:
> On 020828, at 22:31:13, Markus Nißl wrote
> > On Tue, Aug 27, 2002 at 04:48:17PM -0400, David T-G wrote:
> > > And the conversion isn't necessary now because you can
> > > recognize an old-style message with esc-P [...]
>
r to use gpg
> > > > with mutt?
> > >
> > > You need this wrapper script if and only if you want to
> > > communicate signed+encrypted with a person who uses pgp2.6.x
> >
> > So, in order to be able to communicate with anybody who uses
> > an
Okay. At the end of your tutorial, you refer to the
Mutt-GnuPG-PGP-HOWTO. Well, that one isn't that up to date. Some
configuration variables don't exist anymore which are listed there to
be used for a gnupg setup. So that information is a bit misleading :-(
Bye,
Markus
On 020828, at 22:31:13, Markus Nißl wrote
> On Tue, Aug 27, 2002 at 04:48:17PM -0400, David T-G wrote:
> > And the conversion isn't necessary now because you can
> > recognize an old-style message with esc-P [...]
>
> Why can't mutt do that for me?
It can, if you're willing to wait. I have this
people worked with
me on it. I don't think we got anything to work out of it, though.
- --
[!] Justin R. Miller <[EMAIL PROTECTED]>
Encrypted email preferred (key 0xC9C40C31)
Mutt handy guides @ http://codesorcery.net
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (FreeBSD)
iD8
Hi David!
On Tue, Aug 27, 2002 at 04:48:17PM -0400, David T-G wrote:
> %
> % On Mon, Aug 26, 2002 at 05:32:59PM -0400, Justin R. Miller wrote:
> % >
> ...
> % > See my guide at the URL below.
> %
> % Thanks a lot for the link! Good introduction, but I missed the
> % "procmail recipe to rewrite
y if you want to
> > communicate signed+encrypted with a person who uses pgp2.6.x
>
> So, in order to be able to communicate with anybody who uses any
> version of pgp or gnupg, I have to use that script.
No.
pgp version 2 (=pgp2) uses RSA keys in key format version 3.
pgp
Markus, et al --
...and then Markus Nißl said...
%
% On Mon, Aug 26, 2002 at 05:32:59PM -0400, Justin R. Miller wrote:
% >
...
% > See my guide at the URL below.
%
% Thanks a lot for the link! Good introduction, but I missed the
% "procmail recipe to rewrite old-style inline PGP messages as
%
p2.6.x
So, in order to be able to communicate with anybody who uses any
version of pgp or gnupg, I have to use that script.
> If so you must remove the comment hashes '#' on lines which use
> gpg-2comp and set hashes '#' on the correspioning lines without
> gpg-2co
Hi Justin!
On Mon, Aug 26, 2002 at 05:32:59PM -0400, Justin R. Miller wrote:
>
> > I have recently installed gnupg-1.0.7 and I'd like to use it
> > with mutt. But I can't use gnupg with mutt out of the box:
> > the muttrc has to modified to tell mutt explicitel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Said Markus Ni?l on Sun, Aug 25, 2002 at 04:38:26PM +0200:
> I have recently installed gnupg-1.0.7 and I'd like to use it with
> mutt. But I can't use gnupg with mutt out of the box: the muttrc has
> to modified to tell m
Hi Markus,
* Markus Nißl <[EMAIL PROTECTED]> [25. Aug. 2002]:
> Hi mutt experts!
>
> I have recently installed gnupg-1.0.7 and I'd like to use it with
> mutt. But I can't use gnupg with mutt out of the box: the muttrc
> has to modified to tell mutt explicitely t
Hi mutt experts!
I have recently installed gnupg-1.0.7 and I'd like to use it with
mutt. But I can't use gnupg with mutt out of the box: the muttrc
has to modified to tell mutt explicitely the different commands
to sign and encrypt, etc. Where can I find such a setup for
gnupg?
I know
--
Jussi Ekholm -- [EMAIL PROTECTED] -- http://erppimaa.ihku.org/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9E3W2AtEARxQQCB4RAi0gAJ9JUlY7Gq0FEdKZkmWgLSctDxscsgCfasDp
WlNgiGNbdbMx9gpvNH38Ylk=
=nppD
-END PGP SIGNATURE-
ty thorough lists of keyservers there.
- --
Jussi Ekholm -- [EMAIL PROTECTED] -- http://erppimaa.ihku.org/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9E3ULAtEARxQQCB4RAvR0AJ0bKCIPKQ/noEhjE9nTY5wudQTq+gCghSWE
IefBJlDaEvwmsPImahHzgXc=
=DdPW
-END PGP SIGNATURE-
template options file to get some
more:
,[ ~/.gnupg/options ]-
| [...]
| # Use "host -l pgp.net | grep www" to figure out a keyserver.
| [...]
`-
(note: '-l' is important, won't work otherwise)
Cheers, Rocco
Kevin --
We're starting to move dangerously near the edge of topic...
...and then Kevin Coyner said...
%
% On Mon, Jun 10, 2002 at 07:09:18AM -0500, David T-G wrote..
% >
% > %
% > % I'm using the new 1.0.7,
% >
% > OK. If you've never used gpg before this then you're probably fine; if
On Mon, Jun 10, 2002 at 07:09:18AM -0500, David T-G wrote..
> Kevin, et al --
>
> %
> % I'm using the new 1.0.7,
>
> OK. If you've never used gpg before this then you're probably fine; if
> you're upgrading, there are some particular caveats.
>
New user. Can't you tell? I thought it w
Aaron --
...and then Aaron Goldblatt said...
%
% > keyserver-options auto-key-retrieve
%
% When I add this (1.0.7), I get:
%
% [-- PGP output follows (current time: Mon 10 Jun 2002 02:17:15 AM CDT)
% --]
% gpg: /home/rnbwpnt/.gnupg/options:108: invalid optionncrypted bodies,
% [-- End
cle not necessarily in sync with each
other, and I think more than just a day out after a new key is uploaded,
but it's been a long time since I've bothered to take note).
...
% As always, thanks for the tremendous help.
Sure thing!
% Kevin
%
% --
%
% Kevin Coyner
% mailto: [EMAIL
1 - 100 of 328 matches
Mail list logo
