Ticket Change Details
Bounty program for improvements to Tcl and certain Tcl packages.

Artifact ID: b5b16a04d5462fe5649aaa46d2b6cdba0f0aee43aa4121a9e2b76f7b18d4a955
Ticket: f798e2ea1299e4fe603c8bdbfbfea3c2e7beb4d9
TclTLS does not retain socket state when importing
User & Date: anonymous on 2017-12-20 22:15:19

  1. foundin changed to: "1.7.14"
  2. icomment:
    11:42 <@ijchain> <rmax_> rkeene: [tls::import] appears to switch a socket that was in -blocking 0 mode before to -blocking 1.
    11:44 <@ijchain> <rmax_> ... it also sets -translation to {lf lf}
    11:45 <@ijchain> <rmax_> Haven't compared it with the old version yet, but -blocking 1 would explain the behaviour I am seeing.
    11:47 <@ijchain> <rmax_> it also enforces -encoding binary
    11:52 <@ijchain> <rmax_> Indeed, if I hack [fconfigure $sock -blocking 0 -buffering none -encoding utf-8] (copied from tkchat) into jabberlib immediately after tls::import/tls::handshake, the hang is gone.
    11:53 <@ijchain> <rmax_> rkeene: I think this is a regression from the old tls package.
    11:54 <@ijchain> <rmax_> [tls::import] should probably not change any [chan configure] options.
    11:56 <@ijchain> <rmax_> OK, so old tls already changed -translation to lf.
    11:57 <@ijchain> <rmax_> But it does retain blocking state and encoding.
  3. login: "anonymous"
  4. mimetype: "text/plain"
  5. private_contact changed to: "7855111259b8caa9dbbbdee158b103bb190501cd"
  6. severity changed to: "Severe"
  7. status changed to: "Open"
  8. title changed to: "TclTLS does not retain socket state when importing"
  9. type changed to: "Code Defect"