This new version of ec2-instance-connect is significantly better, thanks for all the work.
I was wrong about the dedicated user: using the ec2-instance-connect user is definitely an improvement. My one specific concern: - AWS_SECRET_ACCESS_KEY (and the ability to get one) appears to be available to all processes on the system. What does possession of this secret key mean? The hypervisor may not care, a guest is a guest is a guest, but users may care deeply. Do they? And two generic concerns: - Shell error handling is difficult. This code looks much safer than before but the language is not helpful here. - SSH access credentials are almost invisible: ps auxw | grep ssh will show the flow, as will an inspection of /lib/systemd/system/ssh.service.d/ec2-instance-connect.conf , but these are fairly subtle. These last two issues are more business decisions than security purview. Rewriting a tool isn't cheap and the work on this version was extensive. And all this effort must surely be because users have wanted an out-of- band authentication mechanism. Sufficiently advertising the new feature would allay my concern that it's very subtle. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835114 Title: [MIR] ec2-instance-connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1835114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
