| pronouns | he/him |
| website | https://www.roguelazer.com |
| OpenPGP | 24F8AA354990F3F562EC014BC6496DEB3DA8E9B5 |
| pronouns | he/him |
| website | https://www.roguelazer.com |
| OpenPGP | 24F8AA354990F3F562EC014BC6496DEB3DA8E9B5 |
During the fall of 2022, a few friends and I took a road trip from Chicago, IL to Washington, DC to attend a cybersecurity conference and (try) to take a break from our usual computer work. While we were visiting the University of Maryland, we came across a fleet of electric scooters scattered across the
CircleCi is reporting a “security incident,” but the wording used and and actions advised suggests it’s probably a full blown breach:
https://circleci.com/blog/january-4-2023-security-alert/
“At this point, we are confident that there are no unauthorized actors active in our system.”
actions advised:
“Immediately rotate any and all secrets stored in CircleCI. These may be stored in project environment variables or in contexts.
We also recommend customers review internal logs for their systems for any unauthorized access starting from December 21, 2022 through today, January 4, 2023, or upon completion of your secrets rotation.”
Holy crap! This is one of the biggest footguns in the #ruby development ecosystems, and they've finally fixed it!
https://github.com/rubygems/rubygems/pull/5888
You don't know how many people I've had to support who have trashed their machines by accidentally running `bundle install` and having it automatically sudo and overwrite a bunch of system packages and leave ruby totally unusable.
What was the end-user or developer problem that led to this PR? I think it's time to move on and there's consensus between everyone that this is a harmful feature. In any case, I propose to release...