https://bugs.kde.org/show_bug.cgi?id=351861
--- Comment #8 from jan...@hbz-nrw.de ---
Can't actually reproduce this now (but also did not try very hard) - but in
hindsight the original problem might have been using plain "http" URLs for
accessing the CRL instead of "https"?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=351861
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=351861
--- Comment #6 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=351861
Justin Zobel changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=351861
--- Comment #4 from jan...@hbz-nrw.de ---
After reading through the comments again I come to think that - if all reports
here are really about the same underlying problem - this is probably the wrong
place for reporting the problem.
Given my own
https://bugs.kde.org/show_bug.cgi?id=351861
jan...@hbz-nrw.de changed:
What|Removed |Added
CC||jan...@hbz-nrw.de
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=351861
--- Comment #2 from Pavel ---
I have to add that even though CRL URL is reachable in terms of network
connection (I can download it with wget), there are still problems with using
S/MIME in KMail when "Never consult a CRL" is
https://bugs.kde.org/show_bug.cgi?id=351861
Pavel changed:
What|Removed |Added
CC||a...@thurston.ru
--- Comment #1 from