yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1707037@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package cloud-init -
17.2-20-g32a6a176-0ubuntu1

---------------
cloud-init (17.2-20-g32a6a176-0ubuntu1) bionic; urgency=medium

  * New upstream snapshot.
    - tests: Fix EC2 Platform to return console output as bytes.
    - tests: Fix attempted use of /run in a test case.
    - GCE: Improvements and changes to ssh key behavior for default user.
      [Max Illfelder] (LP: #1670456, #1707033, #1707037, #1707039)
    - subp: make ProcessExecutionError have expected types in stderr, stdout.
    - tests: when querying ntp server, do not do dns resolution.
    - Recognize uppercase vfat disk labels [James Penick] (LP: #1598783)
    - tests: remove zesty as supported OS to test

 -- Chad Smith <chad.smith@xxxxxxxxxxxxx>  Tue, 23 Jan 2018 20:10:44
-0700

** Changed in: cloud-init (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1707037

Title:
  GCE data source should only add "ubuntu" keys to the ubuntu user

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  GCE supports specifying SSH keys for an instance as a tuple of
  (username, key).  Currently, cloud-init will add all keys to the
  default (ubuntu) user, regardless of the user specified in metadata.

  This is problematic because there may be users in the metadata who are
  not intended to have sudo access but could gain sudo privileges via
  the ubuntu user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1707037/+subscriptions