** Description changed: + [IMPACT] Ubuntu Snappy 15.04 disables SSH unless a user provides + explicit user-data to turn SSH on. This happens regardless of a user + providing authentication tokens. This prevents Ubuntu Snappy from being + added to various Cloud WebUI's, Marketplaces and confuses many users. + + [FIX] Enable SSH when a user or the fabric provides authentication + tokens unless the user explicitly disables SSH via user-data. + + [REGRESSION POTENTIAL] Low. This change only affects Ubuntu Snappy and + is scoped to Snappy instances only. + + [TEST]: + 1. Build Ubuntu Snappy 15.04-edge w/ cloud-init from proposed + 2. Boot instance w/ out user-data on EC2, confirm user can SSH in + 3. Boot instance w/ user-data below, confirm SSH is disabled + #cloud-config: + snappy: + ssh_enabled: False + 4. Boot instance w/ user-data below, confirm SSH is enabled + #cluod-config: + snappy: + ssh_enabled: True + + [ORIGINAL REPORT] + For Snappy, SSH is turned off by default. Cloud-init should default to SSH being off by default, BUT if the datasource provides credentials, then SSH should be turned on.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1494816 Title: Snappy should enable SSH when credentials are provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1494816/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
