|
2026-09-05
| ||
| 21:56 | • Ticket [2e20632151] tls::init -securitylevel option problem status still Open with 3 other changes artifact: d9c67f23ba user: bohagan | |
| 20:51 | • Ticket [2e20632151]: 5 changes artifact: f942a9be28 user: bohagan | |
|
2026-09-02
| ||
| 09:31 | • New ticket [2e20632151]. artifact: e6b8d9741c user: anonymous | |
| Ticket Hash: | 2e206321514eb6ea935dcb321c1f85080779a36a | ||
| Title: | tls::init -securitylevel option problem | ||
| Status: | Open | Type: | Code Defect |
| Severity: | Important | Priority: | Immediate |
| Subsystem: | Resolution: | Open | |
| Last Modified: |
2026-09-05 21:56:50 17.6 days ago |
Created: |
2026-09-02 09:31:27 21.1 days ago |
| Version Found In: | 2.0.1 | ||
| User Comments: | ||||
anonymous added on 2026-09-02 09:31:27:
"tls::init -securitylevel 4 " executes with no errors as it is but opening a socket now with this configuration causes this error : "bad option "-securitylevel": and only recognises "-security_level" as the correct option.. when the _ is used int tls::init its not recognised and says "-securitylevel" is valid. I hope my other issue with a simple http::geturl failing to open socket has nothing to do with anything else, im probally going to be using a earlier build. thx. bohagan added on 2026-09-05 20:51:31:
Looks like the tls.tcl file uses -securitylevel while the C code uses -security_level. So the fix is to update tls.tcl. I'll get that fixed. This only effects tls::socket, so use tls::import on an existing socket as a work-around. bohagan added on 2026-09-05 21:56:50:
Fixed in [225266f7674091df]. | ||||