Bug 885055 - [RFE] abrt fails to send reports/backtraces saying "Peer's Certificate has expired" when the system clock isn't correctly set, please don't use SSL (fallback with manual confirmation) or add more explanatory message
Summary: [RFE] abrt fails to send reports/backtraces saying "Peer's Certificate has ex...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libreport
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-07 11:31 UTC by Jaromír Cápík
Modified: 2016-02-01 01:57 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-25 22:59:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
abrt-logs.tgz (35.81 KB, application/x-gzip-compressed)
2012-12-07 13:35 UTC, Jaromír Cápík
no flags Details

Description Jaromír Cápík 2012-12-07 11:31:09 UTC
Description of problem:
Hello. I recently encountered a problem when trying to report crashes on ARM platform. Some of the boards have no realtime clock circuit and the time synchronisation fails when there's no internet connection. In such case abrt rejects to send reports, since the system clock is set to year 1999. It took me a while to figure it out and I don't expect our users to bother with resolving certificate problems when reporting issues. It would be nice to avoid using SSL when sending reports or at least add more explanatory warning to instruct users to check the system clock. As the message origin could be in a different component (ssl? yum?), feel free to change it. But I believe that a more generic and explanatory warning can always be displayed by abrt itself.

Version-Release number of selected component (if applicable):
abrt-2.0.18-1.fc18

Comment 1 Jiri Moskovcak 2012-12-07 12:20:38 UTC
Can you please run abrt-gui -vvv and attach the logs it produces when you try to report the bug?

Comment 2 Jaromír Cápík 2012-12-07 13:35:11 UTC
Created attachment 659366 [details]
abrt-logs.tgz

Comment 4 Michal Toman 2013-01-08 09:09:40 UTC
commit 9ac6208ec7b379c66ce30c570d12a07688d6b639
Author: Michal Toman <mtoman>
Date:   Mon Jan 7 17:15:20 2013 +0100

    uReport: add more explanatory message when upload fails

From the ABRT point of view, the upload failed. A better message has been added.

That's basically all we can do. The original reason (certificate expired) can't be detected from ABRT, because curl uses a single error code for all certificate-related issues.

Comment 5 Fedora Update System 2013-03-20 08:54:02 UTC
abrt-2.1.2-1.fc18,libreport-2.1.2-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/abrt-2.1.2-1.fc18,libreport-2.1.2-1.fc18

Comment 6 Fedora Update System 2013-03-22 00:21:33 UTC
Package abrt-2.1.2-1.fc18, libreport-2.1.2-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.1.2-1.fc18 libreport-2.1.2-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-4176/abrt-2.1.2-1.fc18,libreport-2.1.2-1.fc18
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2013-03-22 21:18:38 UTC
Package abrt-2.1.2-2.fc18, libreport-2.1.2-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.1.2-2.fc18 libreport-2.1.2-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-4176/abrt-2.1.2-2.fc18,libreport-2.1.2-2.fc18
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2013-03-25 22:59:26 UTC
abrt-2.1.2-2.fc18, libreport-2.1.2-2.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.