Am 29.04.2024 um 21:48 schrieb Konstantin Kushnir:
On 29.04.2024 19:40, saito wrote:
On 4/29/2024 2:48 AM, Christian Gollwitzer wrote:
While I like core features, I think this is a bad idea, given the
pace of Tcl development. If a security hole emerges, how long will it
take Tcl to release a fix??
Very good point. Perhaps a good candidate for tcllib?
I don't think it's possible to add things like TLS support to the Tcl
core. There is a wide range of issues: optimized encryption routines are platform-specific, overly sensitive to security, and must be carefully updated. And the main issue is license. The mtls module uses mbedTLS
library which is distributed under Apache2.0 and GPL, but Tcl uses own BSD-like license.
For tcllib it is also not suitable. The main issue is the license incompatibility. And also, tcllib is mainly for Tcl modules written in
Tcl, but this module is written in C.
I doubt that the TLS solution will be "official" someday. It looks like
it will always be out-of-box provided by semi-official and custom Tcl distributions.
Thanks, Konstantin, for your valuable contribution.
I thought about that, as TLS support is practically always required and
it would enable many applications out of the box.
The plugging of svgnano into Tk was a big success. We are now able to
have scalable images and a scalable gui. To have a difficult feature
always available is just a win, even in a restraint manner.
Thank you for all,
Harald
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)