This is my personal working copy of vger, patched where necessary to run on NetBSD.
Go to file
2021-02-25 18:37:48 +01:00
tests restore all tests after mistake 2021-02-03 21:00:38 +01:00
LICENSE Bump LICENSE to include 2021 2021-02-05 21:28:21 +01:00
main.c deal with too small/long requests 2021-02-25 18:37:48 +01:00
Makefile Fix make clean, find conditions are tricky 2021-02-05 21:24:32 +01:00
mimes.c add mimetype and autoindex option + minor changes 2021-01-10 09:30:35 +01:00
mimes.h add mimetype and autoindex option + minor changes 2021-01-10 09:30:35 +01:00
opts.h Add simple cgi support +: 2021-01-14 13:31:51 +01:00 Rewording 2021-02-08 21:55:55 +01:00
utils.c ready for Linux && disable solene's specific tests 2021-02-03 20:46:36 +01:00
utils.h Add simple cgi support +: 2021-01-14 13:31:51 +01:00
vger.8 Rewording 2021-02-08 21:55:55 +01:00

A simplistic and secure Gemini server

Vger is a gemini server supporting chroot, virtualhosts, CGI, default language choice, redirections and MIME types detection.

Vger design is relying on inetd and a daemon to take care of TLS. The idea is to delegate TLS and network to daemons which proved doing it correctly, so vger takes its request from stdin and output the result to stdout.

The average setup should look like:

           ↓           TCP request on port 1965
       relayd or haproxy
       or stunnel on inetd
           ↓           TCP request to a port of choice on localhost
       vger on inetd

Vger is perfectly secure if run on OpenBSD, using unveil() the filesystem access is restricted to one directory (default to /var/gemini/) and with pledge() only systems calls related to reading files and reading input/output are allowed. More explanations about Vger security can be found on this link.

For all supported OS, it's possible to run Vger in a chroot and drop privileges to a dedicated user.


git clone
cd vger
doas make install

On GNU/Linux, make sure you installed libbsd.

Running tests

Vger comes with a test suite you can use with make test.

Some files under /var/gemini/ are required to test the code path without a -d parameter.

Command line parameters

Vger has a few parameters you can use in inetd configuration.

  • -d PATH: use PATH as the data directory to serve files from. Default is /var/gemini
  • -l LANG: change the language in the status return code. Default is no language specified.
  • -v: enable virtualhost support, the hostname in the query will be considered as a directory name.
  • -u username: enable chroot to the data directory and drop privileges to username.
  • -m MIME : use MIME as default instead of "application/octet-stream".
  • -i : Enable auto index if no "index.gmi" file is found in a directory.
  • -c CGI_PATH : files in CGI_PATH are executed and their output is returned to the client.

How to configure Vger using relayd and inetd

Create directory /var/gemini/ (I'd allow this to be configured later), files will be served from there.

Create an user gemini_user.

Add this line to inetd.conf: stream tcp nowait gemini_user /usr/local/bin/vger vger

Add this to relayd.conf

log connection
tcp protocol "gemini" {
    tls keypair hostname.example

relay "gemini" {
    listen on hostname.example port 1965 tls
    protocol "gemini"
    forward to port 11965

Make sure certificates files match hostname: /etc/ssl/private/hostname.example.key and /etc/ssl/hostname.example.crt.

On OpenBSD, enable inetd and relayd and start them:

# rcctl enable relayd inetd
# rcctl start relayd inetd

Don't forget to open the TCP port 1965 in your firewall.

Vger will serve files named index.gmi if no explicit filename is given. If this file doesn't exist and auto index is enabled, an index file with a link to every file in the directory will be served.