<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>I think you read it backwards. I'll try again (inline below)</p>
<p>Scott</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 2022-07-27 09:57, Kumar, Chandan
wrote:<br>
</div>
<blockquote type="cite" cite="mid:SJ0PR14MB5261C7BF77232048CF1E2D5AF2979@SJ0PR14MB5261.namprd14.prod.outlook.com">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}code
{mso-style-priority:99;
font-family:"Courier New";}pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}span.ik-banner
{mso-style-name:ik-banner;
background:#E2E3E5;}span.ik-footer
{mso-style-name:ik-footer;
background:#E2E3E5;}span.EmailStyle27
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}ol
{margin-bottom:0in;}ul
{margin-bottom:0in;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div style="border:solid #9C6500 1.0pt;padding:2.0pt 2.0pt 2.0pt
2.0pt">
<p class="MsoNormal" style="line-height:12.0pt;background:#FFEB9C"><b><span style="font-size:10.0pt;color:#9C6500"></span></b><span style="font-size:10.0pt;color:red">[Please note: This e-mail
is from an EXTERNAL e-mail address]<o:p></o:p></span></p>
</div>
<div>
<div class="WordSection1">
<p class="MsoNormal">Hi Scott,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I was going through the procedure that
you have shared below. Please clarify these two points:
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="background:yellow;mso-highlight:yellow">The rpms
need to be unpacked, the relevant binaries signed with
correct keys, and the rpms reassembled. : </span>The
signing server unpacks images like BOOTX64, shim, shimx64
to get rpms, then signs it using `sbsign` and then repack
it as original image. Is this understanding correct ?</li>
</ul>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>It unpacks RPM: shim*rpm</p>
<p>It looks for files matching:</p>
<p> BOOTX64*, shim*, shimx64*, which it signs with the 'boot'
key; and</p>
<p> MokManager*, fallback*, mmx64*, fbx64* , which it signs with
the 'shim' key</p>
<p> Note: * above should be one of .efi or .EFI<br>
</p>
<p>Finally it repack the shim RPM file.</p>
<p><br>
</p>
<p>Repeat per the below table for the other RPMS.</p>
<p><br>
</p>
<p><br>
</p>
<blockquote type="cite" cite="mid:SJ0PR14MB5261C7BF77232048CF1E2D5AF2979@SJ0PR14MB5261.namprd14.prod.outlook.com">
<div>
<div class="WordSection1">
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="background:yellow;mso-highlight:yellow"><o:p></o:p></span></li>
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1"><span style="background:yellow;mso-highlight:yellow">shim.crt
- Certificated embedded within shim used to validate
kernel, grub
</span>: How is this certificate embedded inside shim
image ? <span style="background:yellow;mso-highlight:yellow">
<o:p></o:p></span></li>
</ul>
<p class="MsoNormal"><span style="background:yellow;mso-highlight:yellow"><o:p> </o:p></span></p>
<p class="MsoNormal">I got review notification for launchpad,
I had raised but could not find where to add comments so
replying to this mail.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal">Chandan Kumar.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Waines, Greg
<a class="moz-txt-link-rfc2396E" href="mailto:Greg.Waines@windriver.com"><Greg.Waines@windriver.com></a> <br>
<b>Sent:</b> Wednesday, July 13, 2022 8:14 PM<br>
<b>To:</b> StarlingX ML
<a class="moz-txt-link-rfc2396E" href="mailto:starlingx-discuss@lists.starlingx.io"><starlingx-discuss@lists.starlingx.io></a><br>
<b>Cc:</b> Kumar, Chandan
<a class="moz-txt-link-rfc2396E" href="mailto:Chandan.Kumar@commscope.com"><Chandan.Kumar@commscope.com></a><br>
<b>Subject:</b> FW: [Starlingx-discuss] Incorrect public
key for signed starlingX 5.0 iso .<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
</div>
<!--removed inky banner-->
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">Forwarding ….<o:p></o:p></p>
<p class="MsoNormal">I think scott meant this for the
starlingx discuss list.<o:p></o:p></p>
<p class="MsoNormal">Greg.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Little, Scott <<a href="mailto:Scott.Little@windriver.com" moz-do-not-send="true" class="moz-txt-link-freetext">Scott.Little@windriver.com</a>>
<br>
<b>Sent:</b> Wednesday, July 6, 2022 2:37 PM<br>
<b>To:</b> Waines, Greg <<a href="mailto:Greg.Waines@windriver.com" moz-do-not-send="true" class="moz-txt-link-freetext">Greg.Waines@windriver.com</a>><br>
<b>Subject:</b> Re: [Starlingx-discuss] Incorrect public
key for signed starlingX 5.0 iso .<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I'll attempt to answer this at a high
level.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Secure boot signing uses a
client/server approach. build-pkgs acts as the client.
The server holds the signing scripts and the keys used for
signing.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The client side code was released to
open source as part of StarlingX. The server side code
was not released.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The interface between client and server
is currently undocumented. I'll try to give an overview
as best I can. Basically it is a series of ssh/scp calls
made into signing server.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">'build-pkgs' requires that the
following environment variables be defined before it will
attempt to request a secure boot signing.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">export
SIGNING_SERVER=<signing-host><br>
export SIGNING_USER=<signing-user><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">export
SIGNING_SERVER_SCRIPT=<path-to-signing-script><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">'build-pkgs' further requires that
"$USER" == "jenkins", and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">export FORMAL_BUILD=1<o:p></o:p></p>
</div>
<p>If that is satisfied, it calls into 'sign-secure-boot'<o:p></o:p></p>
<p>'sign-secure-boot' contains a fairly good set of comments
describing what happens next.<o:p></o:p></p>
<p>The client side call sequence looks like this ...<o:p></o:p></p>
<p class="MsoNormal"> # Set up the server side directory
for files transfers.<br>
UPLOAD_PATH=`ssh $SIGNING_USER@$SIGNING_SERVER sudo
$SIGNING_SCRIPT -r` <o:p>
</o:p></p>
<p> # upload the original package<br>
scp -q $FILE $SIGNING_USER@$SIGNING_<a href="#REDACTED" moz-do-not-send="true">SERVER:$UPLOAD_PATH</a><o:p></o:p></p>
<p class="MsoNormal"> # Request that the package be signed<br>
ssh $SIGNING_USER@$SIGNING_SERVER sudo $SIGNING_SCRIPT
-v -i $UPLOAD_PATH/$(basename $FILE) $UNSIGNED_OPTION -t
$TYPE > $TMPFILE<o:p></o:p></p>
<p> # Download the file from the signing server<br>
DOWNLOAD_FILENAME=$(basename $OUTPUT_FILE)<br>
scp -q $SIGNING_USER@$SIGNING_<a href="#REDACTED" moz-do-not-send="true">SERVER:$OUTPUT_FILE</a> $(dirname
$FILE)<o:p></o:p></p>
<p>Within the signing server there are two keys used for
signing, known as the 'boot' key and the 'shim' key. The
public half of the 'boot' key must manually added to the
secure boot keychain in firmware. The 'boot' key signs
first executable loaded, contained in the 'shim' package.
The first executable must then install the public half of
the shim key (automatically) before passing control to grub,
and ultimately the kernel, both of which are signed by the
'shim' key.<o:p></o:p></p>
<p>Three packages need to be passed to the signing server.
The rpms need to be unpacked, the relevant binaries signed
with correct keys, and the rpms reassembled.<o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre>package key files to sign<o:p></o:p></pre>
<pre>========= ==== ===========================<o:p></o:p></pre>
<pre>shim boot BOOTX64, shim, shimx64<o:p></o:p></pre>
<pre> shim MokManager, fallback, mmx64, fbx64<o:p></o:p></pre>
<pre>grub shim grubx64.efi, gcdx64.efi<o:p></o:p></pre>
<pre>kernel shim vmlinuz<o:p></o:p></pre>
<p>NOTE: shim files to sign might include a '.efi' or '.EFI'
suffix. Sign those as well.<o:p></o:p></p>
<p>NOTE: some files may be absent in newer packages. It is
probably ok if some of the above are missing.<o:p></o:p></p>
<p><o:p> </o:p></p>
<p>Signing looks like this ...<o:p></o:p></p>
<p style="margin-bottom:12.0pt"> sbsign --key
$KEYPATH/$KEYNAME.key --cert $KEYPATH/$KEYNAME.crt --output
$SIGNEDFILE $UNSIGNEDFILE<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On keys and certs ...<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> boot.crt - Certificate to boot (to
be programmed in firmware)<br>
boot.key - Private key with which to sign shim<br>
shim.crt - Certificated embedded within shim used to
validate kernel, grub<br>
shim.key - Private key with which to sign kernel/grub<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">key generation ...<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><code><span style="font-size:10.0pt">
openssl req -new -x509 -newkey
</span></code><a href="#REDACTED" moz-do-not-send="true"><span style="font-size:10.0pt;font-family:"Courier
New"">rsa:2048</span></a><code><span style="font-size:10.0pt"> -keyout $KEY.key -out
$KEY.pem -days 3650</span></code> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><code><span style="font-size:10.0pt">
openssl x509 -in $KEY.pem -out $KEY.crt -outform DER</span></code><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Note: boot.crt should be copied to
cgcs-root/build-tools/certificates/TiBoot.crt for
inclusion during the 'build-iso' step<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Hope this helps<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Scott<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On 2022-07-05 03:19, Kumar, Chandan
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div style="border:solid #9C6500 1.0pt;padding:2.0pt 2.0pt
2.0pt 2.0pt">
<p class="MsoNormal" style="line-height:12.0pt;background:#FFEB9C"><span style="font-size:10.0pt;color:red">[Please note: This
e-mail is from an EXTERNAL e-mail address]</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Hi Greg,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks for acknowledgement.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I have raised starlingx launchpad
for document update. Meanwhile it would be really great
if you can share the steps which has to be done to
integrate signing of images as part of StarlingX build
infrastructure.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal">Chandan Kumar.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Waines, Greg <a href="mailto:Greg.Waines@windriver.com" moz-do-not-send="true">
<Greg.Waines@windriver.com></a> <br>
<b>Sent:</b> Monday, July 4, 2022 6:00 PM<br>
<b>To:</b> <a href="mailto:starlingx-discuss@lists.starlingx.io" moz-do-not-send="true" class="moz-txt-link-freetext">starlingx-discuss@lists.starlingx.io</a><br>
<b>Cc:</b> Little, Scott <a href="mailto:Scott.Little@windriver.com" moz-do-not-send="true"><Scott.Little@windriver.com></a><br>
<b>Subject:</b> Re: [Starlingx-discuss] Incorrect
public key for signed starlingX 5.0 iso .<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal">Hey Chandan,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks for bringing this up.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I chatted with Scott about this.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Currently the StarlingX public builds
on CENGN are not building a secure boot capable load …
i.e. signing the appropriate items to enable secure
boot. Although the StarlingX build infrastructure
allows it to be added.<o:p></o:p></p>
<p class="MsoNormal">Neither of these points are properly
documented in docs.starlingx.io
<span style="font-family:"Segoe UI
Emoji",sans-serif">☹</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I can’t remember the details of why
we are not doing this.<o:p></o:p></p>
<p class="MsoNormal">I am guessing that the thinking was
that a user of StarlingX that wanted to use UEFI Secure
Boot, would want to sign with his own private key.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Can you raise a starlingx launchpad (
<a href="https://urldefense.com/v3/__https:/secure-web.cisco.com/1mVLF-b4c-tBpQaEbNZbIeg5wuI2Sgdw11Kg2fRT9qRF2wo07vvRq040DIA0_Wsi3D4gtikjd41f-NbhgDr0WtPQQBHE441l65nwt6p00kAsBdGTNHMs0SRRp5xooNafH_Whk-Dm4t5akvM7v59ubFU1OqnyVm_DWXmTRsjlP7iavYNBqohwIkDwu5U_0bdpFU4p4YPP0Lf9wDBMltx2noOl9B-SkedaJ-aS-ZXVVTe6xH6VLXYIALMIH-dnrPQ7c4Gq8UZlj5vmUSNdnMlN2-alEns4KcCDiDF4IpogwjWO9-Bzcr272kWadoiBLaMmvU4L7OKnYa3EnFa8xAAyVJA/https*3A*2F*2Flaunchpad.net*2Fstarlingx__;JSUlJQ!!AjveYdw8EvQ!ftQxVQD6PBpbCLvLTR39Z8P_gDz5TUrBPEhzcs1gZuXNSAktfNGKZ7JpMi6FHbnT6g4f60qMmk2zKnypVD2dKYFaFWk0Ya8$" moz-do-not-send="true">
https://launchpad.net/starlingx</a> ) to address the <a href="https://urldefense.com/v3/__http:/docs.starlingx.io__;!!AjveYdw8EvQ!ftQxVQD6PBpbCLvLTR39Z8P_gDz5TUrBPEhzcs1gZuXNSAktfNGKZ7JpMi6FHbnT6g4f60qMmk2zKnypVD2dKYFa1r3VAOU$" moz-do-not-send="true">
docs.starlingx.io</a> documentation issue, i.e. to
indicate that the StarlingX CENGN builds are not signed
to support uefi secure boot, and describe how a
starlingx user could add signing to their StarlingX
build environment in order to sign for uefi secure boot
with their own private key ?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Greg.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Scott Little <<a href="mailto:scott.little@windriver.com" moz-do-not-send="true" class="moz-txt-link-freetext">scott.little@windriver.com</a>>
<br>
<b>Sent:</b> Wednesday, June 29, 2022 10:42 AM<br>
<b>To:</b> <a href="mailto:starlingx-discuss@lists.starlingx.io" moz-do-not-send="true" class="moz-txt-link-freetext">starlingx-discuss@lists.starlingx.io</a><br>
<b>Subject:</b> Re: [Starlingx-discuss] Incorrect
public key for signed starlingX 5.0 iso .<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<div>
<p class="MsoNormal">On 2022-06-02 13:12, Kumar, Chandan
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div style="border:solid #9C6500 1.0pt;padding:2.0pt
2.0pt 2.0pt 2.0pt">
<p class="MsoNormal" style="line-height:12.0pt;background:#FFEB9C"><span style="font-size:10.0pt;color:red">[Please note:
This e-mail is from an EXTERNAL e-mail address]</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Hi, <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I am trying to validate signed
starlingX 5.0 iso on a secureboot enabled setup
against public key(TiBoot.crt) embedded inside iso.
After rebooting , operating system is not coming up
with error screen saying
<span style="background:red;mso-highlight:red">“Verification
failed: (0X1A) Security Violation</span>”.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">However, when I signed images
with self-generated private key and validated
against corresponding public key, system is able to
boot up successfully. Signing is done after flashing
the iso on a server. Please find attached procedure
for signing images inside iso.<o:p></o:p></p>
<p class="MsoNormal">I believe, the public key
provided with iso is not correct. Can you please
confirm ?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal">Chandan Kumar. <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"> <o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Starlingx-discuss mailing list<o:p></o:p></pre>
<pre><a href="mailto:Starlingx-discuss@lists.starlingx.io" moz-do-not-send="true" class="moz-txt-link-freetext">Starlingx-discuss@lists.starlingx.io</a><o:p></o:p></pre>
<pre><a href="https://urldefense.com/v3/__https:/secure-web.cisco.com/1-KIhdgnDGw2i_w1bSfhcdQdJ0gtuSiGAoU-ggPInTuBelT92KbXPGwz89fztx-5CLsTQfshXKTc3aaqqJ-Mq4BnErMA5jCPj57X8BHou8RtYoI0fF-kIFVYYVX9qbmwnPrfape21hfY5wqnypwaoc7s_IL-RIFlZBKWMVC32JZy9GB4EI2XPFktp20B16JE2vxi4esR5XfNXcqUCBA5HqY3LGwMpw_r-Lz3Kxs5sFgxDJWsJNwol2lbAUfTEnyexbAghOCdz5cQrYRbu4HbMGraGchOZUlVwI22gkKpWT_z874pdrPIYAmShanAKy0bpA3IG3jgV79cAljguedbamQ/https*3A*2F*2Furldefense.com*2Fv3*2F__http*3A*2Flists.starlingx.io*2Fcgi-bin*2Fmailman*2Flistinfo*2Fstarlingx-discuss__*3B*21*21AjveYdw8EvQ*21e8leCxdSWn7CF5mepfpbV18UcLDSxfeu8JA2iW4ux5kQ7-Dya9uodepzEl_9Pj1QzoD5CDyT3LJdh6si3eZDcLl5VHlseg*24__;JSUlJSUlJSUlJSUlJSUlJQ!!AjveYdw8EvQ!ftQxVQD6PBpbCLvLTR39Z8P_gDz5TUrBPEhzcs1gZuXNSAktfNGKZ7JpMi6FHbnT6g4f60qMmk2zKnypVD2dKYFa3RUKtLs$" moz-do-not-send="true">http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss</a><o:p></o:p></pre>
</blockquote>
<p>Thanks for the report. I'll look into it<o:p></o:p></p>
<p>Scott Little<o:p></o:p></p>
<p> <o:p></o:p></p>
</div>
</blockquote>
<p><o:p> </o:p></p>
</div>
</div>
</blockquote>
</body>
</html>