3 ms·
> why not just say the attack can be executed directly from the command line? Any techincally literate audience will understand that implies cURL (or any other
by thaumasiotes 5y ago
> why not just say the attack can be executed directly from the command line? Any techincally literate audience will understand that implies cURL (or any other tool!) and an non-technical audience will understand its simplicity, if that is in fact the case.
I mean, the normal way to use curl for this kind of thing is to define the request you want to send in a file and tell curl to read the file. There's no requirement -- or implication -- of simplicity in an attack that "you can execute from the command line"; that description refers to every possible attack. It's meaningless. There's nothing you can do that you can't do from the command line.
- nkrisc 5y agoYes, so why mention cURL at all?
- thaumasiotes 5y agoI'm not saying there's a reason to mention curl. I'm saying the explanation given makes no sense.