Nathan Johnson
Nathan Johnson
I would love to see a PR around this! I'm not yet familiar with the coraza project, but I might play it with next week when things are slow with...
As a followup, using the crate version of boringssl gets it to compile for this target. So followup question: What is the down side of using the crate version of...
@tristanmorgan @ketzacoatl I know I've been awol from fabio for a while now, and some of that is due to me no longer working for ENA and not using fabio...
I know i keep squashing changes / force pushing, but from this point I'm pretty happy with it and am running it locally so I think I'm hands off. I...
As far as reproducing the issue, I will try to work on a minimal code example to reproduce, but I can't share the actual code in question. But generally: POST...
@ghedo would a packet capture with session keys be helpful?
So right before the error, this is sent from server (quic-go) to client (quiche): And this is the response:
[quiche_issue_2108.tar.gz](https://github.com/user-attachments/files/21300973/quiche_issue_2108.tar.gz) This has the pcap as well as the keylog file.
> So, as far as I can tell the issue is caused by a failure to encrypt packets, so I don't think it would be caused by anything quic-go specifically...
Also, forgot to mention, I've tried this with the vendored boringssl as well as the crate version - both 4.17 and tip on that one as well. Same results.