_____ _ _ _ _ _ |_ _| |__ ___ | | | |_ __ (_)_ _____ _ __ ___ __ _| | | | | '_ \ / _ \ | | | | '_ \| \ \ / / _ \ '__/ __|/ _` | | | | | | | | __/ | |_| | | | | |\ V / __/ | \__ \ (_| | | |_| |_| |_|\___| \___/|_| |_|_| \_/ \___|_| |___/\__,_|_| ____ _ / ___| ___ _ __ | |__ ___ _ __ | | _ / _ \| '_ \| '_ \ / _ \ '__| | |_| | (_) | |_) | | | | __/ | \____|\___/| .__/|_| |_|\___|_| |_| ____ / ___| ___ _ ____ _____ _ __ \___ \ / _ \ '__\ \ / / _ \ '__| ___) | __/ | \ V / __/ | |____/ \___|_| \_/ \___|_| by Umbrellix uGopherServer, the universal gopher server See LICENSE for copyright information uGopherServer is a modern, featureful and relatively secure gopher daemon built to be run under inetd, available under the 2-clause BSD license. Binaries are available under the combination of the 2-clause BSD license, the SSLeay license and the OpenSSL license. uGS accepts the environment variables "REMOTE_ADDR" and "REMOTE_HOST" with the same semantics so that if it is being run behind some kind of proxy, it is possible for that proxy, with a counterpart shielding uGS, to pass the address through to uGS. (what? no. that's pelvic wording. what I meant was) uGS accepts the environment variables "REMOTE_ADDR" and "REMOTE_HOST" both meaning the same thing (Gopher client remote address), so that if UGS is being run behind some sort of proxy, it's possible for said proxy to pass the address of the client through to UGS. It is based on the proven codebase of Gophernicus 2014, and includes numerous additions for TLS support, including user privilege droppage, and obviously, TLS support. You MUST have OpenSSL available in /usr/lib and /usr/include for it to compile. (HTM) GitHub link (DIR) .. (ARC) Local tarball copy of the uGopherServer software (Bzip2 format) (ARC) Local tarball copy of the uGopherServer software (Gzip format) (BIN) Local tarball copy of the uGopherServer software (LZ4 format)