I think it is much more a policy of not being root to avoid issues of
generally doing things as root than it is to prevent an attacker from
reaching the system. By default, the images have no ssh password login,
and the attacker would only see this message if they had access to the
correct private keys.
If you want to change the behavior, it can be done via cloud-config. Simply
add the following cloud config syntax:
#cloud-config
disable_root: False
** Changed in: ubuntu-on-ec2
Importance: Undecided => Wishlist
** Changed in: ubuntu-on-ec2
Status: New => Won't Fix
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Won't Fix
** Changed in: ubuntu-on-ec2
Status: Won't Fix => Invalid
--
Root logins are crippled
https://bugs.launchpad.net/bugs/608958
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
