Re: Yet another gemini server
Message headers
From: Andrea Biscuola <a@abiscuola.com>
Subject: Re: Yet another gemini server
Date: Mon, 2 Jan 2023 23:15:19 +0100
Message-ID: <20230102231519.4b3efee6d54ccff7b1772ea0@abiscuola.com>
Message content
Hi.
First of all, sorry for the late answer, I was on vacation :)
On Mon, 12 Dec 2022 00:29:37 +0100
pepinno@thinkpad.naleco.com.NOSPAM (Pepinno The Great) wrote:
Andrea Biscuola <a@abiscuola.com> wrote:
>Hi all!
>
>Yes, I know, why re-invent the wheel? Well, because it's fun :)
>
> https://lab.abiscuola.org/gmnxd
>
>It's a gemini server that works with inetd and requires a reverse proxy in front of it for TLS
>acceleration. I've built it for my personal use case: an OpenBSD server already using relayd(8)
>for the web.
>
Hi. The README file for Gmnxd says:
>
At this time, gmnxd(8) only runs on OpenBSD, considering it
makes active use of pledge(2) and unveil(2) and other OpenBSD
specific functions.
>
What are your plans about generalizing the code so that it compiles on
Linux?
>
>
Good question :)
When I started to work on it, having a portable branch was a "nice to have" that I put at the bottom
of the requirements list.
However, the code itself is really basic and a port probably require some just some hours of work.
Mind that, _I_ don't plan to use gmnxd on linux anytime soon, but if somebody would like to have
it work on some linux distributions, I wouldn't mind doing the work (or accepting patches for it).
That's said, there are two ways, that I see, to make gmnxd portable:
1 - Doing it quick: things like pledge and unveil becomes no-ops and things like strlcpy are added
to the codebase.
2 - Doing it right: find a proper way to sandbox gmnxd on linux (landlock?). However I'm no expert
on how to do something like that on linux, so I may need some help with it.
I may give it a shot in the next days and see, first, what a "quick" port would look like.
Andrea.
Related
Parent:
Start of thread: