True, I guess I was expecting if you were reimplementing these with additional protections, why not add the protection using the custom pointer reimplementations to ensure no use after frees. Seems like a missed opportunity.
Does the StringView/Span implementation here seem lacking? If the underlying data goes away, wouldn't the pointer now point to an invalid freed location, because it doesn't track the underlying data in any way?
Just submit a PR that removes the action so it doesn't run on the branch before the merge! If devs aren't reviewing the code anyways, will they even catch that kind of change?
Maybe it's just me, but I'd rather teach how to use a knife safely? And a cut from a blade is a lesson to be learned, hopefully only once.
Edit: Oh and if anyone's looking for the tool name, it's called a nibbler. This one is just table-mounted, there are power tool and unpowered versions ofc.
Right, Windows Hello requires it for facial auth, Windows itself does not. Hello still works, just you have to authenticate with a different method if the hardware isn't present.
Not only can you yourself manually check out a specific repo, but if you have submodules and do a recursive checkout, it's also possible to pull in other security nightmares from places you never expected now. That would be one complicated attack to pull off though, chain of compromised workflows haha