<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2017年07月05日 23:15, Burton, Ross
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJTo0LZryGcQvFq373ix5VHBrjP5NDzL8-onaX2_s0GnO_m6SQ@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On 5 July 2017 at 15:38, Khem Raj <span
dir="ltr"><<a href="mailto:raj.khem@gmail.com"
target="_blank" moz-do-not-send="true">raj.khem@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">It's probably more appropriate to pin it
at recipe level may be via package config OpenSSL is not
universal and some may even avoid it completely</div>
<span class=""></span></blockquote>
</div>
<br>
Agreed, whilst I'm not against adding options for enabling
insecure ciphers (verses just disabling them), I don't think
they deserve a DISTRO_FEATURE of their own.</div>
</div>
</blockquote>
<br>
The problem is that packages depend on openssl don't know whether
the cipher they need is disabled or not, so add such a
DISTRO_FEATURE to sync openssl and packages depends on it.<br>
I did it by a var before, but it looks not be a so official way.<br>
<br>
<br>
Thanks,<br>
Kai<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAJTo0LZryGcQvFq373ix5VHBrjP5NDzL8-onaX2_s0GnO_m6SQ@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Ross</div>
</div>
</blockquote>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Regards,
Neil | Kai Kang</pre>
</body>
</html>