chrony audit
Miroslav Lichvar <[email protected]> Fri, 15 Sep 2017 15:17:36 +0200
| Newsgroups | gmane.comp.time.chrony.announce,gmane.comp.time.chrony.devel,gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <20170915131736.GC9412@localhost> |
--2B/JsCI69OhZNC5r Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I have some good news. The chrony source code was recently audited by Cure53. The audit was organized by Mozilla and funded by the Linux Foundation's Core Infrastructure Initiative (CII). The report is available here: https://wiki.mozilla.org/images/e/e4/Chrony-report.pdf In summary, the audit found only two minor issues, which could theoretically be exploited in future, but didn't have a security impact in the current code. Both issues were fixed in chrony-3.2-pre2. --=20 Miroslav Lichvar --2B/JsCI69OhZNC5r Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlm70vAACgkQX/BvKboeATvBpwCgkvfAChi0DvCd0GcqiVbUhsZU qr4Anjef5vTnM305sIWPxSh/Hjr9SXwS =/1LS -----END PGP SIGNATURE----- --2B/JsCI69OhZNC5r-- -- To unsubscribe email chrony-announce-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "unsubscribe" in the subject. For help email chrony-announce-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "help" in the subject. Trouble? Email [email protected]