On Tue, Nov 22, 2016 at 9:36 AM, Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx> wrote: > On Mon, 2016-11-21 at 12:07 -0600, Michael Catanzaro wrote: >> On Mon, 2016-11-21 at 18:13 +0100, Jan Kurik wrote: >> > >> > As it is now, the System-wide crypto policy in F25 is enforced by >> > the >> > OpenSSL, GnuTLS and NSS TLS libraries. To harmonize crypto across >> > all >> > applications in Fedora, including the Java ones, OpenJDK is >> > enhanced >> > to respect the settings of the system-wide crypto policy as well. >> >> This is no longer true. I just got a questionable F24 stable release >> update that implemented this change, so I presume F25 will have it >> soon >> enough. We probably don't want an F26 change proposal for a feature >> that's implemented in a zero-day F25 update. > > That wasn't the plan, but it could have been a mistake. Could you add > more info at: > https://bugzilla.redhat.com/show_bug.cgi?id=1249083 Hi, as required by the Change process, after a week since the proposal was announced, I have put this on the FESCo meeting agenda for the upcoming Friday. However, reading the discussion in this email thread and in the tracking bug [2] I am puzzled what the current state is. Is it already delivered, or is it delivered but disabled, or is it in any other state ? May I ask the maintainer, or any engineer who is working on this to clarify the current state of implementation before the FESCo meeting, so the FESCo has clear information they can use to make a decision ? [1] https://pagure.io/fesco/issue/1635#comment-43494 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1249083 Thanks and Best Regards, Jan ______________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
