Hi! So I took a look at #1863 <https://github.com/pyca/cryptography/issues/1863> and I think none of the methods mentioned in the ticket are bound (except the one that is already crossed out in the list, SSL_CTX_set_tlsext_status_cb). Also, I haven't learned much C yet, is that going to be a problem while working on this issue? :-)
Thanks a lot for answering my questions! It means a lot! :-) Warm regards, Eeshan Garg On Thu, Apr 30, 2015 at 9:41 PM, Paul Kehrer <paul.l.keh...@gmail.com> wrote: > Take a look at 1863 and 1864 for some discussion about what needs to be > bound. It looks like a first pass might be excluding any of the OCSP > methods listed in 1863. You'll also want to verify that the items listed > aren't already bound. > > > On April 29, 2015 at 9:34:38 AM, Eeshan Garg (jerryguitar...@gmail.com) > wrote: > > Hi! > > So I submitted two pull requests for < > https://github.com/pyca/cryptography/issues/1870>. And both have them > have been merged and the issue has been closed. :-) > > I have a couple of questions. So, you said that < > https://github.com/pyca/cryptography/issues/1863> is challenging and > requires some discussion; in the meantime, is there anything I should read > or go through (code or documentation) before working on this issue? Also, > is it necessary to leave a comment on an issue indicating that you are > working on it or plan on working on it? :-) > > Thanks & regards, > Eeshan Garg > > On Wed, Apr 29, 2015 at 9:28 AM, Eeshan Garg <jerryguitar...@gmail.com> > wrote: > >> Hey Paul! >> >> I am working on the first one right now and I'll submit a PR for it soon! >> I'll ask on IRC or on the mailing list if I have any questions. :-) >> >> Thanks & regards, >> Eeshan Garg >> >> On Wed, Apr 29, 2015 at 3:13 AM, Paul Kehrer <paul.l.keh...@gmail.com> >> wrote: >> >>> Hey Eeshan, good to hear from you again. Take a look at >>> https://github.com/pyca/cryptography/issues/1870 and >>> https://github.com/pyca/cryptography/issues/1863. The latter is more >>> challenging and requires some discussion so starting with 1870 might >>> be a good idea. >>> >>> -Paul >>> >>> On Tue, Apr 28, 2015 at 12:46 PM, Eeshan Garg <jerryguitar...@gmail.com> >>> wrote: >>> > Hello! >>> > >>> > I really want to contribute to pyca/cryptography. I already have a >>> > development environment setup and I have run the tests. At the PyCon >>> sprints >>> > I worked on <https://github.com/pyca/cryptography/issues/1440>, and I >>> also >>> > submitted a PR for it <https://github.com/pyca/cryptography/pull/1841>, >>> but >>> > it was decided that we won't be moving forward with what I was working >>> on. >>> > >>> > It would mean a lot to me if someone could give me some guidance and >>> help me >>> > find something to work on and get started. :-) >>> > >>> > Thanks, >>> > Eeshan Garg >>> > >>> > _______________________________________________ >>> > Cryptography-dev mailing list >>> > Cryptography-dev@python.org >>> > https://mail.python.org/mailman/listinfo/cryptography-dev >>> > >>> _______________________________________________ >>> Cryptography-dev mailing list >>> Cryptography-dev@python.org >>> https://mail.python.org/mailman/listinfo/cryptography-dev >>> >> >> > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev@python.org > https://mail.python.org/mailman/listinfo/cryptography-dev > > > _______________________________________________ > Cryptography-dev mailing list > Cryptography-dev@python.org > https://mail.python.org/mailman/listinfo/cryptography-dev > >
_______________________________________________ Cryptography-dev mailing list Cryptography-dev@python.org https://mail.python.org/mailman/listinfo/cryptography-dev
