1 |
On Thu, Jan 19, 2012 at 01:22:50PM -0600, Paul Hartman wrote: |
2 |
> On 1/19/2012 11:32 AM, Chris Walters wrote: |
3 |
> > On 1/19/2012 11:57 AM, Frank Steinmetzger wrote: |
4 |
> >> On Thu, Jan 19, 2012 at 12:53:07AM -0600, Dale wrote: |
5 |
> >> |
6 |
> >>> While on this subject, sort of. Who on here as their email set up to |
7 |
> >>> encrypt and decrypt emails? I want to test some things OFF LIST. |
8 |
> >> |
9 |
> >> Well, if you had signed your mail, then I could write you encrypted. :) |
10 |
> > |
11 |
> > This is a test. Enigmail has been trying to use a revoked and expired key to |
12 |
> > sign my messages, lately. |
13 |
> > |
14 |
> > Chris |
15 |
> |
16 |
> Looks good to me, at least based on what's presently available in the |
17 |
> keyservers. |
18 |
|
19 |
Hm... I seem to be too dumb. Mutt tells me that the msg is signed, but doesn't |
20 |
tell me by whom (I know that I need to have the public key in my keyring to see |
21 |
a name, but it doesn't even tell me the key ID). Saving the whole mail to a |
22 |
file and verifying the sig doesn't work either, that too is obvious because 1) |
23 |
only the text is signed, not the rest of the mail and b) the signed stuff and |
24 |
the sig need to be two different files for gpg --verify to work. So I saved the |
25 |
signature.asc and the text separately. Now verification works and I see a key |
26 |
ID, but using gpg --search <key ID> doesn't find the given key on the server. |
27 |
|
28 |
GPGing was much easier when KMail still worked. ^^ |
29 |
-- |
30 |
Gruß | Greetings | Qapla' |
31 |
I forbid any use of my email addresses with Facebook services. |
32 |
|
33 |
The computer is not a miracle. |
34 |
It only works so fast because it doesn’t think. |