SUSE Manager Register Cloned VM

On the cloned machine, change the hostname and IP addresses. Make sure /etc/hosts contains the changes you made and the correct host entries.

For distributions that support systemd: If your machines have the same machine ID, delete the file on each duplicated client and re-create it:

# rm /etc/machine-id
rm /var/lib/dbus/machine-id
dbus-uuidgen --ensure
systemd-machine-id-setup
For distributions that do not support systemd: Generate a machine ID from dbus:

---

You don't really need to do these unless errors:

rm /var/lib/dbus/machine-id
dbus-uuidgen --ensure
If your clients still have the same Salt client ID, delete the minion_id file on each client (FQDN will be used when it is regenerated on client restart):

rm /etc/salt/minion_id
Delete accepted keys from the onboarding page and the system profile from SUSE Manager, and restart the client with:

service salt-minion restart
Re-register the clients. Each client will now have a different /etc/machine-id and should be correctly displayed on the System Overview page.

Social-Engineering via LinkedIN

Well, it finally happened to me on LinkedIN: Friendly chat from an old acquaintance reaching out. Only, it was in broken English (unusual for the connection), on a subject unrelated to our careers or established friendship, and finally - a pasted URL LinkedIN had marked as suspect. I reached out to him on another messaging app to verify the conversation; it wasn't him.

My earliest memories of security consciousness surrounded being stationed in Cold War Germany - many of which are still applicable this day and age - and given the employers and roles we readily share here (as opposed to other social sites) we open ourselves up for a more targeted social-engineering attack. So remember your annual security training, and stay vigilant!