We're updating our SSH keys provisioning code in D1187.
In the process, when I tested this state on Eglide in dry-run mode, I noticed some keys diverge between config and server.
I'll reach each user to confirm the keys and update the config accordingly.
DevCentral username | Username | Action to take | Date confirmed |
@eunutmaz | erol | Nothing — the second server key is the correct one | 2017-11-10 08:49 |
— | khmerboy | Probably nothing — key committed seems the right one, the previous not removed | 2017-11-12 13:01 |
@dereckson | dereckson | Nothing — Keys updated in 6d1bf74 but not applied to Eglide | 2017-11-11 23:41 |
@tomjerr | tomjerr | Nothing — Key updated in 90d97e1, former ones not removed but we can clean them | 2017-10-26 15:38 |
— | kazuya | Nothing — Key updated in 9d5cbec5d, former one not removed | |
@FRWPKumkum | kumkum | Nothing — Key updated in c850066a, former one not removed | |
The extra keys situation is explained by the fact the full file wasn't managed. Only new keys were added by ssh_keys.present.
With D1187, we'll get a fully managed file, with the header committed this time (ssh_keys.present ignored the # lines when updating the file), and former keys well removed.