From: Jan Girlich <vollkorn@freenet.de>
To: gentoo-user-de@lists.gentoo.org
Subject: [gentoo-user-de] Enigmail & gpg - Key-Signieren geht nicht
Date: Tue, 27 Dec 2005 15:44:59 +0100 [thread overview]
Message-ID: <43B1536B.20306@freenet.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hallo,
ich bin vor kurzem in PGP/GPG eingestiegen und habe mir die
Enigmail-Extension für Thunderbird von deren Internetseite installiert.
Soweit funktioniert auch alles ganz toll wie Keys herunterladen,
ausgehende Mails signieren, empfangene verifizieren, Ent- und Verschlüsseln.
Aber: Nach meiner ersten Key-Signing-Party habe ich jetzt das Problem,
dass ich keine Schlüssel signieren kann:
rechte Maustatse auf einen Schlüssel -> sign key -> OK ->
"Key signing failed
An undefined error occurred."
Wenn ich den gpg-Befehl von Enigmail per Hand ausführe erhalte ich einen
Lizenzhinweis und dann passiert nichts bis ich Enter drücke. Versteht
auch gar nicht was da genau passiert:
jan@jan ~ $ /usr/bin/gpg --charset utf8 --passphrase-fd 0
- --no-use-agent --no-tty --status-fd 1 --logger-fd 1 --command-fd 0 -u
0xAAAAAAAAAAAAAAAA --ask-cert-level --edit-key BBBBBBBBBBBBBBBB sign
gpg (GnuPG) 1.4.2; Copyright (C) 2005 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.
<ENTER>
[GNUPG:] GET_BOOL keyedit.sign_all.okay
<ENTER>
[GNUPG:] GOT_IT
[GNUPG:] GET_LINE keyedit.prompt
<ENTER>
[GNUPG:] GOT_IT
[GNUPG:] GET_LINE keyedit.prompt
<ENTER>
[GNUPG:] GOT_IT
[GNUPG:] GET_LINE keyedit.prompt
<STRG+C>
enigerr.txt gibt folgendes:
enigmail> /usr/bin/gpg --charset utf8 --passphrase-fd 0 --no-use-agent
--no-tty --status-fd 1 --logger-fd 1 --command-fd 0 -u
0xAAAAAAAAAAAAAAAA --ask-cert-level --edit-key BBBBBBBBBBBBBBBB sign
2005-12-27 15:26:04.860 enigmail.js: Enigmail.execStart: pipetrans =
[xpconnect wrapped nsIPipeTransport]
2005-12-27 15:26:04.880 [GNUPG:] GET_BOOL keyedit.sign_all.okay
2005-12-27 15:26:04.883 [GNUPG:] GOT_IT
2005-12-27 15:26:04.883 [GNUPG:] GET_LINE sign_uid.class
2005-12-27 15:26:04.885 [GNUPG:] GOT_IT
2005-12-27 15:26:04.885 [GNUPG:] GET_BOOL sign_uid.okay
2005-12-27 15:26:05.139 [GNUPG:] GOT_IT
2005-12-27 15:26:05.140 [GNUPG:] USERID_HINT AAAAAAAAAAAAAAAA Jan
Girlich <vollkorn@freenet.de>
2005-12-27 15:26:05.141 [GNUPG:] NEED_PASSPHRASE AAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAA 17 0
2005-12-27 15:26:05.142 [GNUPG:] GOOD_PASSPHRASE
2005-12-27 15:26:05.142 [GNUPG:] GOOD_PASSPHRASE
2005-12-27 15:26:05.144 no more data
2005-12-27 15:26:05.145 enigmail.js: Enigmail.editKey: GnuPG terminated
with code=2
2005-12-27 15:26:05.146 enigmail.js: Enigmail.stillActive:
2005-12-27 15:26:07.121 enigmailUserSelection.js: enigmailBuildList
2005-12-27 15:26:07.122 enigmailCommon.js: EnigLoadKeyList
2005-12-27 15:26:07.123 enigmailCommon.js: EnigObtainKeyList
2005-12-27 15:26:07.124 enigmail.js: Enigmail.execCmd: command =
/usr/bin/gpg --charset utf8 --batch --no-tty --status-fd 2
- --with-fingerprint --fixed-list-mode --with-colons --list-keys
2005-12-27 15:26:07.125 enigmail.js: WriteFileContents:
file=/home/jan/.gpglog/eniginp.txt
2005-12-27 15:26:07.126 enigmail.js: WriteFileContents:
file=/home/jan/.gpglog/enigcmd.txt
2005-12-27 15:26:07.229 enigmail.js: WriteFileContents:
file=/home/jan/.gpglog/enigenv.txt
2005-12-27 15:26:07.234 enigmail.js: Enigmail.execCmd: copied command
line/env/input to files
/home/jan/.gpglog/enigcmd.txt/enigenv.txt/eniginp.txt
2005-12-27 15:26:07.235
Irgendeine Idee woran es liegen könnte?
Gruß
Jan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDsVNrvuM9o4Jvd/8RAomRAJ9v5mpeFFXOU97GUYWVKi5FbMM7OgCfSG6Q
EJwDHOT+6+zHK3JmvmluFgE=
=twip
-----END PGP SIGNATURE-----
--
gentoo-user-de@gentoo.org mailing list
next reply other threads:[~2005-12-27 14:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-27 14:44 Jan Girlich [this message]
2006-01-09 19:59 ` [gentoo-user-de] Enigmail & gpg - Key-Signieren geht nicht Jan Girlich
2006-01-09 20:31 ` Max Roder
2006-01-09 20:32 ` Steffen Rehn
2006-01-09 21:27 ` Sebastian Damm
2006-01-09 21:53 ` Steffen Rehn
2006-01-10 18:02 ` Jan Girlich
2006-01-10 19:55 ` Steffen Rehn
2006-01-09 22:44 ` Markus Wagner
2006-01-09 22:57 ` Markus Wagner
2006-01-10 18:15 ` Jan Girlich
2006-01-11 17:39 ` Jan Girlich
2006-01-11 18:00 ` Markus Wagner
2006-01-10 18:18 ` Jan Girlich
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=43B1536B.20306@freenet.de \
--to=vollkorn@freenet.de \
--cc=gentoo-user-de@lists.gentoo.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