Rename the project to tls-proxy-tunnel to avoid name clashing

This project was rename to tls-proxy-tunnel to be clear that this
projct is a different project the the one from which I forked it.

Thanks to Jacob for his great cooperation.

Author: git001

.drone.jsonnet

@@ -1,22 +1,23 @@
 [package]
-name = "layer4-proxy"
-version = "0.7.1"
+name = "tls-proxy-tunnel"
+version = "1.0.1"
 edition = "2021"
-authors = ["Aleksandar Lazic <al-git001@none.at>","Jacob Kiers <code@kiers.eu>"]
+authors = ["Aleksandar Lazic <al-git001@none.at>"]
 license = "Apache-2.0"
-description = "Simple and fast layer 4 proxy in Rust"
+description = "Simple and fast TLS-Proxy tunnel in Rust"
 readme = "README.md"
-homepage = "https://github.com/git001/layer4-proxy-rs"
-repository = "https://github.com/git001/layer4-proxy-rs"
+homepage = "https://github.com/git001/tls-proxy-tunnel"
+repository = "https://github.com/git001/tls-proxy-tunnel"
 keywords = ["proxy", "network"]
 categories = ["web-programming"]
+publish = false
 
 # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
 
 exclude = [".*"]
 
 [[bin]]
-name = "layer4-proxy"
+name = "tls-proxy-tunnel"
 path = "src/main.rs"
 
 [dependencies]

Cargo.lock

@@ -7,7 +7,7 @@ RUN set -x \
   && apk upgrade --no-cache \
   && apk add --no-cache bash bash-completion curl bind-tools gcc musl-dev \
   && cargo install --path . \
-  && mv /usr/local/cargo/bin/layer4-proxy /usr/local/bin/layer4-proxy \
+  && mv /usr/local/cargo/bin/tls-proxy-tunnel /usr/local/bin/tls-proxy-tunnel \
   && apk del --no-cache gcc musl-dev \
   && rm -rf /var/cache/apk/* /usr/src /usr/local/rustup /usr/local/cargo/
 
@@ -20,4 +20,4 @@ COPY container-files /
 
 WORKDIR /tmp
 
-CMD ["/usr/local/bin/layer4-proxy"]
+CMD ["/usr/local/bin/tls-proxy-tunnel"]

Cargo.toml

@@ -1,9 +1,9 @@
-# layer4-proxy
+# tls-proxy-tunnel
 
 > Hey, now we are on level 4!
 
 
-`layer4-proxy` is a layer 4 proxy implemented by Rust to listen on specific ports and transfer TCP data to remote addresses (only TCP) according to the configuration.
+`tls-proxy-tunnel` is a layer 4 proxy implemented by Rust to listen on specific ports and transfer TCP data to remote addresses (only TCP) via a HTTP Proxy according to the configuration.
 
 ## Features
 
@@ -21,11 +21,11 @@
 sequenceDiagram
 
   participant CL AS Client
-  participant LP AS Layer4 Proxy
+  participant LP AS TLS-Proxy Tunnel
   participant UP AS Upstream Proxy
   participant DS AS Destination Server
 
-  CL->>LP: Connect to Layer4 Proxy via TCP<br/>SNI is used for routing
+  CL->>LP: Connect to TLS-Proxy Tunnel via TCP<br/>SNI is used for routing
   LP->>UP: Connect to Upstream Proxy via TCP
   LP->>UP: Send "CONNECT" and some other<br/>Upstream Proxy header
   UP->>DS: Connect to Destination Server
@@ -41,23 +41,23 @@ sequenceDiagram
 To gain best performance on your computer's architecture, please consider build the source code. First, you may need [Rust tool chain](https://rustup.rs/).
 
 ```bash
-$ cd layer4-proxy
+$ cd tls-proxy-tunnel
 $ cargo build --release
 ```
 
-Binary file will be generated at `target/release/layer4-proxy`, or you can use `cargo install --path .` to install.
+Binary file will be generated at `target/release/tls-proxy-tunnel`, or you can use `cargo install --path .` to install.
 
-Or you can use Cargo to install `layer4-proxy`:
+Or you can use Cargo to install `tls-proxy-tunnel`:
 
 ```bash
-$ cargo install layer4-proxy
+$ cargo install tls-proxy-tunnel
 ```
 
 Or you can download binary file form the Release page.
 
 ## Configuration
 
-`layer4-proxy` will read yaml format configuration file from `/etc/l4p/l4p.yaml`, and you can set custom path to environment variable `L4P_CONFIG`, here is an minimal viable example:
+`tls-proxy-tunnel` will read yaml format configuration file from `/etc/tpt/tpt.yaml`, and you can set custom path to environment variable `tpt_CONFIG`, here is an minimal viable example:
 
 ```yaml
 version: 1
@@ -67,7 +67,7 @@ via: &viaanchor
   target: www.test1.com
   headers:
     Host: www.test1.com
-    Proxy-Authorization: basic ${ENCODED_PW}
+    Proxy-Authorization: Basic ${ENCODED_PW}
     Proxy-KeepAlive: true
 
 servers:
@@ -96,14 +96,14 @@ For detailed configuration, check [this example](./config.yaml.example).
 ## Test run
 
 ```shell
-L4P_CONFIG=container-files/etc/l4p/config.yaml cargo run
+TPT_CONFIG=container-files/etc/tpt/config.yaml cargo run
 ```
 
 ## Thanks
 
-- [`l4p`](https://crates.io/crates/`l4p`), of which this is a heavily modified fork.
+- [`fourth`](https://crates.io/crates/fourth), of which this is a heavily modified fork.
 - [`layer4-proxy`](https://code.kiers.eu/jjkiers/layer4-proxy)
 
 ## License
 
-`layer4-proxy` is available under terms of Apache-2.0.
+`tls-proxy-tunnel` (`tpt`) is available under terms of Apache-2.0.

Dockerfile

@@ -133,9 +133,9 @@ fn load_config(path: &str) -> Result<ParsedConfigV1, ConfigError> {
 
     let log_level = base.log.clone().unwrap_or_else(|| "info".to_string());
     if !log_level.eq("disable") {
-        std::env::set_var("FOURTH_LOG", log_level.clone());
+        std::env::set_var("TPT_LOG", log_level.clone());
         env_logger::builder().default_format().init();
-        //pretty_env_logger::init_custom_env("FOURTH_LOG");
+        //pretty_env_logger::init_custom_env("TPT_LOG");
         //pretty_env_logger::init_timed();
     }
 

README.md

@@ -41,13 +41,13 @@ fn main() {
 }
 
 fn find_config() -> Result<String, Vec<String>> {
-    let possible_locations = ["/etc/l4p", ""];
-    let possible_names = ["l4p.yaml", "config.yaml"];
+    let possible_locations = ["/etc/tpt", ""];
+    let possible_names = ["tpt.yaml", "config.yaml"];
 
     let mut tried_paths = Vec::<String>::new();
     let mut possible_paths = Vec::<PathBuf>::new();
 
-    if let Ok(env_path) = std::env::var("L4P_CONFIG") {
+    if let Ok(env_path) = std::env::var("TPT_CONFIG") {
         possible_paths.push(PathBuf::from(env_path));
     }
 

container-files/etc/l4p/config.yaml container-files/etc/tpt/config.yamlcontainer-files/etc/l4p/config.yaml renamed to container-files/etc/tpt/config.yaml

@@ -1,5 +1,5 @@
 [Unit]
-Description=l4p - Layer 4 proxy
+Description=tpt - TLS-Proxy Tunnel
 
 After=network-online.target
 Wants=network-online.target
@@ -11,9 +11,9 @@ WantedBy=default.target
 Type=simple
 
 # Allow read-only access to the config directory
-ReadOnlyPaths=/etc/l4p
+ReadOnlyPaths=/etc/tpt
 # Path to the binary
-ExecStart=/usr/local/bin/layer4-proxy
+ExecStart=/usr/local/bin/tls-proxy-tunnel
 
 # Needs CAP_NET_BIND_SERVICE in order to bind to lower ports
 # When using ports above 1024, these should be made empty