-
Notifications
You must be signed in to change notification settings - Fork 201
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.
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
qh3 is having a major version #943
Comments
I just verified with latest version and it does break. That was the full traceback, if it gives you any hints:
|
Unfortunately the stack trace isn't helpful. |
These lines should help provide all useful information about the QUIC connection establishment pymobiledevice3/pymobiledevice3/remote/tunnel_service.py Lines 387 to 417 in 9713fab
|
Ah. I think I got what is wrong. extract from changelog: Breaking: You may no longer pass certificates (along with private keys) as object that comes from cryptography. You have to encode them into PEM format.
I suppose private_key and cert are objects from cryptography. |
I still need it as a PSK, so just changing the encoding of it? |
Also, I just released v4.1.3 with Huge thanks for the heads up! 😊 |
Of course, you may keep your private key and cert object for ext usage. Just convert it when establishing the quic tunnel. |
I have a cryptography's configuration = QuicConfiguration(
alpn_protocols=['RemotePairingTunnelProtocol'],
is_client=True,
certificate=cert.public_bytes(Encoding.PEM),
private_key=private_key.private_bytes(Encoding.PEM, PrivateFormat.TraditionalOpenSSL,
NoEncryption()).decode(),
verify_mode=VerifyMode.CERT_NONE,
verify_hostname=False,
max_datagram_frame_size=RemotePairingQuicTunnel.MAX_QUIC_DATAGRAM,
idle_timeout=max_idle_timeout
) Still am getting the same errors. Can you guide me as to how exactly should I convert the data-structure? |
Try the following: dismiss the |
The new version seems to work great :) |
Perfect 👌 |
The release process is in progress. Expect the PyPI tag to be pushed in an hour or so. regards, |
Just tested and it works great :) |
Hello there,
As pymobiledevice3 was a early adopter of qh3 and now a "long" dependent of it,
I though to give a heads up about the forthcoming major of qh3.
The idea would to promote qh3 v1 to stable, but before that the least we can do is to ensure the compatibility.
Normally it should work as is.
The main change to be concerned about is: "qh3 no longer depend on anything. not even cryptography". Wrote a dedicated bridge using PyO3 and aws-lc-rs. The idea behind this is to ease the http3 adoption through niquests
I can see that you have an explicit dependency on cryptography.
Would you assess the v1.0.0b1 so that I can move forward? See jawah/qh3#25
Regards,
The text was updated successfully, but these errors were encountered: