Yeah its a crap design decision/issue/bug/feature from MikroTik. I would REALLY REALLY REALLY REALLY like for all user accounts including MD5/SHA hashes of passwords to be included in /export
It’s way too easy to replace a faulty router, load the backup config and ‘forget’ to change the user details, potentially exposing a router with admin/blank
It’s also impossible to audit passwords. If user accounts AND hashes were included then known hashes for old/insecure passwords (i.e. core staff leaving and certain routers needing local passwords changed) could be automatically checked and a notification raised if it wasn’t changed
I can go ahead and put a mass password change, but I can’t audit it and actually verify it happened
I really hope this is ‘fixed’ and hashes get included with config at some point
Other things that aren’t included (such as certificate files) I feel probably shouldn’t be included in a config, but again a hash would be nice so that if restoring a config, it can be verified after applying to see what was missed. The certificate itself doesn’t need to be in the config, but if it was a hash (calculated every time /export is run) it would verify if said certificate actually exists on the device
Let’s stick to the point where we agree it is “Work In Progress”
Also noticed on ROS7 some things do become available when using show-sensitive (where they should be shown regardless) but other things never show.
And yes, users is one of them.