v4.7.2

Security

• Check the host header to mitigate a DNS rebinding attack #578

v5.4.3

Fixed

• Fixed 404 page not found when credentials from metadata service in --server mode #577. If you're experiencing issues, kill any old background proxy process using sudo killall -9 aws-vault before running aws-vault exec --server
• Removed the experimental hidden --ecs-server flag (this feature will be in v6)

v5.4.2

Fixed

• Reverted the change introduced in v5.4.0 where the exec command defaulted to a login shell if SHELL is known to support -l as this is causing issues with nested environment variables #546

v5.4.1

Fixed

• region env var being set to blank
• error handling on ecs credential server

v5.4.0

Fixed

• AWS_FEDERATION_TOKEN_TTL was not correctly setting the Federation TTL #550 #551
• AWS region retrieval from metadata server #542

Added

• --region to the exec and login commands #557 #531
• Currently hidden, an experimental exec --ecs-server flag starts a ECS credential server offering many advantages over the ec2 metadata server #556 #375 (reverted in v5.4.3)

Changed

• The exec command now defaults to a login shell if SHELL is known to support -l 38262fd #546 (reverted in v5.4.2)

v5.3.2

Fixed

• Fix test for recursive source_profile #527 0760274

v5.3.1

Fixed

• failures when AWS_SDK_LOAD_CONFIG and AWS_PROFILE were both set #410 1ce3655

v5.3.0

Fixed

• Ignore a profile's source_profile if it refers to itself f26b718 #504

Added

• Support for kdialog #523

v5.2.1

Fixed

• Fix autocompletion of profile names #506 e05eb98
• Fix linux secret-service keyring unlock #513 #521

v5.2.0

Fixed

• Fix use of GetSessionToken when a single profile is used for the the credentials and role #501

Added

• Add --no-session to login #500
• Add SHA256SUMS file to releases #503

Changed

• Don't use chained GetSessionToken if a role's duration is over 1 hour. AWS doesn't allow it and is the main use-case for --no-session b5c0224