non-registered Account.username gets regenerated each time the account is disabled/re-enabled
Hi,
I've stumbled on this strange behavior playing with the Guix System Jami service, which interacts with jamid
via its D-Bus interface:
# herd list-accounts jami
The following Jami accounts are available:
- cbdf1e811005a9da53d73d0eaaa6a1c5f9b23321 ()
# herd disable-account jami cbdf1e811005a9da53d73d0eaaa6a1c5f9b23321
# herd list-accounts jami
The following Jami accounts are available:
- cbdf1e811005a9da53d73d0eaaa6a1c5f9b23321 () [disabled]
herd enable-account jami cbdf1e811005a9da53d73d0eaaa6a1c5f9b23321
# let some time pass
# herd list-accounts jami
The following Jami accounts are available:
- f3cb93f1aac048e8284d271ae5a2950dc60318af ()
We can see that the above account username changed (the ID corresponds to the Account.username
entry). I can't think of a reason why this should be; it is unintuitive and complicate things. In my opinion, the Account.username should not change.
Edited by Maxim Cournoyer