ports/99465: seahorse fails to sign an imported key - resulting in a "sign_transit" error
User1001
supraexpress at globaleyes.net
Sun Jun 25 22:20:24 UTC 2006
>Number: 99465
>Category: ports
>Synopsis: seahorse fails to sign an imported key - resulting in a "sign_transit" error
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Jun 25 22:20:22 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: User1001
>Release: FreeBSD 5.5-STABLE i386
>Organization:
>Environment:
System: FreeBSD 5.5-STABLE #4: Fri Jun 2 21:18:39 CDT 2006
root@:/usr/obj/usr/src/sys/XSYSTEM
gpgme-1.0.3_1 A library to make access to GnuPG easier
libassuan-0.6.10 IPC library used by GnuPG and gpgme
libgpg-error-1.3 Common error values for all GnuPG components
gnupg-1.4.3 The GNU Privacy Guard
gnupg-devel-1.9.20_1 Prerelease package of GnuPG extensions for GnuPG 2.0
seahorse-0.8_4
gnome-2.12.3
>Description:
1) import GPG key via seahorse GUI
2) attempt to SIGN newly imported key via seahorse GUI
3) signing key fails with
error popup:
Couldn't sign key General error
console messages:
** (seahorse:1353): CRITICAL **: file seahorse-key-op.c: line 360 (sign_transit): should \
not be reached
** (seahorse:1353): CRITICAL **: edit_key: assertion `GPG_IS_OK (err)' failed
4) no private key passphrase prompt or verification of private key to use prompt ever appears
5) using GPG manually, outside of SEAHORSE, there is no problem with signing the newly imported key
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list