home.social

#urllib3 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #urllib3, aggregated by home.social.

fetched live
  1. I'm happy to announce that #urllib3 has a new lead maintainer: @illiav 👏 Illia has been contributing to urllib3 for over 3 years now and I'm confident will make a great lead of the project. I'll continue to maintain the project alongside my other co-maintainers @quentinpradet and @shazow

    github.com/urllib3/urllib3/iss

  2. I can't count how many times I've put import requests behind a warnings filter after urllib3's developers decided they can dictate what libraries the end user has.

    github.com/urllib3/urllib3/iss

    #Python #Requests #Urllib3 #OpenSSL #LibreSSL

  3. Splunk

    Set up Splunk enterprise on local system and installed some attack data from here

    But the ./bin/requirements.txt file is wrong .. so replace

    #requests==2.25.1
    requests==2.28.1

    #urllib3==2.3.0
    urllib3==1.26.12

    Then edit the yaml file and this will import the dataset directly into Splunk..

  4. It's here! The 2024 annual report for , a relatively quiet year that included work on HTTP/2 and Web Assembly (WASM). We include our plans for Python 2 deprecation, please take a look. $3,300 worth of bounty issues exist today!

    quentin.pradet.me/blog/urllib3

  5. Hot off the presses!!! 🔥 Find me at tomorrow and tell me how you're supporting your open source middle-stack for a sticker!

  6. Python's urllib3 has fixed a low severity vulnerability in version 2.2.2, which was released yesterday.
    This vulnerability has been assigned CVE-2024-37891.
    For those not familiar with urllib3, it describes it's self as

    a powerful, user-friendly HTTP client for Python

    It is used by many projects and libraries, including the popular requests library.

    github.com/urllib3/urllib3/sec

    #CVE_2024_37891 #urllib3 #pythonSecurity

  7. landed its first HTTP/2 PR, many more where that came from!

    We're still fundraising to release HTTP/2 support, forward this URL to folks who have been wanting HTTP/2 support in :

    opencollective.com/urllib3/upd

  8. 📦 We released v2.1.0 today! This release removes many of the features that have been deprecated for removal in v2. Security fixes will continue to be available in v1.26.x thanks to @[email protected]

    github.com/urllib3/urllib3/rel

  9. v2.0.4 is now available! This was the first release by our new maintainer Illia Volochii 🎉

    now uses stdlib hostname verification if possible
    – Union operator support for HTTPHeaderDict
    – Emits http.client.connect audit events

    github.com/urllib3/urllib3/rel

  10. New release of , v1.26.16 backports a bugfix for PoolManager thread-safety when accessing a high number of distinct origins to not close responses before they complete: github.com/urllib3/urllib3/rel

  11. 2.0* is a true horror story. Whenever I fix one package not to downgrade my whole testing container to the previous version, I discover another broken package.

    The most horrendous part is that they usually aren't broken by deliberate API changes — they rely on implementation details!

  12. This whole / situation is getting absurd.

    I don't have sympathy for or . However, I can understand that they had good reasons to fork OpenSSL, and that switching back today would be hard.

    I can understand projects refusing to officially declare support and rejecting workarounds. But pushing LibreSSL hate to the point of blocking implementations that don't link to OpenSSL is just horrible. Users get in the crossfire, again.

    github.com/urllib3/urllib3/iss

  13. Oh, just great!

    It turns out that added a totally bonkers OpenSSL version check, and they broke a lot of systems as a result. Ofc the immediate result is dozens of packages pinning urllib3 < 2, and if they continue their negligence it's going to go into hundreds.

    Ofc, it is a mess that distro maintainers will have to clean up eventually. I mean, removing the pins when they do not apply to us.

    github.com/urllib3/urllib3/iss
    github.com/urllib3/urllib3/pul

  14. New release v2.30.0 which adds explicit support for v2.0.0! 🚀 Let's go!!!

    github.com/psf/requests/releas

  15. One thing that the team does that I wonder if other projects do is ensure someone is around to help in case of disasters. Very similar to on-call but ad-hoc and during fragile moments like releases of new default behaviors/major versions. Do any other projects do this?

  16. v2.0.1 has been released with two small fixes:

    – Fixed socket leak after failed cert hostname or fingerprint verification (thanks @graingert !)
    – Fixed an issue when .read(0) was called on an empty response buffer (thanks @quentinpradet !)

    github.com/urllib3/urllib3/rel

  17. Over 1 million installs of a new major version in 24 hours (and single-digit number of integration issues 😏)

    pepy.tech/project/urllib3?vers

    Next hurdle is being unpinned by Requests, then we'll *really* know if there are any big issues... 😬

  18. 2.0.0 was released! FWICS most of the "breaking" changes are delayed until 2.1.0. However, I'm pretty sure I've seen some project importing vendored six from urllib3, and that's certainly going to break since it is gone ;-).

    Ofc pinned <2 in random places is going to be a pain.

    urllib3.readthedocs.io/en/late