5 ms·

> cURL has been used extensively for bad purposes What?! Sources please.

• nickserv 9y ago
  I once used it to change the user-agent and get an alternative response from an API.
  • funnyfacts365 9y ago
    badass...
• m-j-fox 9y ago
  I mean, I've personally used it to access APIs from shell scripts that would have been far more maintainable in a proper Python script.
  • nthcolumn 9y ago
    You monster!
  • contingencies 9y ago
    That's three counts of conspiracy to degrade system maintainability, manufacturing tooling with intent to degrade system maintainability, possession of tooling to degrade system maintainability, one count of international travel with intent to degrade system maintainability, two counts of manufacture of false documents[0][1] in support of a conspiracy. Bail denied. And... that's life. [0] Exhibit A: man curl [1] CURL website
• joncrocks 9y ago
  I presume the author of the comment is refferring to incidents such as https://daniel.haxx.se/blog/2010/12/23/hacking-me/ https://daniel.haxx.se/blog/2010/12/23/hacking-me/ If you write a general-purpose utility and it gets included in some kind of bad software, the people writing the 'bad' parts aren't likely to include their details, but if your 'good' code has your details....
• rev 9y ago
  "I once saw him kill three men in a bar with a pencil, with... a... f#@king... pencil." © John Wick
• qume 9y ago
  If an attackers rouge process lands itself on a target, using something trusted like cURL is better than opening a socket directly, no? Less likely to attract attention? Same goes for wget, links, etc. Sorry no sources, it won't take you long to verify this yourself using google. I'm sure there are competent infosec guys and gals here who can provide a better explanation.
  • funnyfacts365 9y ago
    rogue, not rouge.
• buremba 9y ago
  curl -i -X POST http://SOME_TERRIBLE_WEBSITE/api/people/SSN/kill http://SOME_TERRIBLE_WEBSITE/api/people/SSN/kill