diff options
| author | Anonymous <anon@anon.com> | 2023-01-06 00:49:46 +0100 |
|---|---|---|
| committer | Anonymous <anon@anon.com> | 2023-01-06 00:49:46 +0100 |
| commit | f78259e60748b53f8dc06560da32708951f6f79f (patch) | |
| tree | 1b9065071a9f73b6ae8c24181cd8249c74d2168f | |
| parent | da9bda6b3f64a07255a7a77c24046c6a0ae9cdea (diff) | |
Updated add tcpmux service.md (markdown)
| -rw-r--r-- | agenda/add tcpmux service.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/agenda/add tcpmux service.md b/agenda/add tcpmux service.md index 1b47227..9eecef3 100644 --- a/agenda/add tcpmux service.md +++ b/agenda/add tcpmux service.md @@ -1,4 +1,4 @@ [rfc1078](https://www.rfc-editor.org/rfc/rfc1078.txt) is deprecated, but the protocol is too simple to not implement. -The implementation should feature an application level firewall, that correspond to the rules added to iptables/nftables to mitigate [security risks](https://en.wikipedia.org/wiki/TCP_Port_Service_Multiplexer#Security_risks). If that's not possible (or additionally), allow access only from within the VPNs. +The implementation should feature an application level firewall, that correspond to the rules added to iptables/nftables to mitigate [security risks](https://en.wikipedia.org/wiki/TCP_Port_Service_Multiplexer#Security_risks). If that's not feasible (or additionally), allow access only from within the VPNs. Bonus level: find as many clients that support tcpmux as possible
\ No newline at end of file |