Skip to content

History / Phase 28 amissl issue

Revisions

  • Correct AmiSSL #111 framing: it was CPU speed, not a bug The filed AmiSSL issue turned out to be a processor-speed limitation, not an AmiSSL defect. Drop the bug-tracker link and state the resolution plainly on both pages.

    @sidick sidick committed Jun 21, 2026
    54fbb72

  • Cross-connection poison fixed: clear OpenSSL error queue before SSL ops. Signed-off-by: Simon Dick <simond@irrelevant.org>

    @sidick sidick committed Jun 21, 2026
    e5cc985

  • urequests: shared SSLContext + close-on-failure; correct the framing. The TLS flakiness is a post-handshake server reset, not CDN/handshake fingerprinting -- AmiSSL handshakes fine, then the exchange resets. Signed-off-by: Simon Dick <simond@irrelevant.org>

    @sidick sidick committed Jun 21, 2026
    b640bf2

  • urequests hardened: TLS now on the single BIO transport. Signed-off-by: Simon Dick <simond@irrelevant.org>

    @sidick sidick committed Jun 21, 2026
    8efca81

  • asyncio-over-TLS works; note BIO stream path is more resilient. Signed-off-by: Simon Dick <simond@irrelevant.org>

    @sidick sidick committed Jun 21, 2026
    5fea77b

  • Refresh Phase 28 / 29 pages with latest in-tree updates.

    @sidick sidick committed Jun 2, 2026
    6a5efd9

  • Import Amiga port design log and per-phase plans from in-tree docs/.

    @sidick sidick committed Jun 2, 2026
    fd6c66c