On Sat, Jun 12, 2010 at 09:25:31AM -0400, Rob Owens wrote:
> Hey, I just noticed that there are 2 different keys for you on the public key
> server. Are you sure you're using the right one to verify the
> signatures?
Yes, there are two keys - old one and new one. Unfortunately, old one was
crea
On Sat, Jun 12, 2010 at 09:22:45AM -0400, Rob Owens wrote:
> (...)
>
> If this problem started when you imported your private key, then maybe
> that was not done correctly. Is there a step that needs to be taken
> besides simply importing? (I don't know the answer to that).
I think that now,
On Sat, 12 Jun 2010 01:52:54 +0300, Alexander Batischev wrote:
> On Fri, Jun 11, 2010 at 09:39:58PM +, Camaleón wrote:
(...)
>> Well, what we are testing here (by using another e-mail client) is GPG
>> and your keyring configuration, so you better try with a GUI e-mail
>> client that uses th
On Fri, Jun 11, 2010 at 08:48:09PM +0300, Alexander Batischev wrote:
> I'm using mutt for about a month already. Almost all problems already solved,
> I
> successfully moved to IMAP. It's time to get GPG signing to work.
>
> As you probably noticed, all my messages are signed. But when I open any
On Fri, Jun 11, 2010 at 08:48:09PM +0300, Alexander Batischev wrote:
> I'm using mutt for about a month already. Almost all problems already solved,
> I
> successfully moved to IMAP. It's time to get GPG signing to work.
>
> As you probably noticed, all my messages are signed. But when I open any
On Fri, Jun 11, 2010 at 09:39:58PM +, Camaleón wrote:
> > Better than before, but mutt still claims "signature can NOT be
> > verified"…
>
> Still? From where are you getting that "not verified" message? From
> Mutt's pager?
Yes, mutt's pager. Message appears at the very bottom of the s
On Sat, 12 Jun 2010 00:09:30 +0300, Alexander Batischev wrote:
> On Fri, Jun 11, 2010 at 06:59:23PM +, Camaleón wrote:
>> Then maybe is that you have to "explicitely" import the key and trust
>> that key. Did you already do that? :-?
>
> Well, okay, I set trust for my key to 5 (absolute) and
Done a little more research: I used lsign (local sign) command and signed
Andrei Popescu's key. Then I set full trust for it. After that, mutt showed me
message like that one showed in previous post: just two lines saying sign is
correct. But mutt still says that sign can not be verified! I definit
On Fri, Jun 11, 2010 at 06:59:23PM +, Camaleón wrote:
> On Fri, 11 Jun 2010 21:37:57 +0300, Alexander Batischev wrote:
>
> > On Fri, Jun 11, 2010 at 06:21:14PM +, Camale??n wrote:
>
> >> In order to verify a signed message, either you have to previosuly
> >> import the key into your keyri
On Fri, 11 Jun 2010 21:37:57 +0300, Alexander Batischev wrote:
> On Fri, Jun 11, 2010 at 06:21:14PM +, Camale??n wrote:
>> In order to verify a signed message, either you have to previosuly
>> import the key into your keyring or you need to setup Mutt to retrieve
>> the key from public server
On Fri, Jun 11, 2010 at 06:21:14PM +, Camale??n wrote:
> On Fri, 11 Jun 2010 21:03:22 +0300, Alexander Batischev wrote:
>
> > Some thoughts which just came to my head: can it be because of lack of
> > trusted keys? I did not set anyone's key as trusted, so I don't have web
> > of trust. This s
On Fri, 11 Jun 2010 21:03:22 +0300, Alexander Batischev wrote:
> Some thoughts which just came to my head: can it be because of lack of
> trusted keys? I did not set anyone's key as trusted, so I don't have web
> of trust. This still don't explain (in my opinion, at least) why my own
> signature c
Some thoughts which just came to my head: can it be because of lack of trusted
keys? I did not set anyone's key as trusted, so I don't have web of trust. This
still don't explain (in my opinion, at least) why my own signature can't be
verified.
--
Regards,
Alexander Batischev
1024D/69093C81
F870
On Fri, Apr 05, 2002 at 02:27:28PM -0500, Matthew Daubenspeck wrote:
> I am trying to setup Mutt so that it automatically retrieves keys from a
> keyserver is it is not listed in my public key. So far, I have the
> following in my .muttrc:
>
> set pgp_getkeys_command="gpg --recv-keys --keyserver w
On Wed, 03 Apr 2002, Vineet Kumar wrote:
> * Matthew Daubenspeck ([EMAIL PROTECTED]) [020403 08:14]:
> > I just got mutt working properly with gpg thanks to the archives. Does mutt
> > have to include the signature as an attachment, or can it do it in-line in
> > the message itself?
>
> pgp_crea
At 10:41 AM 4/3/2002, you wrote:
>* Matthew Daubenspeck ([EMAIL PROTECTED]) [020403 08:14]:
>> I just got mutt working properly with gpg thanks to the archives. Does mutt
>> have to include the signature as an attachment, or can it do it in-line in
>> the message itself?
>
>pgp_create_traditional
* Matthew Daubenspeck ([EMAIL PROTECTED]) [020403 08:14]:
> I just got mutt working properly with gpg thanks to the archives. Does mutt
> have to include the signature as an attachment, or can it do it in-line in
> the message itself?
pgp_create_traditional
>
> Can it also verify signatures th
both, absolute paths for pgpewrap and the --comment issue exist as
bugreports, so expect fixes sooner or later. for now, yes, just remove
all --comment '' from gpg.rc and change pgpewrap to
/usr/lib/mutt/pgpewrap
--
martin; (greetings from the heart of the sun.)
\ echo mailto:
On Tue, Oct 09, 2001 at 12:11:07PM +0200, Sven Gaerner wrote:
> Hi,
>
> I got a problem using mutt and gpg since the last update for these packages.
> When I try to encrypt and sign a message I get an error after entering
> my passphrase.
>
> Error message:
> gpg: Missing argument for option "--c
19 matches
Mail list logo
