home.social

#boringssl — Public Fediverse posts

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

fetched live
  1. По обе стороны антибота: как я имитирую Chrome при скрейпинге и ловлю ботов по тем же сигналам

    Я собираю афишу города в одну карту из пяти источников. Два из них — Яндекс.Афиша и afisha.ru — собирать себя не хотят. И режут не так, как ждешь: ни логина, ни капчи на входе, ни «подтвердите, что вы не робот». Мой requests.get(...) ловит 403 — даже когда заголовки скопированы из Chrome один в один . Первая мысль была дурацкая: где-то не хватает куки или очередного sec-ch-ua . Оказалось — проблема раньше. К тому моменту, когда сервер читает мой браузерный User-Agent , он уже успел посмотреть, как именно клиент открыл защищенное соединение . Питоновский клиент палится ровно тем, как он здоровается.

    habr.com/ru/articles/1063180/

    #TLS_fingerprint #JA3 #JA4 #curl_cffi #антибот #парсинг #BoringSSL #fraud_score #bot_detection #http2

  2. “AWS-LC looks like a very active project with a strong community. […] Even the recently reported performance issue was quickly fixed and released with the next version. […] This is definitely a library that anyone interested in the topic should monitor.”

    #OpenSSL #BoringSSL #WolfSSL #AWSLC #HAProxy #OpenSource #FreeSoftware #FOSS #OSS #TLS #QUIC
    haproxy.com/blog/state-of-ssl-

  3. #GNOME Web is truly independent from #Google. Though still dependent on #Apple, they don't have as much power as Google. It is still better than a Google monopoly. And #webkit is developed with proper APIs and meant to be embedded in other applications unlike Google's #blink.

    One big feature missing is support for audio / video calls (webrtc). With #BoringSSL switching to Apache 2.0, a big blocker for webrtc support is resolved.

    bugs.debian.org/cgi-bin/bugrep

    #mozilla #firefox #epiphany

  4. I'm looking for a document that describes the reaction of OpenSSL after Heartbleed until recent years. What has happened? Redesign? Refactorings?

    Is OpenSSL 3 a designed in a better way? Or is it still the dumpster fire it once was?

    #openssl #libressl #boringssl #hearbleed

    EDIT: I'm looking for a summary, not a wealth of change logs and commits.

  5. @birnim I developed an app using #pyqtdeploy and #Kirigami a few years ago.
    One limitation I noticed that however which Python Qt API limits you to access Qt's Android API's
    that you have to use because of Android's interaction with files.
    In general you are more limited when having to call Java API's.
    The other thing was that Androids #openssl fork #boringssl was a limitation if your Qt is build with
    openssl.
    A smaller issue was to setup scripts for building and bootstrapping.