<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Hi,</div><div class=""><br class=""></div>By the way, I recently discovered the tool “clone-master-clean-up”: <div class=""><br class=""><div class=""><div class=""></div><blockquote type="cite" class=""><div class=""># zypper info clone-master-clean-up</div><div class="">Loading repository data...</div><div class="">Reading installed packages...</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Information for package clone-master-clean-up:</div><div class="">----------------------------------------------</div><div class="">Repository : SLE-Module-Server-Applications15-Pool</div><div class="">Name : clone-master-clean-up</div><div class="">Version : 1.2-2.6</div><div class="">Arch : noarch</div><div class="">Vendor : SUSE LLC <<a href="https://www.suse.com/" class="">https://www.suse.com/</a>></div><div class="">Support Level : Level 3</div><div class="">Installed Size : 12.4 KiB</div><div class="">Installed : No</div><div class="">Status : not installed</div><div class="">Source package : clone-master-clean-up-1.2-2.6.src</div><div class="">Summary : Clean up a system for cloning preparation</div><div class="">Description :</div><div class=""> Clean up a system for cloning preparation by cleaning up usage history and log files, etc.</div></blockquote><div class=""><br class=""></div><div class="">And you can also find a bit of documentation at: </div><div class=""><a href="https://susedoc.github.io/doc-sle/develop/SLES-deployment/single-html/#sec.deployment.clone_image.clean" class="">https://susedoc.github.io/doc-sle/develop/SLES-deployment/single-html/#sec.deployment.clone_image.clean</a></div><div class=""><br class=""></div><div class="">Please give this tool a try,</div><div class=""><br class=""></div><div class="">Regards,<br class=""><div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;">--<br class="">Vincent Moutoussamy<br class="">SUSE Beta Program and SDK Project Manager</div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 13 Mar 2018, at 07:28, Thorsten Kukuk <<a href="mailto:kukuk@suse.de" class="">kukuk@suse.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Tue, Mar 13, Waite, Dick (External) wrote:<br class=""><br class=""><blockquote type="cite" class="">Last word and then I shut up...<br class=""><br class="">You can not update / write to a database / registry without any check that the caller is entitled to update / write that field. Even a Hostname check would be better that nothing. The --cleanup option will be forgotten at some time by someone and then that lowly clone is going to update the SCC of a valuable Mother or maybe even a queen.<br class=""></blockquote><br class="">Again: the hostname is completly useless for this case in most environments. <br class="">Else: all other data used for registration got cloned by you and <br class="">is identical on both machines. So any check we can do would tell<br class="">us: this is the same machine as registered against SCC.<br class=""><br class="">If you clone a machine, you have to remove all host specific data.<br class="">And this is not only the SCC registration stuff, this are also<br class="">machine-id, dbus ID, ssh host key, maschine specific certificates, ...<br class="">If you don't do that, bad thinks can happen, not only with registration.<br class=""><br class=""> Thorsten<br class=""><br class="">-- <br class="">Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP<br class="">SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany<br class="">GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)<br class="">_______________________________________________<br class="">sle-beta mailing list<br class=""><a href="mailto:sle-beta@lists.suse.com" class="">sle-beta@lists.suse.com</a><br class="">http://lists.suse.com/mailman/listinfo/sle-beta<br class=""></div></div></blockquote></div><br class=""></div></div></div></body></html>