This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
Validated yakkety and zesty---
cat config.yml
#cloud-config
ssh_pwauth: true
for release in yakkety zesty; do ref=$release-proposed; lxc init $ref $name;
lxc file pull $name/etc/ssh/sshd_config .; ls -l sshd_config; chmod 600
sshd_config; lxc file push sshd_config $name/etc/ssh/sshd_config;
Verified xenial keeps sshd_config perms:
$ name=test-proposed
$ release=xenial
$ ref=$release-proposed
$ ./lxc-proposed-snapshot --proposed --publish $release $ref
$ lxc init $ref $name
$ lxc init $ref $name
Creating test-proposed
$ lxc file pull $name/etc/ssh/sshd_config .
$ ls -ltr sshd_config
Hello GUO, or anyone else affected,
Accepted cloud-init into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-113-g513e99e0-0ubuntu1~17.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing this
Hello GUO, or anyone else affected,
Accepted cloud-init into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-113-g513e99e0-0ubuntu1~16.10.1 in a few hours, and then in
the -proposed repository.
Please help us by testing this
Hello GUO, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-113-g513e99e0-0ubuntu1~16.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing this
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init
** Description changed:
- In my deploy image, the default permission of sshd_config file is 600.
- It always be changed to 644 after cloud-init run. After debug, it is
- caused by cloud-config item:
+ === Begin SRU Template ===
+ [Impact]
+ Existing security permissions on /etc/ssh/sshd_config
Fixed in 721348a622a660b65acfdf7fdf53203b47f80748
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: New => Fix Committed
** Changed in: cloud-init
Assignee: (unassigned) => Lars Kellogg-Stedman (larsks)
** Also affects: cloud-init
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644064
Title:
sshd_config file permission changed to 644 if
13 matches
Mail list logo
