Search

Items tagged with: curl


#curl


only 3 severity high vulnerabilities in #curl during the last 5 years

(slide from my curl security talk I did over the weekend)

#curl


#curl


Did you notice how speed in #CURL changed for HTTP/2 in the last releases?

Thanks Stefan for your work!

#curl




Two laptops, webcam on stand, mike, mike-stand, power for laptops, cable kit, repair kit, 12 curl mugs, eight packs with different curl stickers, carton coasters, pcb coasters, t-shirts, name tags + pens, two UCB-C to HDMI adapters

Preparing for #curl up 2024.

github.com/curl/curl-up/wiki/2…

#curl


My "predicting the future" slide, used in several presentations over the last few years. It involves #curl.

"everything will be networked"

#curl


#curl


How many authors have their contributions in #curl product source code? How many have had their previous work completely removed. Over time.

The first #curl release with code present authored by 200 persons was done in 2015-04-22. In that release, we had already removed all traces of contributions from 20 authors.

In the latest release, 604 authors' code is still present. 171 authors' work have been replaced.

#curl


@gary_alderson I think you can expect me and not too many others to obsess and speak about historical #curl events and changes.



#curl



In 10 days (at #curl up 2024) I will do this presentation - out of which I seem to already have about 100 slides prepared...
#curl


with all due respect this sounds like a confusing cli argument design. I am the one doing it wrong :’) I personally can never remember all the #curl arguments, only the most commonly used ones, and -X is one that is easy to remember and can be used for many occasions. Maybe the solution should be to prefer -X always and a separate argument for whether the redirects should follow explicitly given method
#curl


#curl


bonus graph: fixed/introduced vulnerabilities in #curl over time:
#curl


Today we celebrate the five year anniversary of #curl's bug-bounty. It has resulted in 69 reported vulnerabilities and almost 80,000 USD payouts. Out of a total of 439 submissions. 86 of them were considered "informative", which mostly means they were handled as normal bugs.

Submit your suspected curl securirty issue here: hackerone.com/curl

#curl


#curl


Apparently San Francisco gets to enjoy #curl command lines in ads...
#curl


They fit excellently on the #curl cheat sheet coaster...
#curl


This box landed on my doorstep. The #curl up 2024 preparations continue!
#curl




#curl


#curl


#curl


I think it is worth for #hyper and the #rust ecosystem to work as #curl backend but not other way around. The only reason for curl to support hyper is to validate that the backend api is flexible enough and to have another "validator" for such interface. But probably it is one of those piece of code that maintainers are happy to push to third parties 😅


Today I want to mention how nice #opensource can be! Look at this #cURL issue github.com/curl/curl/issues/13… nice developers chatting on their own time about code and features with reproducible code and respect in mind! 😭 this is what I am here for!


#curl


#curl


I wonder if @bagder is aware that millions of Garmin users are carrying a #curl licence credit on their wrists