Package: tinyca Version: 0.7.5-5 Severity: important Dear Maintainer,
Microsoft released a SHA1 Deprecation Policy[1]. Example: "For SSL certificates, Windows will stop accepting SHA1 end-entity certificates by 1 January 2017. This means any time valid SHA1 SSL certificates must be replaced with a SHA2 equivalent by 1 January 2017." Google also deprecates SHA1 end-entity certificates within Chrome[2]: - "All SHA-1-using certificates that are valid AFTER 2017/1/1 are treated insecure, but without an interstitial. That is, they will receive a degraded UI indicator, but users will NOT be directed to click through an error page." - "Additionally, the mixed content blocker will be taught to treat these as mixed content, which WILL require a user action to interact with." - "All SHA-1-using certificates that are valid AFTER 2016/1/1 are treated as insecure, but without an interstitial. They will receive a degraded UI indicator, but will NOT be treated as mixed content." TinyCA has no SHA2 support. So, does TinyCA become deprecated as well? Kind regards, Aiko Barz [1]: http://blogs.technet.com/b/pki/archive/2013/11/12/sha1-deprecation- policy.aspx [2]: https://groups.google.com/a/chromium.org/forum/#!msg/blink- dev/2-R4XziFc7A/YO0ZSrX_X4wJ -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages tinyca depends on: ii libgtk2-perl 2:1.2492-2+b1 ii liblocale-gettext-perl 1.05-8+b1 ii openssl 1.0.1i-2 Versions of packages tinyca recommends: ii zip 3.0-8 tinyca suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
