public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Tapani Tarvainen <ipfire@tapanitarvainen.fi>
To: development@lists.ipfire.org
Subject: sslh (and some general AddOn questions)
Date: Fri, 15 Jan 2021 13:35:45 +0200	[thread overview]
Message-ID: <20210115113545.GA2763257@vesikko.tarvainen.info> (raw)

[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]

Dear all,

The version of sslh in IPFire now, 1.7a, is very old, some 10 years,
and its parameters are hardcoded in /etc/init.d/sslh for one specific
use case (IPFire admin access).

I have a different use case for it: sharing port 443 with OpenVPN and
a web server in Orange. That would be easy with a more recent version
of sslh (OpenVPn first appeared in 1.8 in July 2011).

So I'd like to update the sslh AddOn with

(1) A more recent version of sslh. Latest upstream version is 1.21,
released on 11 July 2020, and I see no obvious reason not to use it,
although for the present purpose some older version might do as well.

Are there some specific procedures for updating AddOn binaries?

(2) Parameters in a configuration file. I'd be happy to edit it by
hand, writing a GUI for it would probably not be worth the trouble.

Is there some convention or guidelines where in IPFire such
configuration files should be put? Debian uses /etc/defaults/sslh,
sslh changelog presently suggests /etc/sslh.cfg.

Should a default configuration file be packaged as a separate
file, or should the init script create one if it's missing
or should it just use the hardcoded defaults in that case?

Are there guidelines or instructions for doing or proposing such
changes to AddOns?

I can't even find a category for them in the Bugzilla. Is there one?

My apologies if I'm missing something obvious, pointers to
documentation would be welcome.

-- 
Tapani Tarvainen

             reply	other threads:[~2021-01-15 11:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 11:35 Tapani Tarvainen [this message]
2021-01-15 12:43 ` Adolf Belka
2021-01-15 13:22   ` sslh Tapani Tarvainen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210115113545.GA2763257@vesikko.tarvainen.info \
    --to=ipfire@tapanitarvainen.fi \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox