1 |
There's more than one bugs that I need to report so please bear with me as I |
2 |
describe how I came across them: |
3 |
|
4 |
1st Bug |
5 |
|
6 |
Recently I tried to import a personal SSL certificate from Comodo into |
7 |
Kleopatra version 2.0.9. Every time it fails when I enter a passphrase to |
8 |
import it. Converting the .pkcs12 certificate and key file into a .pem format |
9 |
and then trying to import that also fails with a "BER error". |
10 |
|
11 |
The Gnupg Log Viewer shows: |
12 |
=========================================================== |
13 |
[2010-05-07T22:24:22] Log cleared |
14 |
[client at fd 4 connected] |
15 |
4 - 2010-05-07 22:24:25 gpgsm[14692]: enabled debug flags: assuan |
16 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: -> # Home: ~/.gnupg |
17 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: -> # Config: |
18 |
/home/michael/.gnupg/gpgsm.conf |
19 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: -> # AgentInfo: /tmp/gpg- |
20 |
yRFiu9/S.gpg-agent:13728:1 |
21 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: -> # DirmngrInfo: [not set] |
22 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: -> OK GNU Privacy Guard's S/M |
23 |
server 2.0.14 ready |
24 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: <- OPTION display=:0.0 |
25 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: -> OK |
26 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: <- OPTION enable-audit-log=1 |
27 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: -> OK |
28 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: <- INPUT FD=21 |
29 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: -> OK |
30 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: <- IMPORT |
31 |
4 - 2010-05-07 22:24:25 gpgsm[14692]: invalid radix64 character 2d skipped |
32 |
4 - 2010-05-07 22:24:25 gpgsm[14692]: invalid radix64 character 3a skipped |
33 |
4 - 2010-05-07 22:24:25 gpgsm[14692]: invalid radix64 character 2c skipped |
34 |
4 - 2010-05-07 22:24:25 gpgsm[14692]: invalid radix64 character 2d skipped |
35 |
4 - 2010-05-07 22:24:25 gpgsm[14692]: invalid radix64 character 3a skipped |
36 |
4 - 2010-05-07 22:24:25 gpgsm[14692]: invalid radix64 character 2d skipped |
37 |
4 - 2010-05-07 22:24:25 gpgsm[14692]: total number processed: 0 |
38 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: -> S IMPORT_RES 0 0 0 0 0 0 0 0 |
39 |
0 0 0 0 0 0 |
40 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: -> ERR 150995078 BER error |
41 |
<KSBA> |
42 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: <- BYE |
43 |
4 - 2010-05-07 22:24:25 gpgsm[14692.0] DBG: -> OK closing connection |
44 |
[client at fd 4 disconnected] |
45 |
=========================================================== |
46 |
|
47 |
Would you know what the entries invalid "radix64 character" mean? This error |
48 |
seems to be repeated with a 32bit Gentoo system of mine too (I initially |
49 |
suspected that it was only relevant to this amd64 arch). |
50 |
|
51 |
|
52 |
2nd Bug |
53 |
|
54 |
Looking into the Gnupg Log Viewer options, I changed the Default log level |
55 |
from Basic to Guru, to see if I can get some more information about this |
56 |
error. Well, that proved to be a bad mistake which crippled my log viewer! |
57 |
|
58 |
Now, I cannot launch the Gnupg Log Viewer. It crashes every time, after it |
59 |
dumps a load of files like "dbgmd-00001.hash.cert" into ~/. |
60 |
|
61 |
Also I cannot change the log viewer's default log level anymore! Trying to do |
62 |
it from within Kleopatra takes, as shown in ~/.gnupg/dirmngr.conf: |
63 |
=========================================================== |
64 |
###+++--- GPGConf ---+++### |
65 |
debug-level basic |
66 |
log-file socket:///home/michael/.gnupg/log-socket |
67 |
###+++--- GPGConf ---+++### Sat May 8 11:45:20 2010 BST |
68 |
# GPGConf edited this configuration file. |
69 |
# It will disable options before this marked block, but it will |
70 |
# never change anything below these lines. |
71 |
=========================================================== |
72 |
|
73 |
but as soon as I launch Gnupg Log Viewer it reverts back to Guru. Any idea |
74 |
what gpgconf reads to reset this damn log level from Basic to Guru? |
75 |
|
76 |
Remerging a load of apps including dirmngr does not fix it. :-( |
77 |
|
78 |
This is what the gconf settings for dirmngr show: |
79 |
=========================================================== |
80 |
$ gpgconf --list-options dirmngr |
81 |
Monitor:1:0:Options controlling the diagnostic output:0:0:::: |
82 |
verbose:4:0:verbose:0:0:::: |
83 |
quiet:0:0:be somewhat more quiet:0:0:::: |
84 |
no-greeting:0:3::0:0:::: |
85 |
Format:1:0:Options controlling the format of the output:0:0:::: |
86 |
Configuration:1:2:Options controlling the configuration:0:0:::: |
87 |
Debug:1:1:Options useful for debugging:0:0:::: |
88 |
debug-level:18:1:set the debugging level to LEVEL:1:1:LEVEL:"none::"guru |
89 |
log-file:0:1:write server mode logs to |
90 |
FILE:32:1:FILE:::"socket%3a///home/michael/.gnupg/log-socket |
91 |
faked-system-time:0:3::3:3:::: |
92 |
Enforcement:1:0:Options controlling the interactivity and enforcement:0:0:::: |
93 |
force:0:0:force loading of outdated CRLs:0:0:::: |
94 |
HTTP:1:1:Configuration for HTTP servers:0:0:::: |
95 |
disable-http:0:1:inhibit the use of HTTP:0:0:::: |
96 |
ignore-http-dp:0:1:ignore HTTP CRL distribution points:0:0:::: |
97 |
http-proxy:0:1:redirect all HTTP requests to URL:1:1:URL::: |
98 |
honor-http-proxy:0:1:use system's HTTP proxy setting:0:0:::: |
99 |
LDAP:1:0:Configuration of LDAP servers to use:0:0:::: |
100 |
disable-ldap:0:1:inhibit the use of LDAP:0:0:::: |
101 |
ignore-ldap-dp:0:1:ignore LDAP CRL distribution points:0:0:::: |
102 |
ldap-proxy:0:0:use HOST for LDAP queries:1:1:HOST::: |
103 |
only-ldap-proxy:0:1:do not use fallback hosts with --ldap-proxy:0:0:::: |
104 |
=========================================================== |
105 |
|
106 |
Any help to solve this mess would be greatly appreciated. |
107 |
-- |
108 |
Regards, |
109 |
Mick |