From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2] WebUI: print more information on used nameservers
Date: Fri, 15 Sep 2017 17:05:45 +0200 [thread overview]
Message-ID: <23fdbe13-edc9-c532-9022-7f99b7eb22dd@ipfire.org> (raw)
In-Reply-To: <1505421709.2540.9.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
Hi Michael,
On 14.09.2017 22:41, Michael Tremer wrote:
> Hi,
>
> On Tue, 2017-09-12 at 18:26 +0200, Matthias Fischer wrote:
>> Hi Peter,
>>
>> On 12.09.2017 06:38, Peter Müller wrote:
>> ...
>> ...
>> Could someone of these please take a look at this?
>
> You mean moving this to HTTPS? Yes. I have that on my list.
>
> Unfortunately I am still not a huge fan of Let's Encrypt. So anyone in
> favour or against using our own CA?
No. ;-)
> Best,
> -Michael
>
>>
Best,
Matthias
next prev parent reply other threads:[~2017-09-15 15:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 17:58 Peter Müller
2017-09-09 10:37 ` Matthias Fischer
2017-09-12 4:38 ` Peter Müller
2017-09-12 16:26 ` Matthias Fischer
2017-09-14 20:41 ` Michael Tremer
2017-09-15 15:05 ` Matthias Fischer [this message]
2017-09-15 20:26 ` CA and HTTPS usage on *.ipfire.org (was: Re: [PATCH v2] WebUI: print more information on used nameservers) Peter Müller
2017-09-24 22:00 ` Michael Tremer
2017-09-25 15:48 ` Peter Müller
2017-10-25 14:25 ` CA and HTTPS usage on *.ipfire.org Michael Tremer
2017-10-25 20:12 ` Peter Müller
2017-10-26 10:31 ` Michael Tremer
2017-10-26 19:24 ` Peter Müller
2017-10-27 14:44 ` Michael Tremer
2018-01-29 12:14 ` Michael Tremer
2018-01-29 14:17 ` Jeffrey Walton
2017-09-17 7:39 ` [PATCH v2] WebUI: print more information on used nameservers Matthias Fischer
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=23fdbe13-edc9-c532-9022-7f99b7eb22dd@ipfire.org \
--to=matthias.fischer@ipfire.org \
--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