Securing the Git push pipeline: Responding to a critical remote code execution
1–4 of 4 posts
Re: Securing the Git push pipeline: Responding to a critical remote code execution
#2I mean, sure.
But what about allowing user inputs in trusted fields,
Or allowing switching environments per request, on inputs from users
Or allowing requests in a user context to access storage from another
Or storing everything in plaintext on a node that everything can access
Or not validating user inputs
Or...
Its not a success story.
Re: Securing the Git push pipeline: Responding to a critical remote code execution
#3Nothing on auditing other fields? Nothing on how it escaped test coverage? No fuzzing?
Re: Securing the Git push pipeline: Responding to a critical remote code execution
#4[deleted]