Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust. (by microsoft)

Msquic Alternatives

Similar projects and alternatives to msquic

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better msquic alternative or higher similarity.

msquic reviews and mentions

Posts with mentions or reviews of msquic. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-04-02.
  • Avoiding HTTP/3 (for a while) as a pragmatic default
    4 projects | | 2 Apr 2023
    I referred to sockets as an API design, not to express an opinion on whether you should place your protocol implementations inside or outside the kernel. (Although that’s undeniably an interesting question that by all rights should have been settled by now, but isn’t.)

    Even then, I didn’t mean you should reproduce the Berkeley socket API verbatim (ZeroMQ-style); multiple streams per connection does not sound like a particularly good fit to it (although apparently people have managed to fit SCTP into it[1]?). I only meant that with the current mainstream libraries[2,3,4], establishing a QUIC connection and transmitting bytestreams or datagrams over it seems quite a bit more involved than performing the equivalent TCP actions using sockets.





  • My plan for making 256bit signed and unsigned integers in C. Please help me understand this concept better.
    2 projects | /r/C_Programming | 26 Mar 2023
    The documentation of MS QUIC says it is cross-platform, it should work on Linux, it has a CMake preset for Linux and you can download the prebuilt binary releases for Linux.
  • Best performing quic implementation?
    4 projects | /r/rust | 5 Mar 2023
  • Show HN: Protect Your CI/CD from SolarWinds-Type Attacks with This Agent
    4 projects | | 25 Jan 2023
    Hello HN, my name is Varun, and I am the co-founder of StepSecurity. Here is the backstory about Harden-Runner. We thoroughly researched past software supply chain security incidents. The devastating breaches of SolarWinds, Codecov, and others, have one thing in common – they attacked the CI/ CD pipeline or the build server.

    These incidents made it clear that a purpose-built security agent was needed for CI/ CD. While there are numerous agents available for desktops and servers, such as from CrowdStrike and Lacework, none have been tailored specifically to address the unique risks present in CI/CD pipelines.

    With the understanding that a specialized solution was needed to secure CI/CD environments, we developed Harden-Runner, an open-source solution tailored specifically for GitHub Actions hosted runners. It can be seamlessly integrated into your workflow by simply adding a step. The agent installation process is also lightning-fast, taking no more than 5 seconds to complete.

    Harden-Runner's security agent is designed to closely monitor all aspects of the workflow run, including DNS, network, file, and process events. This allows for real-time identification of any potential security breaches. To prevent incidents like the Codecov breach, where exfiltration of credentials occurred, Harden-Runner allows you to set policies that restrict outbound traffic at both the DNS and network layers. Additionally, we are actively working on implementing further restrictions at the application layer, such as using HTTP verbs and paths, to provide an even more comprehensive security solution.

    An excellent example of how Harden-Runner effectively blocks outbound traffic can be found in the following link: As you can see, all traffic to unauthorized endpoints is highlighted in red, indicating that it has been blocked; this is because these endpoints are not included in the allowed list defined in the GitHub Actions workflow file, which can be viewed here:

    One of the key features of Harden-Runner's monitoring capabilities is its ability to detect any tampering or alteration of files during the build process, similar to the SolarWinds incident. To further enhance security and protect against potential malicious tools or attempts to disable the agent, Harden-Runner includes a disable-sudo mode. This mode effectively disables the use of 'sudo' on the hosted runner, providing an additional layer of protection

    Harden-Runner has already been adopted by over 600 open-source repositories: To fully understand the capabilities of Harden-Runner and how it can protect against past supply chain attacks, please try out our attack simulator GitHub repository at I would love to hear your feedback.

  • Least painful path to multiplatform builds?
    4 projects | /r/cpp_questions | 10 Aug 2022 (QUIC / HTTP3)
  • msquic VS MsQuic.Net - a user suggested alternative
    2 projects | 15 Jul 2022
  • The Illustrated QUIC Connection
    2 projects | | 20 Jun 2022
    3 projects | /r/netsec | 22 Apr 2022
  • .plan
    11 projects | | 16 Nov 2021
  • The QUIC API OpenSSL will not provide
    2 projects | /r/programming | 27 Oct 2021
    I don't think that's true, Microsoft is already doing their own thing:
  • A note from our sponsor - WorkOS | 17 Apr 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →


Basic msquic repo stats
about 14 hours ago

microsoft/msquic is an open source project licensed under MIT License which is an OSI approved license.

The primary programming language of msquic is C.

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives