Comments (15)
We also need DHE/ECDHE support from PyOpenSSL.
from hyper.
According to @reaperhulk on Twitter, Cryptography is about a month away from a release, meaning that PyOpenSSL is more than a month away. That's unfortunate for us, as it blocks our release.
from hyper.
Other options:
- Vendor PyOpenSSL and Cryptography using the versions that contain the NPN code.
- Move the HPACK-6 code into the h2-10 branch, prune it from the development branch and release the development branch alone, without h2-10 support.
from hyper.
I think we've done point releases to help out downstream before so if it's
just bindings you need we might able to sort something out? I think a month
is probably on the optimistic for 0.4 myself :-)
On 19 April 2014 17:11:24 Cory Benfield [email protected] wrote:
According to @reaperhulk on
Twitter,
Cryptography is about a month away from a release, meaning that PyOpenSSL
is more than a month away. That's unfortunate for us, as it blocks our release.
Reply to this email directly or view it on GitHub:
#37 (comment)
from hyper.
@public I genuinely just need the NPN bindings, assuming that's all that is blocking pyca/pyopenssl#86 (my read is that it is). Is there anything I can do to help make that happen (for example code review, testing etc. etc.)?
from hyper.
It looks like you also want the ECHDE stuff, but I believe we released that in 0.3 and PyOpenSSL just needs a release to support that? We could backport NPN to an 0.3.1 pretty easily so it's mostly a PyOpenSSL question at that point.
from hyper.
Yeah, that sounds right to me. =)
I'd like to get this moved forward one step: if we can get a release of cryptography then I can work on getting a release of PyOpenSSL.
from hyper.
Go ahead and file an issue against cryptography requesting a 0.3.1 with pyca/cryptography#857 backported and we can make a decision.
from hyper.
Done; see pyca/cryptography#941. @reaperhulk, @public, thanks for your receptiveness! Makes me feel a lot better about adding cryptography as an upstream dependency. =)
from hyper.
In case any user is keeping an eye on this issue, I have three outstanding pull requests on PyOpenSSL, of which one blocks release of hyper
. This issue blocks because to release without it would be to remove support for Python 3.3, which the current released version has support for.
The relevant issues:
- pyca/pyopenssl#110 (NPN, blocking)
- pyca/pyopenssl#120 (ALPN, non-blocking)
- pyca/pyopenssl#121 (
Connection.recv_into
, non-blocking)
from hyper.
an odd though, should new, beta version of pyOpenSSL be bundled with hyper until it is released if some feature is needed?
from hyper.
I thought about it. Don't want to do it yet, but might have to.
from hyper.
Again, for those keeping an eye, the blocking issue on PyOpenSSL is pyca/pyopenssl#15.
from hyper.
Screw it, I'm not blocking on PyOpenSSL any longer. I'll note that I'm regressing support for Python 3.3, and that we've got partial support for Python 2.7 and PyPy until PyOpenSSL ships a new release.
from hyper.
For the moment I'm closing all pyOpenSSL issues, because I simply no longer have faith in the ability of pyopenssl to ship further releases.
from hyper.
Related Issues (20)
- Ping does not work correctly HOT 3
- Edit on github link on RTD broken.
- Transfer of maintenance HOT 3
- HTTP20Adapter sends extra headers ?? HOT 20
- How to control ssl context in a HTTP20Adapter HOT 1
- hyper.contrib.HTTP20Adapter with requests.session not working on python 2.7
- Upgrade from HTTP/1.1. to HTTP2 not working HOT 2
- Could you please make MAX_CHUNK configurable? HOT 1
- Upgrade to the latest h2 HOT 2
- How resolve DNS to a specific IP?
- HTTP11Connection does not use http/1.1 protocol HOT 1
- hyper hangs while POSTing to Apple APNS servers HOT 2
- Forcing Cleartext HTTP2 Without Upgrade Mechanism HOT 3
- How can I add query parameters when using class HTTP20Connection?
- Python deprecation warnings: collections, imp, logging.warn
- basestring erroneously ignores unicode in Python2.7
- Client certificates?
- Retain connection in HTTP/2 using hyper to avoid authentication for every request
- HTTP20Connection.request has no mechanism to send duplicate headers HOT 3
- The orders of sending packages in Debug mode and Run mode are different.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hyper.