From: KOS <sv3ora@qrp.gr>
To: <galene@lists.galene.org>
Subject: [Galene] Message from KOS
Date: Wed, 20 Dec 2023 12:19:05 +0000 [thread overview]
Message-ID: <Mr.FqoYVgpooJD.yHIGsTlnOJ6@qrp.gr> (raw)
In-Reply-To: <Mr.FqoYVgpooJD.yHIGsTlnOJ6@qrp.gr>
Hello,
I have compiled Galene for Windows 10 and it works perfectly. Thanks so
much about this amazing and lightweight program!
I am using it for family usage, under a static IP address on ADSL.
Because of family usage, I do not need a certificate, the self-signed certificate
is enough for me.
I accept this certificate on the family browsers and everything runs well.
The problem is that when the Galene server restarts, a new self-signed certificate
is created (probably) and all the family members have to accept again the
new certificate in their browsers.
Is there any way to make this certificate sticky in Galene, so that no new
certificate is generated on every Galene server restart?
Thank you
KOS
next parent reply other threads:[~2023-12-20 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 12:19 KOS [this message]
2023-12-20 13:57 ` [Galene] " Juliusz Chroboczek
2023-12-20 18:20 ` KOS
2023-12-20 22:22 ` Juliusz Chroboczek
2023-12-20 22:28 ` KOS
2024-01-23 10:24 ` KOS
2024-01-23 14:11 ` Juliusz Chroboczek
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
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Mr.FqoYVgpooJD.yHIGsTlnOJ6@qrp.gr \
--to=sv3ora@qrp.gr \
--cc=galene@lists.galene.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