Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

lsquic certificate size #173

Closed
prchander opened this issue Oct 1, 2020 · 6 comments
Closed

lsquic certificate size #173

prchander opened this issue Oct 1, 2020 · 6 comments
Labels
bug

Comments

@prchander
Copy link
Contributor

Hello, this is a question, not an issue. I am able to make successful connections with rsa2048 but with a higher bitesize, I am not able to establish a connection. Is there a size limit defined in lsquic? and if so where is it located?

Thank you
@dtikhonov
Copy link
Contributor

Thank you for the bug report! I have reproduced the issue. It affects gQUIC versions only; IETF QUIC versions are fine.

@prchander
Copy link
Contributor Author

Thank you for your reply. So how do I use IETF QUIC? I can specify version = Q050 for google QUIC but I do not see the syntax for IETF versions.

@dtikhonov
Copy link
Contributor

In http_client (I assume you mean http_client), you can do -o version=h3-31 (for example). Also, if you omit the option altogether, the engine will pick the highest version -- which is also "h3-31".

@prchander
Copy link
Contributor Author

Awesome, so what about using open quantum safe boringssl (https://github.com/open-quantum-safe/boringssl). I was trying to transfer a post-quantum algorithm cert but I get the error "[ERROR] SSL_CTX_use_PrivateKey_file failed". Am I generating the key and cert wrong or is it a transfer size limit?

@dtikhonov
Copy link
Contributor

The certificate size bug will be fixed in the next release.

The SSL_CTX_use_PrivateKey_file failure is in BoringSSL, it's likely not related to anything lsquic is doing.

litespeedtech pushed a commit that referenced this issue Oct 7, 2020
Release 2.22.0
fbc6cc0 
- [FEATURE] Extensible HTTP Priorities (HTTP/3 only).
- [FEATURE] Add conn context to packet-out memory interface (PR #175).
- [BUGFIX] gQUIC proof generation: allocate buffer big enough for
  signature (issue #173).
- [BUGFIX] Make library thread-safe: drop use of global variables
  (issue #133, issue #167).
- [BUGFIX] Deactivate only *recent* HQ frame, not any HQ frame.
- [BUGFIX] gQUIC server: associate compressed cert with SSL_CTX,
  instead of keeping them in a separate hash, potentially leading
  to mismatches.
- [BUGFIX] Stream data discard infinite loop: break on FIN.
- cmake: add install target via -DCMAKE_INSTALL_PREFIX (PR #171).
- Support randomized packet number to begin a connection.
- Mini and full IETF connection size optimization.
- http_client: specify HTTP priorities based on stream conditions.
@litespeedtech
Copy link
Owner

Fixed in 2.22.0 -- closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dtikhonov @litespeedtech @prchander