Re: crypto-policies not very useful, FUTURE too strict?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2016-12-19 at 09:35 +0100, Nikos Mavrogiannopoulos wrote:

$ update-crypto-policies --set FUTURE
Setting system policy to FUTURE

$ wget https://github.com
Resolving github.com (github.com)... 192.30.253.112, 
192.30.253.113  
                                                     github.com
(github.com)|192.30.253.112|:443... connected
ERROR: The certificate of 'github.com' is not trusted.
ERROR: The certificate of 'github.com' was signed using an insecure
algorithm.

The example you have above is a glitch on the combination of the
shared
system store use and crypto policies at gnutls.

Actually it relates to a particular behavior of wget [0]. In fact it
was disabling the system-wide policy as soon as it was enabling it.

[0]. https://bugzilla.redhat.com/show_bug.cgi?id=1405956

regards,
Nikos
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux