Re:Rubygems.org AWS Root Access Event – September 2025
by TehCorwiz on Thursday October 09, 2025 @03:58PM
(#45532327)
Right?! Did nobody there think to actually disable the accounts? These are the people who are harping about "security" being the reason for the ham-fisted takeover of the source repos, but they didn't secure the production infrastructure?
Re:Rubygems.org AWS Root Access Event – September 2025
by colonwqbang on Thursday October 09, 2025 @05:00PM
(#45533034)
It didn't occur to them that he might have written the password down? That's wild.
Re:Rubygems.org AWS Root Access Event – September 2025
by TehCorwiz on Thursday October 09, 2025 @07:25PM
(#45534072)
Either profoundly naive, tech illiterate, or it's a bad faith argument.
Re:Rubygems.org AWS Root Access Event – September 2025
by baobun on Friday October 10, 2025 @03:31AM
(#45536235)
Or more realistically, accessed the accounts via IAM token and/or service account.
Something they also failed to consider, reading between the lines.
Re:Rubygems.org AWS Root Access Event – September 2025
by jeffwask on Friday October 10, 2025 @10:36AM
(#45539599)
No matter how you slice it this is miserable root password security. Why do maintainers need root access? No one in my org has root access but me and all those creds are tied to hardware MFA locked in my MDF.
> 1. While Ruby Central correctly removed access to shared credentials through its enterprise password manager prior to the incident, our staff did not consider the possibility that this credential may have been copied or exfiltrated to other password managers outside of Ruby Central’s visibility or control.
> 2. Ruby Central failed to rotate the AWS root account credentials (password and MFA) after the departure of personnel with access to the shared vault.