[Bug 1860142] Re: Please update ec2-instance-connect to 1.1.12 release

Wed Jan 29 18:32:55 UTC 2020

Verified 1.1.12+dfsg1-0ubuntu1~16.04.0 on Xenial:

ubuntu at ip-172-31-23-71:~$ sudo apt install ec2-instance-connect 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  ec2-instance-connect
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 11.4 kB of archives.
After this operation, 48.1 kB of additional disk space will be used.
Get:1 http://us-east-2.ec2.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 ec2-instance-connect all 1.1.9-0ubuntu3~16.04.1 [11.4 kB]
Fetched 11.4 kB in 0s (106 kB/s)          
Selecting previously unselected package ec2-instance-connect.
(Reading database ... 76553 files and directories currently installed.)
Preparing to unpack .../ec2-instance-connect_1.1.9-0ubuntu3~16.04.1_all.deb ...
Created system user ec2-instance-connect
Unpacking ec2-instance-connect (1.1.9-0ubuntu3~16.04.1) ...
Setting up ec2-instance-connect (1.1.9-0ubuntu3~16.04.1) ...
sshd override added, restarting daemon
ubuntu at ip-172-31-23-71:~$ sudo sed -i s/backports/proposed/ /etc/apt/sources.list
ubuntu at ip-172-31-23-71:~$ sudo apt update -qq
24 packages can be upgraded. Run 'apt list --upgradable' to see them.
ubuntu at ip-172-31-23-71:~$ sudo apt install -q ec2-instance-connect 
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
  ec2-instance-connect
1 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
Need to get 12.7 kB of archives.
After this operation, 7,168 B of additional disk space will be used.
Get:1 http://us-east-2.ec2.archive.ubuntu.com/ubuntu xenial-proposed/universe amd64 ec2-instance-connect all 1.1.12+dfsg1-0ubuntu1~16.04.0 [12.7 kB]
Fetched 12.7 kB in 0s (247 kB/s)
(Reading database ... 76562 files and directories currently installed.)
Preparing to unpack .../ec2-instance-connect_1.1.12+dfsg1-0ubuntu1~16.04.0_all.deb ...
Unpacking ec2-instance-connect (1.1.12+dfsg1-0ubuntu1~16.04.0) over (1.1.9-0ubuntu3~16.04.1) ...
Setting up ec2-instance-connect (1.1.12+dfsg1-0ubuntu1~16.04.0) ...
ubuntu at ip-172-31-23-71:~$ sudo apt purge ec2-instance-connect
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  ec2-instance-connect*
0 upgraded, 0 newly installed, 1 to remove and 23 not upgraded.
After this operation, 55.3 kB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 76562 files and directories currently installed.)
Removing ec2-instance-connect (1.1.12+dfsg1-0ubuntu1~16.04.0) ...
sshd override removed, restarting daemon...
Deleted system user ec2-instance-connect
Purging configuration files for ec2-instance-connect (1.1.12+dfsg1-0ubuntu1~16.04.0) ...
Deleted system user ec2-instance-connect
(failed reverse-i-search)`apit in': sudo ^Ct purge ec2-instance-connect
ubuntu at ip-172-31-23-71:~$ sudo apt install -q ec2-instance-connect 
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  ec2-instance-connect
0 upgraded, 1 newly installed, 0 to remove and 23 not upgraded.
Need to get 12.7 kB of archives.
After this operation, 55.3 kB of additional disk space will be used.
Get:1 http://us-east-2.ec2.archive.ubuntu.com/ubuntu xenial-proposed/universe amd64 ec2-instance-connect all 1.1.12+dfsg1-0ubuntu1~16.04.0 [12.7 kB]
Fetched 12.7 kB in 0s (0 B/s)
Selecting previously unselected package ec2-instance-connect.
(Reading database ... 76553 files and directories currently installed.)
Preparing to unpack .../ec2-instance-connect_1.1.12+dfsg1-0ubuntu1~16.04.0_all.deb ...
Created system user ec2-instance-connect
Unpacking ec2-instance-connect (1.1.12+dfsg1-0ubuntu1~16.04.0) ...
Setting up ec2-instance-connect (1.1.12+dfsg1-0ubuntu1~16.04.0) ...
sshd override added, restarting daemon
ubuntu at ip-172-31-23-71:~$ 

I used the following aws cli command to switch to IMDSv2:

root at aws-cli-br-cc:~# aws ec2 modify-instance-metadata-options --instance-id i-021a1d1da29c13d4a --http-tokens required --http-endpoint enabled
{
    "InstanceId": "i-021a1d1da29c13d4a",
    "InstanceMetadataOptions": {
        "State": "pending",
        "HttpTokens": "required",
        "HttpPutResponseHopLimit": 1,
        "HttpEndpoint": "enabled"
    }
}

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ec2-instance-connect in Ubuntu.
https://bugs.launchpad.net/bugs/1860142

Title:
  Please update ec2-instance-connect to 1.1.12 release

Status in ec2-instance-connect package in Ubuntu:
  Fix Released
Status in ec2-instance-connect source package in Xenial:
  Fix Committed
Status in ec2-instance-connect source package in Bionic:
  Fix Committed
Status in ec2-instance-connect source package in Disco:
  Won't Fix
Status in ec2-instance-connect source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  New upstream release of the package providing SSH access to instances;
  available to any AWS users. The most notable new feature is supporting
  Instance Metadata Service Version 2, but since the release included
  major rewrite which honored on Security Team's input the package is
  backported in full.

  [Test Cases]
  This is manually tested by Amazon:

  0) Deploy an Amazon AWS instance with Instance Connect feature enabled
  1) Install the previous version of the ec2-instance-connect package
  2) Verify that the sshd process has been restarted with the changed command-line, now including "AuthorizedKeysCommand*" options.
  3) Attempt to connect to the instance using a SSH key that is known by the Instance Connect service.
  4) Upgrade to the new version of the package
  5) Attempt to connect to the instance using a SSH key that is known by the Instance Connect service.
  6) Purge the ec2-instance-connect package
  7) Configure the instance to use IMDSv2
  8) Install the new ec2-instance-connect again and verify that is working again (steps 2 and 3)

  [Regression Potential]
  Limited to SSH access on instances where the package gets installed. This package will be installed by default for a new service called "Instance Connect" provided to AWS customers. In the case of an issue, things to watch out for would be for some keys to not be usable to connect to the instance when they are expected to be, as the list of authorized keys is collated by the service to include both the usual authorized_keys contents, as well as keys provided by the Instance Connect service.

  The package upgrade is covered in the test case.

  [Other Info]
  The source difference for the SRUs contain a lot of extra files because the source now contains almost the full upstream tarball, but the difference between the binary packages is still minimal and it maybe easier to reviewing that difference.

  Disco SRU is skipped because it goes EOL before the aging of the
  package would finish.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1860142/+subscriptions