Archived

This repository has been archived on 2024-06-18. You can view files and clone it, but cannot push or open issues or pull requests.

History

Philippe PITTOLI b1078dfe98 renaming msg.[ch] in message.[ch]		2018-10-09 13:20:26 +02:00
..
Makefile
README.md	readme + filename convention for diags	2017-09-10 00:30:45 +02:00
remotec.c	renaming msg.[ch] in message.[ch]	2018-10-09 13:20:26 +02:00
remoted.c	s/process/client/g	2018-10-04 01:22:50 +02:00

README.md

remoted

This service creates a path on the relevent remote location, going through anything network-related: TCP, UDP, HTTP, ...

TODO

authorizations
code the -d option

authorizations

The idea is to have a simple configuration file for authentication of remote connections, such as:

table dynusers    # dynamic user table

clients = { "client123", alice.example.com, john@doe.com }
localclients = { pamuser1, <dynusers> }

level1services = { pongd, weather }

ifext = enp0s25
pass in on $ifext from any for all to local services $level1services
pass out on $ifext from local for $localclients to any services $level1services

block all