sslyze VS aioquic

For Internally and Externally accessible websites – Can use hostname or IP address Sslyze command line tool - https://github.com/nabla-c0d3/sslyze/releases - current version is 4.1.0

3) If you are technically skilled then there are programs/scripts you can run that will tell you exactly what TLS/SSL settings your router supports by scanning it. I have used https://github.com/nabla-c0d3/sslyze in the past but that was a long time ago so not sure it still works well

There are many notable open-source projects (SSLyze, CipherScan, testssl.sh, tls-scan, …) and several SaaS solutions (CryptCheck, CypherCraft, Hardenize, ImmuniWeb, Mozilla Observatory, SSL Labs, …) to do a security setting analysis, especially when we are talking about TLS, which is the most common and popular cryptographic protocol. However, most of these tools heavily depend on one or more versions of one or more cryptographic protocol libraries, like GnuTLS, OpenSSL, or wolfSSL. But why is this such a problem?

SSLyze - Fast and comprehensive TLS/SSL configuration analyzer to help identify security mis-configurations.

One of the interesting patterns happening in Rust is io-less libraries. I'm not sure where best to link this phenomenon. It here s a open issue for an io-less quic library, from 2019, https://github.com/aiortc/aioquic/issues/4

It'd be so fracking sweet to see filesystems follow this pattern. If we could re-use the file system logic, but apply it to windows or fuse or Linux or wasm linearly-addressed-storage, that would allow such intensely cool forms of portability/reuse & bending/hacking.

for those wishing to use http3 with a Python web framework, the ASGI hypercorn[1] currently supports it.

made a Django example last week with a sample client based on the examples from aioquic[2]: https://github.com/djstein/django-http3-example

this example also includes the first pass at async Django REST Framework using adrift[3] based on these GitHub issues:

- https://github.com/encode/django-rest-framework/pull/8617

- https://github.com/encode/django-rest-framework/issues/8496

sources

[1]: https://github.com/pgjones/hypercorn

[2]: https://github.com/aiortc/aioquic

[2]: https://github.com/em1208/adrf

In your estimation where does the QUIC specification, HTTP/3 specification, WebTransport specification, aioquic QUIC and HTTP/3 implementation in Python https://github.com/aiortc/aioquic (notice the GoogleChrome/samples WebTransport sample code is described as local server "There's code for a sample local server at https://github.com/GoogleChrome/samples/blob/gh-pages/webtransport/webtransport_server.py") fit into the categories you color "Framework" and "Webserver"?

Whilst the article rightly mentions aioquic to use HTTP/3 with Python, it is only a minimal example server. Hypercorn is a compete ASGI server built on aioquic that is likely more useful practically.