Mailing List Archive

On Mittwoch, 7. Januar 2009, Andreas Petzold wrote:
> when opening kleopatra it throws the following error
>
> An error occurred while fetching the certificates from the backend:
> End of file

From the log it seems to
Maybe one that does not result into anything.
Does it go away if you switch away from external certificates
to internal ones in the search dialog?

> since I've switched to RHEL5 (gnupg2 2.0.8) and kde 3.5.10. I've  
> checked the gnupg log, but haven't found a clue about the cause of the  
> problem. The logfile can be found here
>
> http://tinyurl.com/7alk5h

4 - 2009-01-07 17:30:54 gpgsm[15650]: looking up issuer at external location
4 - 2009-01-07 17:30:54 gpgsm[15650]: can't connect to the dirmngr - trying
fall back
4 - 2009-01-07 17:30:54 gpgsm[15650]: no running dirmngr - starting
`/usr/bin/dirmngr'
[client at fd 6 connected]
6 - 2009-01-07 17:30:54 dirmngr[15651]: permanently loaded certificates: 0
6 - 2009-01-07 17:30:54 dirmngr[15651]: runtime cached certificates: 0
6 - 2009-01-07 17:30:54 dirmngr[15651.0] DBG: -> # Home: ~/.gnupg
6 - 2009-01-07 17:30:54 dirmngr[15651.0] DBG: -> #
Config: /home/petzold/.gnupg/dirmngr.conf
6 - 2009-01-07 17:30:54 dirmngr[15651.0] DBG: -> OK Dirmngr 1.0.0 at your
service
[client at fd 4 disconnected]
5 - 2009-01-07 17:30:54 gpg-agent[7363.6] DBG: <- [EOF]
5 - 2009-01-07 17:30:54 gpg-agent[7363]: handler 0xf347af0 for fd 6
terminated
6 - 2009-01-07 17:30:54 dirmngr[15651.0] DBG: <- [EOF]
[client at fd 6 disconnected]

> Please let me know if additional info is required to track down the  
> cause of the problem.

You could try to look enable and look into the dirmngr log.
It might be that this is a superflous messsage.
Do you encounter other problems?

--
Managing Director - Owner: www.intevation.net (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

Hi,

Quoting Bernhard Reiter <bernhard@intevation.de>:

> On Mittwoch, 7. Januar 2009, Andreas Petzold wrote:
>> when opening kleopatra it throws the following error
>>
>> An error occurred while fetching the certificates from the backend:
>> End of file
>
> From the log it seems to
> Maybe one that does not result into anything.

sorry, I don't understand what you mean here?

> Does it go away if you switch away from external certificates
> to internal ones in the search dialog?

switching from local to external certs doesn't result in an error.
switching back to local certs (which is the default) causes the error.

>
>> The logfile can be found here
>>
>> http://tinyurl.com/7alk5h
>
> 4 - 2009-01-07 17:30:54 gpgsm[15650]: looking up issuer at
> external location
> 4 - 2009-01-07 17:30:54 gpgsm[15650]: can't connect to the dirmngr - trying
> fall back
> 4 - 2009-01-07 17:30:54 gpgsm[15650]: no running dirmngr - starting
> `/usr/bin/dirmngr'
> [client at fd 6 connected]
> 6 - 2009-01-07 17:30:54 dirmngr[15651]: permanently loaded certificates: 0
> 6 - 2009-01-07 17:30:54 dirmngr[15651]: runtime cached certificates: 0
> 6 - 2009-01-07 17:30:54 dirmngr[15651.0] DBG: -> # Home: ~/.gnupg
> 6 - 2009-01-07 17:30:54 dirmngr[15651.0] DBG: -> #
> Config: /home/petzold/.gnupg/dirmngr.conf
> 6 - 2009-01-07 17:30:54 dirmngr[15651.0] DBG: -> OK Dirmngr 1.0.0 at your
> service
> [client at fd 4 disconnected]
> 5 - 2009-01-07 17:30:54 gpg-agent[7363.6] DBG: <- [EOF]
> 5 - 2009-01-07 17:30:54 gpg-agent[7363]: handler 0xf347af0 for fd 6
> terminated
> 6 - 2009-01-07 17:30:54 dirmngr[15651.0] DBG: <- [EOF]
> [client at fd 6 disconnected]
>
>> Please let me know if additional info is required to track down the  
>> cause of the problem.
>
> You could try to look enable and look into the dirmngr log.
> It might be that this is a superflous messsage.

my dirmngr.conf contains

debug-level expert
log-file socket:///home/petzold/.gnupg/log-socket

so I guess the log I've posted should contain all relevant log
messages from dirmngr. Should I change these settings?

I played around a bit and found out that if I disable

Kleopatra->Settings->Configure GpgME Backend->GPG for S/MIME-> Fetch
missing issuer certs

then the error is gone.

> Do you encounter other problems?

After disabling the option above, I can't verify any signatures in
kmail. Actually, it also doesn't work if I enable the fetch option.
However, I can validate all the certificates inside kleopatra if the
fetch option is disabled.

A log of the failed signature validation can be found here:

http://tinyurl.com/8bo4ru

To my quite untrained eye, there is no indication of a failure in this
log. I'm at loss :-( Hope we can track this down sooner rather than
later.

Cheers,

Andreas



_______________________________________________
Gpa-dev mailing list
Gpa-dev@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gpa-dev

On Dienstag, 13. Januar 2009, Andreas Petzold wrote:
> Quoting Bernhard Reiter <bernhard@intevation.de>:
> > On Mittwoch, 7. Januar 2009, Andreas Petzold wrote:
> >> when opening kleopatra it throws the following error
> >>
> >> An error occurred while fetching the certificates from the backend:
> >> End of file
> >
> > From the log it seems to
> > Maybe one that does not result into anything.
>
> sorry, I don't understand what you mean here?

I've meant that it tried to fetch and external certificate
as far as I have studied the log.

> > Does it go away if you switch away from external certificates
> > to internal ones in the search dialog?
>
> switching from local to external certs doesn't result in an error.
> switching back to local certs (which is the default) causes the error.
>
> >> The logfile can be found here
> >>
> >> http://tinyurl.com/7alk5h
> >
> > 4 - 2009-01-07 17:30:54 gpgsm[15650]: looking up issuer at
> > external location
> > 4 - 2009-01-07 17:30:54 gpgsm[15650]: can't connect to the dirmngr -
> > trying fall back
> > 4 - 2009-01-07 17:30:54 gpgsm[15650]: no running dirmngr - starting
> > `/usr/bin/dirmngr'
> > [client at fd 6 connected]
> > 6 - 2009-01-07 17:30:54 dirmngr[15651]: permanently loaded
> > certificates: 0 6 - 2009-01-07 17:30:54 dirmngr[15651]: runtime
> > cached certificates: 0 6 - 2009-01-07 17:30:54 dirmngr[15651.0] DBG: -> #
> > Home: ~/.gnupg 6 - 2009-01-07 17:30:54 dirmngr[15651.0] DBG: -> #
> > Config: /home/petzold/.gnupg/dirmngr.conf
> > 6 - 2009-01-07 17:30:54 dirmngr[15651.0] DBG: -> OK Dirmngr 1.0.0 at
> > your service
> > [client at fd 4 disconnected]
> > 5 - 2009-01-07 17:30:54 gpg-agent[7363.6] DBG: <- [EOF]
> > 5 - 2009-01-07 17:30:54 gpg-agent[7363]: handler 0xf347af0 for fd 6
> > terminated
> > 6 - 2009-01-07 17:30:54 dirmngr[15651.0] DBG: <- [EOF]
> > [client at fd 6 disconnected]
> >
> >> Please let me know if additional info is required to track down the  
> >> cause of the problem.
> >
> > You could try to look enable and look into the dirmngr log.
> > It might be that this is a superflous messsage.
>
> my dirmngr.conf contains
>
> debug-level expert
> log-file socket:///home/petzold/.gnupg/log-socket
>
> so I guess the log I've posted should contain all relevant log
> messages from dirmngr. Should I change these settings?

No. You could try debug-level guru or a newer dirmngr.

> I played around a bit and found out that if I disable
>
> Kleopatra->Settings->Configure GpgME Backend->GPG for S/MIME-> Fetch
> missing issuer certs
>
> then the error is gone.

Could you post a message where this problem appears to the public?
At least I could check if I have the same problems with the particular
certificate.
>
> > Do you encounter other problems?
>
> After disabling the option above, I can't verify any signatures in
> kmail. Actually, it also doesn't work if I enable the fetch option.
> However, I can validate all the certificates inside kleopatra if the
> fetch option is disabled.
>
> A log of the failed signature validation can be found here:
>
> http://tinyurl.com/8bo4ru
>
> To my quite untrained eye, there is no indication of a failure in this
> log. I'm at loss :-( Hope we can track this down sooner rather than
> later.

What is the result: Not enough information to verify signature? Yellow color?
Is there an audit log button? If yes, what does pressing it say?
What is the debugging level of gpgsm.conf? Maybe try "expert" or "guru" there.
You should also check the .xsession output of kmail.

Bernhard


--
Managing Director - Owner: www.intevation.net (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

Hi Bernhard,

thanks for bearing with me on that problem.

>> so I guess the log I've posted should contain all relevant log
>> messages from dirmngr. Should I change these settings?
>
> No. You could try debug-level guru or a newer dirmngr.

Newer dirmngr (currently 1.0.0) is not an immediate option, but I've
set the debug level for dirmngr to guru. However, w/o any visible
effect whatsoever :-(

http://tinyurl.com/7a2bcu

>
>> I played around a bit and found out that if I disable
>>
>> Kleopatra->Settings->Configure GpgME Backend->GPG for S/MIME-> Fetch
>> missing issuer certs
>>
>> then the error is gone.
>
> Could you post a message where this problem appears to the public?
> At least I could check if I have the same problems with the particular
> certificate.

Well, the problem I've described above, is not connected to any
message. It's inside kleopatra. kleopatra is throwing the error
when listing all the certs. I would have expected to find the culprit
cert in the logfile, but alas...

I'll see if it helps to delete all the certs one-by-one. Maybe, I can
track down the culprit cert.

>>
>> > Do you encounter other problems?
>>
>> After disabling the option above, I can't verify any signatures in
>> kmail. Actually, it also doesn't work if I enable the fetch option.
>> However, I can validate all the certificates inside kleopatra if the
>> fetch option is disabled.
>>
>> A log of the failed signature validation can be found here:
>>
>> http://tinyurl.com/8bo4ru
>>
>> To my quite untrained eye, there is no indication of a failure in this
>> log. I'm at loss :-( Hope we can track this down sooner rather than
>> later.
>
> What is the result: Not enough information to verify signature? Yellow color?

kmail shows the yellow bars and:

Not enough information to check signature.
Status: No status information available. No Audit Log available

> Is there an audit log button? If yes, what does pressing it say?
> What is the debugging level of gpgsm.conf? Maybe try "expert" or
> "guru" there.

The guru log is here

http://tinyurl.com/82kz3l

> You should also check the .xsession output of kmail.

I can't find anything related to kmail .xsession-errors.

Cheers,

Andreas



_______________________________________________
Gpa-dev mailing list
Gpa-dev@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gpa-dev