<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 1/4/22 10:26, Patrick Williams
wrote:<br>
</div>
<blockquote type="cite" cite="mid:YdSRSUhGYWj58YJb@heinlein">
<pre class="moz-quote-pre" wrap="">On Tue, Jan 04, 2022 at 07:32:06AM -0800, Johnathan Mantey wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Patrick....
On 12/30/21 05:52, Patrick Williams wrote:
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I am currently enabling this IMAGE_FEATURE in meta-facebook to avoid having this
happen again. Is there any reason why we wouldn't want to enable it by default
in meta-phosphor? There isn't really full support for non-root users in the
base systems anyhow, so is there anyone that wouldn't want "allow-root-login"
enabled by default?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Intel explicitly requires root login to be disabled for production
releases. Especially since the default password is a known quantity.
The Intel security audit group enforced blocking a default user for the
S2600 WF/BNP/STP series of servers. All user accounts are created using
local IPMI commands.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Is this currently able to be done with all upstream functionality or something
that only works in your own forks?</pre>
</blockquote>
<br>
As a developer for Intel I have to explicitly add 'debug-tweaks'
back into our bitbake config. I've not dug into who made the
decision, and which layer of the build process enforced it.<br>
<br>
<blockquote type="cite" cite="mid:YdSRSUhGYWj58YJb@heinlein">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Intel will prefer the existing behavior remain.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
It seems to me that the current behavior is broken for typical cases using
currently upstreamed functionality and so that's why I'm suggesting that
meta-phosphor be "fixed". It'd be pretty easy to IMAGE_FEATURE:remove this
for meta-intel-bmc, right?
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title></title>
<font color="#1F497D"><font face="Century Gothic">Johnathan Mantey<br>
<small>Senior Software Engineer</small><br>
<big><font color="#555555"><small><b>azad te</b><b>chnology
partners</b></small><br>
<small><font color="#1F497D"><small>Contributing to
Technology Innovation since 1992</small></font><small><br>
<font color="#1F497D">Phone: (503) 712-6764<br>
Email: <a href="mailto:johnathanx.mantey@intel.com"
class="moz-txt-link-freetext">johnathanx.mantey@intel.com</a></font></small><br>
<br>
</small></font></big></font></font> </div>
</body>
</html>