| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA. This is necessary for legal reasons before we can look at your contribution. Please follow these steps to help rectify the issue:
Thanks again to your contribution and we look forward to looking at it! |
Sorry, something went wrong.
There was a problem hiding this comment.
For the little effect my review can have, I approve, and comment made by OP are correct.
RFC 4366 has been obsoleted by RFC 6066.
If another reviewer is wondering, this one is already cited a couple of lines after the end the diff.
Sorry, something went wrong.
|
Thanks for the review. Any thing more to add to this patch? |
Sorry, something went wrong.
|
@Carreau @serhiy-storchaka anything more i can improve to this patch? |
Sorry, something went wrong.
|
@serhiy-storchaka - shall we move forward with this? The change looks good to me. These are See Also links which informative guidance ( like introduction to SSL/TLS from Apache site in the same list). Removing the obsolete RFC and mentioning the correct ones seems to be right thing to do. |
Sorry, something went wrong.
|
RFC references should be updated only if the ssl module actually supports new RFCs and is not sticked to obsolete RFCs. I'm not a SSL expert and don't know if it is. @tiran is an expert. There are also other references to obsolete RFCs in ssl.rst and _ssl.c. Shouldn't they be updated too? |
Sorry, something went wrong.
There was a problem hiding this comment.
Please update inline references, too.
Also please add RFC 6125 and link it from match_hostname.
Sorry, something went wrong.
There was a problem hiding this comment.
This RFC is referenced in the documentation of RAND_add. You need to update both occurrences.
Sorry, something went wrong.
There was a problem hiding this comment.
Done.
Sorry, something went wrong.
There was a problem hiding this comment.
5280 is correct. Please update documentation of SSLSocket.getpeercert, too.
Sorry, something went wrong.
There was a problem hiding this comment.
Done
Sorry, something went wrong.
There was a problem hiding this comment.
RFC 6066 is the successor to 4366. Please update documentation of HAS_SNI.
Sorry, something went wrong.
There was a problem hiding this comment.
Done
Sorry, something went wrong.
|
@chkumar246 Thanks for the initial work on this at the PyCon Pune sprints. Do you think you may be able to find time to follow up on @tiran's feedback, or would you prefer that someone else pick up the change and finish up those final details? |
Sorry, something went wrong.
|
Added the sprint label, as this PR was submitted at the PyCon Pune 2017 core development sprint. |
Sorry, something went wrong.
|
Sorry for the late reply, I will update the PR soon. |
Sorry, something went wrong.
* RFC 1750 has been been obsoleted by RFC 4086. * RFC 3280 has been obsoleted by RFC 5280. * RFC 4366 has been obsoleted by RFC 6066.
Sorry, something went wrong.
|
Just add the url https://bugs.python.org/issue19180 |
Sorry, something went wrong.
…pythonGH-148) * RFC 1750 has been been obsoleted by RFC 4086. * RFC 3280 has been obsoleted by RFC 5280. * RFC 4366 has been obsoleted by RFC 6066. (cherry picked from commit 63c2c8a)
Push 61 bundle (doc-only, post push-60 100/100 PURE close).
(1) docs/cinderx-oracle-env-spec.md (NEW, 5632 B):
Theologian-authored env-spec per supervisor 01:30:42Z PRIORITY
directive after cinderx_dev oracle attempt failed at 01:16:27Z
(-X jit didn't activate JIT + cross-arch confound). Spec covers
build equivalence, JIT activation verification (force_compile +
is_jit_compiled, NOT -X jit alone), test-harness equivalence,
warmup threshold handling, observed failure modes, application
procedure for W-PERF-PRE-W27C-BISECT.
(2) docs/w-protocol-codify-spec.md (P11 + P12):
P11 — cinderx_dev Oracle Environment Specification: rule that any
cinderx_dev oracle invocation MUST follow env-spec procedure.
Origin: pythia D-1777065234 python#3 deferred ~10 days; closed by
01:32:28Z env-spec landing.
P12 — Alex-Pending Escalations Not Self-Liftable: caps the
self-lift precedent supervisor invoked at 00:04:33Z. Rule: no
agent may self-lift an Alex-pending hold; alternative paths
execute on their own merits without 'hold-lift' framing.
Origin: pythia python#145 python#1 + python#147 python#2 + python#148 python#2.
No code changes. Reference-only push.
Push 62 (doc-only) — env-spec updated with lessons from 02:33Z dry-run + 02:39Z successful oracle execution that produced Phoenix-vs-Cinder verdict (Phoenix faster on 3/3 benches, sub-1.0x inherited from Cinder). Updates per theologian 02:41:37Z: - Phoenix JIT activation: import _cinderx FIRST, then import cinderjit (corrects v1 assumption that cinderjit was directly importable) - cinderx_dev JIT activation: from cinderx import jit; jit.force_compile - Binary paths: ~/local/cinderx_dev/python-3.12/python (corrects v1 assumption of ~/local/cinderx_dev/cinderx/python) - LD_LIBRARY_PATH + PYTHONPATH env requirements for cinderx_dev - Same-arch comparison (both ARM64 on devgpu004) verified working - Application result section: oracle verdict + per-bench numbers - Failure modes from 01:16Z (-X jit didn't activate) + 02:33Z (API enumeration gap) + both resolved methodologies Closes pythia python#148 python#4 (spec-from-single-failure shipping before empirical validation). v2 ships AFTER successful oracle execution.
| Back | FazBrowse Home | New Git URL |
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.