Support disable_root-esque behaviour for other users

Bug #1771198 reported by Dan Watkins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
Wishlist
Dan Watkins
cloud-init (Ubuntu)
Fix Released
Undecided
Chad Smith
Xenial
Triaged
Undecided
Unassigned
Bionic
Triaged
Undecided
Unassigned
Cosmic
Fix Released
Undecided
Chad Smith

Bug Description

When building Ubuntu cloud images, we prefer to name the default user "ubuntu" where possible, to maintain a consistent user experience between substrates. Some clouds, however, like to have a consistent user name across all of their various image offerings. This is an inherent conflict. One way in which we have agreed to resolve this is to use the messaging that the disable_root behaviour currently provides on the cloud-specific user, to point to the ubuntu user. This means, at least, that users are given some direction (rather than being left wondering if their instance has provisioned correctly, or if their SSH keys are invalid, or &c.)

I propose a new cloud.cfg key named "ssh_disable_users" which defines a list of users. For each of these users, cloud-init will ensure they exist, and configure the system so that users SSH'ing to that user will be redirected to the default user (a la disable_root behaviour currently).

(`disable_root: True` would translate as `ssh_disable_users: ["root"]`.)

Related branches

Revision history for this message
Scott Moser (smoser) wrote :

that seems like a sane plan.

Changed in cloud-init:
status: New → Triaged
importance: Undecided → Wishlist
Dan Watkins (oddbloke)
Changed in cloud-init:
assignee: nobody → Dan Watkins (daniel-thewatkins)
tags: added: id-5ad63efb9e110201665a1dac
Chad Smith (chad.smith)
Changed in cloud-init:
status: Triaged → Fix Released
Changed in cloud-init (Ubuntu Cosmic):
status: New → Fix Released
assignee: nobody → Chad Smith (chad.smith)
Changed in cloud-init (Ubuntu Bionic):
status: New → Triaged
Changed in cloud-init (Ubuntu Xenial):
status: New → Triaged
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.