From: Jack Twilley <jmt+usenet@tbe.net>
Subject: Re: Force Oort to verify sigs?
Date: 17 Mar 2001 18:07:14 -0800 [thread overview]
Message-ID: <86r8zv4yp9.fsf@duchess.twilley.org> (raw)
In-Reply-To: <868zm4yzat.fsf@mediawars.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
>>>>> "Shigeki" == Shigeki Uno <shigeki@mediawars.ne.jp> writes:
Shigeki> Hi, ding users.
[...]
Shigeki> as for me, it complains the following error in mini buffer.
Shigeki> BAD SIGNATURE claiming to be from 'Shigeki Uno (UNO PROJECT)
Shigeki> <shigeki@mediawars.ne.jp>'
Shigeki> is something wrong with my Gnupg-1.0.4?
I don't know. I do know that your message's signature failed, with
"No details." When I look in the *MailCrypt* buffer, it says:
unknown hash: unable to verify signature.
I can see other people's signatures for the most part.
I'm using: PGP for Personal Privacy Version: unix50i1b
Now, what *I*'d like to see is a hack to bbdb such that every time I
successfully validate someone's signature, their bbdb record is
updated such that mail I send to them is encrypted by default. If
that makes any sense.
Jack.
--
Jack Twilley
jmt at tbe dot net
http colon slash slash www dot tbe dot net slash tilde jmt slash
[-- Attachment #2: Type: application/pgp-signature, Size: 277 bytes --]
next prev parent reply other threads:[~2001-03-18 2:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-17 16:44 Alan Shutko
2001-03-17 16:52 ` ShengHuo ZHU
2001-03-17 19:23 ` Shigeki Uno
2001-03-17 19:53 ` Shigeki Uno
2001-03-18 1:28 ` Daniel Pittman
2001-03-21 22:21 ` Jake Colman
2001-03-22 2:10 ` Colin Marquardt
2001-03-22 3:01 ` Daniel Pittman
2001-03-22 18:19 ` Jake Colman
2001-03-22 20:34 ` Paul Jarc
2001-03-22 21:47 ` Jake Colman
2001-03-22 22:47 ` Paul Jarc
2001-03-23 1:39 ` Russ Allbery
2001-03-23 15:54 ` Paul Jarc
2001-03-26 17:20 ` Jake Colman
2001-03-26 17:56 ` Josh Huber
2001-03-26 18:58 ` Jake Colman
2001-03-18 2:07 ` Jack Twilley [this message]
2001-03-17 16:52 ` Karl Kleinpaste
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=86r8zv4yp9.fsf@duchess.twilley.org \
--to=jmt+usenet@tbe.net \
/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).