es with this?
> I may even decide to go back to ACME then if things are running ok.
>
> Regards
> Michael Knill
>
> From: Lonnie Abelbeck
> Reply to: AstLinux List
> Date: Thursday, 11 April 2019 at 12:34 am
> To: AstLinux Lis
t; Regards
> Michael Knill
>
> From: Lonnie Abelbeck
> Reply to: AstLinux List
> Date: Thursday, 11 April 2019 at 12:34 am
> To: AstLinux List
> Subject: Re: [Astlinux-users] ACME (Let's Encrypt) Certificates Vs Wildcard
> SSL certificates
>
> Hi Michael,
>
Abelbeck
Reply to: AstLinux List
Date: Thursday, 11 April 2019 at 12:34 am
To: AstLinux List
Subject: Re: [Astlinux-users] ACME (Let's Encrypt) Certificates Vs Wildcard SSL
certificates
Hi Michael,
but the way I see it is that we could just purchase a Wildcard SSL certificate
instead of us
List
Subject: Re: [Astlinux-users] ACME (Let's Encrypt) Certificates Vs Wildcard SSL
certificates
Hi Michael,
but the way I see it is that we could just purchase a Wildcard SSL certificate
instead of using ACME which seems a bit of a hassle.
Am I correct?
IMO, using automatic ACME certs in A
Thanks all.
I might look into the LetsEncrypt wildcard certificates!
Regards
Michael Knill
From: David Kerr
Reply-To: AstLinux List
Date: Thursday, 11 April 2019 at 1:06 am
To: AstLinux List
Subject: Re: [Astlinux-users] ACME (Let's Encrypt) Certificates Vs Wildcard SSL
certifi
> Am 10.04.2019 um 16:36 schrieb David Kerr :
>
> LetsEncrypt supports wildcard certificates and the acme client in AstLinux
> supports it too. There are limitations on which DNS providers it works with
> -- I had to implement it for FreeDNS. I don't think it will be that hard to
> use Lets
LetsEncrypt supports wildcard certificates and the acme client in AstLinux
supports it too. There are limitations on which DNS providers it works
with -- I had to implement it for FreeDNS. I don't think it will be that
hard to use LetsEncrypt.
David
On Wed, Apr 10, 2019 at 6:34 AM Michael Knil
Followup,
One disadvantage of generating local ACME certificates (using DNS validation)
is your DNS provider's credentials are needed on each AstLinux box.
Lonnie
> On Apr 10, 2019, at 9:30 AM, Lonnie Abelbeck
> wrote:
>
> Hi Michael,
>
>> but the way I see it is that we could just purcha
Hi Michael,but the way I see it is that we could just purchase a Wildcard SSL certificate instead of using ACME which seems a bit of a hassle.Am I correct?IMO, using automatic ACME certs in AstLinux is the least-hassle approach ... after the initial setup.The hassle with a 1-2 year Wildcard SSL cer
Hi Group
As I am looking to encourage the use of web portals that we have built into
Astlinux, I am having to consider the use of non self signed certificates to
stop the browser complaining.
The web interface for all our systems is accessible with .ibcaccess.net.
Forgive me for my ignorance but
You could have different subdomains, e.g.
pbx1.ibcaccess.net
pbx2.ibcaccess.net
pbx2.ibcaccess.net
And each could have a unique certificate. But then each Astlinux box would
need to have the login credentials for ibcaccess.net at whatever DNS
service you are using. You might not want that.
Alt
Hi Michael,
Yes, ACME (Let's Encrypt) Certificates is the solution.
You need a DNS provider supported by acme-cleint (acme.sh) that is able to
prove DNS record ownership.
There are two ways to go here:
1) Create an account with a supported DNS service using the services's domain,
such as htt
ACME certificates are supported directly in Astlinux...
https://doc.astlinux-project.org/userdoc:tt_acme_certificates
Each of your Astlinux boxes should have a unique URL (
https://michaelpbx.example.com) and you need access to the registrar where
you keep your DNS record for michaelpbx.example.co
Ok after reading the doco page and Lets Encrypt and ACME Protocol pages, I
realise that I don't really know what I am doing 😊
The Problem:
I am now providing more regular access to the Astlinux Admin interface to
customers and the certificate error is not a good look. You can store the Self
Sig
> Am 22.07.2017 um 16:25 schrieb Lonnie Abelbeck :
>
> Greetings,
>
> Given the recent pre-release, I want to follow-up discussing the addition of
> ACME (Let's Encrypt) certificates.
>
> I must say, when Let's Encrypt was first announced in 2015 I was skeptical
> how useful this would be wit
Greetings,
Given the recent pre-release, I want to follow-up discussing the addition of
ACME (Let's Encrypt) certificates.
I must say, when Let's Encrypt was first announced in 2015 I was skeptical how
useful this would be with AstLinux, and frankly it initially wasn't too
practical since a HT
16 matches
Mail list logo
