~mokeseven7/cloud-init:ubuntu/focal

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

fc6ac02... by James Falcon on 2021-03-22

releasing cloud-init version 21.1-19-gbad84ad4-0ubuntu1~20.04.1

adfbd0d... by James Falcon on 2021-03-22

debian/cloud-init.templates: Add UpCloud datasource

7e13b71... by James Falcon on 2021-03-19

debian/cloud-init.postinst: Change output log permissions on upgrade

In b794d426 (#847), we changed log permissions on
/var/log/cloud-init.log to be owned by root:adm and have 740 permissions
by default. This commit performs that same change on upgrade.

LP: #1918303

02475f0... by Dan Watkins on 2021-01-04

d/cloud-init.manpages: include upstream manpages in package.

cc5ad98... by James Falcon on 2021-03-22

update changelog (New upstream snapshot 21.1-19-gbad84ad4).

9342914... by James Falcon on 2021-03-22

merge from upstream/master at 21.1-19-gbad84ad4

4def71c... by James Falcon on 2021-03-22

update changelog.

e9daef9... by James Falcon on 2021-03-22

drop cherry picks included in upstream/master commit bad84ad4

drop the following cherry picks:
  cpick-4f62ae8d-Fix-regression-with-handling-of-IMDS-ssh-keys-760

bad84ad... by Dan Watkins on 2021-03-19

.travis.yml: generate an SSH key before running tests (#848)

b794d42... by Dan Watkins on 2021-03-19

write passwords only to serial console, lock down cloud-init-output.log (#847)

Prior to this commit, when a user specified configuration which would
generate random passwords for users, cloud-init would cause those
passwords to be written to the serial console by emitting them on
stderr. In the default configuration, any stdout or stderr emitted by
cloud-init is also written to `/var/log/cloud-init-output.log`. This
file is world-readable, meaning that those randomly-generated passwords
were available to be read by any user with access to the system. This
presents an obvious security issue.

This commit responds to this issue in two ways:

* We address the direct issue by moving from writing the passwords to
  sys.stderr to writing them directly to /dev/console (via
  util.multi_log); this means that the passwords will never end up in
  cloud-init-output.log
* To avoid future issues like this, we also modify the logging code so
  that any files created in a log sink subprocess will only be
  owner/group readable and, if it exists, will be owned by the adm
  group. This results in `/var/log/cloud-init-output.log` no longer
  being world-readable, meaning that if there are other parts of the
  codebase that are emitting sensitive data intended for the serial
  console, that data is no longer available to all users of the system.

LP: #1918303