luxferre/BFG
1
0
Fork 0
Code Actions Activity

Implemented auto TLS upgrade support

Browse Source
This commit is contained in:
Luxferre
2024-10-16 21:03:06 +03:00
parent f0cd4aadf6
commit 638333b62c
3 changed files with 18 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5 -2
View File
@@ -36,6 +36,7 @@ The following features are already (fully or partially) supported in BFG.
* In-page text search
* Ini-based customization of the current Ttk theme, content fonts and colors
* Non-TLS mode for systems without TclTLS support
* Automatic TLS upgrade support for Gopher and other protocols (configurable in the `bfg.ini` file)
* Opening links in Torified windows (for the systems with torsocks installed)
## Non-supported features
@@ -117,7 +118,7 @@ You don't need to do any special combinations to open links in Tor once the pare
BFG ships with a `bfg.ini` file that holds your configuration values and bookmarks.
The main configuration sections are:
* `[net]`: network-related configs, currently has "timeout" parameter and an optional "tls" parameter
* `[net]`: network-related configs, currently has "timeout" parameter and an optional "tls" parameter (`auto` by default)
* `[widget]`: general UI widget appearance (ttkTheme, font (button font), entryfont, statusfont)
* `[style.general]`: general content area appearance (textfont, monofont\*, foreground color, background color)
* `[style.link.normal]`: normal link colors (foreground, background)
@@ -184,7 +185,9 @@ The [Scroll protocol](gemini://scrollprotocol.us.to/) is essentially advertised
### Why does a Gopher-over-TLS (`gophers://` URL) resource still show plain `gopher://` links?
Due to a purely technical limitation of the Gopher protocol (or rather the Gophermap format) itself, we cannot determine if a particular Gophermap entry points to a plain Gopher or a Gopher-over-TLS resource. Hence, only the links belonging to the same host/port pair that was already opened with a `gophers://` link are displayed as `gophers://` links. Everything else needs to be adjusted manually for now. Sorry for the inconvenience.
Due to a purely technical limitation of the Gopher protocol (or rather the Gophermap format) itself, we cannot determine if a particular Gophermap entry points to a plain Gopher or a Gopher-over-TLS resource. Hence, only the links belonging to the same host/port pair that was already opened with a `gophers://` link are displayed as `gophers://` links.
If the `tls` parameter in the `[net]` section of the `bfg.ini` file is set to `auto`, the client will try opening the TLS connection first regardless of the link type, so you don't have to worry about the URL scheme anymore..
### My system (or Tclkit) doesn't have TclTLS available, can I still use BFG for plaintext protocols?