Skip to content

envoyproxy/envoy

main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

https://github.com/google/quiche/compare/5cc27c4cf..68e7ffc3a

```
$ git log 5cc27c4cf..68e7ffc3a --date=short --no-merges --format="%ad %al %s"

2023-07-13 bnc Remove IsSupportedTransportVersion().
2023-07-13 birenroy Removes a DCHECK that can be reached by fuzzing.
2023-07-13 wub Internal change
2023-07-12 wub Let QuicReceivedPacketManager trim ack ranges when packet is received, instead of when sending acks.
2023-07-12 haoyuewang Log all data in the sequencer when QUIC_HTTP_INVALID_FRAME_SEQUENCE_ON_SPDY_STREAM happens with no bytes ever consumed.
2023-07-11 quiche-dev Fixing tests in anonymous_tokens_rsa_bssa_client_test.cc.
2023-07-11 quiche-dev When the GFE issues a 413 error due to excessively long request headers, also send a Clear-Site-Data: "cookies" response header, but only if the portion of the cookie header we have is greater than a certain length.
2023-07-11 diannahu Internal change
2023-07-09 vasilvv Add a connection option (`kBSUS`) to force the server to buffer incoming streams until the SETTINGS frame is received.
2023-07-07 wub Internal change
2023-07-06 wub In QuicCryptoClientConfig: - Change session_cache_ from std::unique_ptr to std::shared_ptr. This allows multiple QuicCryptoClientConfig(s) to use the same Session Cache. - Add set_session_cache(). So a caller can change Session Cache after construction. - Remove mutable_session_cache(). It is the same as session_cache().
2023-07-06 quiche-dev Updating RsaBlindSignatureVerify in crypto_utils to use RSA struct only when verifying even for public metadata signature verification.
```

Signed-off-by: Vanessa Reimer <vreimer@google.com>
bd241eb

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
ci
July 13, 2023 13:02
July 13, 2023 10:21
November 1, 2022 12:58
DCO
September 15, 2017 12:23
August 10, 2022 09:30

Envoy Logo

Cloud-native high-performance edge/middle/service proxy

Envoy is hosted by the Cloud Native Computing Foundation (CNCF). If you are a company that wants to help shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented, consider joining the CNCF. For details about who's involved and how Envoy plays a role, read the CNCF announcement.

CII Best Practices Azure Pipelines Fuzzing Status Jenkins

Documentation

Related

Contact

  • envoy-announce: Low frequency mailing list where we will email announcements only.
  • envoy-security-announce: Low frequency mailing list where we will email security related announcements only.
  • envoy-users: General user discussion.
  • envoy-dev: Envoy developer discussion (APIs, feature design, etc.).
  • envoy-maintainers: Use this list to reach all core Envoy maintainers.
  • Twitter: Follow along on Twitter!
  • Slack: Slack, to get invited go here.
    • NOTE: Response to user questions is best effort on Slack. For a "guaranteed" response please email envoy-users@ per the guidance in the following linked thread.

Please see this email thread for information on email list usage.

Contributing

Contributing to Envoy is fun and modern C++ is a lot less scary than you might think if you don't have prior experience. To get started:

Community Meeting

The Envoy team meets twice per month on Tuesday at 9am PT. The public Google calendar is here: https://goo.gl/PkDijT

  • Meeting minutes are here
  • Recorded videos are posted here

Security

Security Audit

There has been several third party engagements focused on Envoy security:

  • In 2018 Cure53 performed a security audit, full report.
  • In 2021 Ada Logics performed an audit on our fuzzing infrastructure with recommendations for improvements, full report.

Reporting security vulnerabilities

If you've found a vulnerability or a potential vulnerability in Envoy please let us know at envoy-security. We'll send a confirmation email to acknowledge your report, and we'll send an additional email when we've identified the issue positively or negatively.

For further details please see our complete security release process.