I have uploaded a updated package for Mageia 5(+Cauldron). Formerly packaged version 3.0 is unusable due to change of CA certificate used by service provider asi of Sep 13th. CA change is user unfriendly and beyond capabilities of common users (by design to prevent casual users from changing them). Added new CA certificate, tested on both i586/x86_64, working again. Suggested advisory: ======================== Updated dslib packages to fix 'datovka' app and make it work again. As of 2015/09/13, ISDS (databox provider) changed CA certificate making Datovka app inoperable. Therefore patched dslib library was released which mitigates this problem. References: https://www.datoveschranky.info/-/upozorneni-na-prechod-na-sha-256-k-13-9-2015 ======================== Updated packages in {core/updates_testing: ======================== dslib-3.0-8.2.mga5 Source RPM: dslib-3.0-8.2.mga5.src.rpm Reproducible: Steps to Reproduce:
Reposting my comment from the dev list: Is this list of CA certs supposed to be different than the system ones? If not, you should actually remove the all_trusted.pem file and link it to /etc/pki/tls/certs/ca-bundle.crt.
Whiteboard: (none) => feedback
Very different - those CA certs are not included in standard CA bundle. Sole CA provider for DataBox system is http://www.postsignum.cz/
OK, thanks for the answer.
Whiteboard: feedback => (none)
Tested the package updates cleanly. Tomas states in comment 1 that this resolves the issue both arches but we have no way to independently verify this. Validating. Advisory uplaoded. Please push to 5 updates Thanks
Keywords: (none) => validated_updateWhiteboard: (none) => advisory mga5-64-okCC: (none) => sysadmin-bugs
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0131.html
Status: NEW => RESOLVEDResolution: (none) => FIXED