diff options
| author | Graham Christensen <graham@grahamc.com> | 2020-11-18 11:56:15 -0500 |
|---|---|---|
| committer | Graham Christensen <graham@grahamc.com> | 2020-11-19 13:00:56 -0500 |
| commit | 83ea88e03fe2775601636c5f578b63276910a538 (patch) | |
| tree | 9e094e34f05b8169790b4e67542cad4683af7a50 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 21339b41bf60847b0b8880b8ca5ceb2867044bf1 (diff) | |
nixos: ec2 ami: support IMDSv2
AWS's metadata service has two versions. Version 1 allowed plain HTTP
requests to get metadata. However, this was frequently abused when a
user could trick an AWS-hosted server in to proxying requests to the
metadata service. Since the metadata service is frequently used to
generate AWS access keys, this is pretty gnarly. Version two is
identical except it requires the caller to request a token and provide
it on each request.
Today, starting a NixOS AMI in EC2 where the metadata service is
configured to only allow v2 requests fails: the user's SSH key is not
placed, and configuration provided by the user-data is not applied.
The server is useless. This patch addresses that.
Note the dependency on curl is not a joyful one, and it expand the
initrd by 30M. However, see the added comment for more information
about why this is needed. Note the idea of using `echo` and `nc` are
laughable. Don't do that.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions