Closed
Bug 1299148
Opened 8 years ago
Closed 7 years ago
Stop using the AWS KeyPair provided by EC2
Categories
(Taskcluster :: Workers, defect)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhford, Unassigned)
Details
We use KeyPair for metadata. We need to stop reading the value that AWS stores in here in the SSH authentication for the root account. This should be changing from:
AuthorizedKeysFile .ssh/authorized_keys
to something like:
AuthorizedKeysFile .ssh/authorized_keys_real
then set the allowed public key files in the packer configs, or however we build AMIs.
This means that the SSH Public Key provided by EC2 is just ignored by SSHD. This is because bug 1290922 is not going to happen.
Reporter | ||
Comment 1•8 years ago
|
||
(In reply to John Ford [:jhford] CET/CEST Berlin Time from comment #0)
oh, this change should be made in /etc/ssh/sshd_config
Comment 2•7 years ago
|
||
This is not an issue any longer when the new deploy is done, right?
Flags: needinfo?(jhford)
Reporter | ||
Comment 3•7 years ago
|
||
we can close this. Key management is now a responsibility of the maintainer of a worker type.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jhford)
Resolution: --- → FIXED
Assignee | ||
Updated•6 years ago
|
Component: Docker-Worker → Workers
You need to log in
before you can comment on or make changes to this bug.
Description
•