https certificate installation issues on Amcrest DVR

Have some questions or having issues with your IP Camera(s), Post them here for the mods and other users to assist you with.
Post Reply
jfriend00
Posts: 14
Joined: Fri Nov 11, 2016 11:22 am

https certificate installation issues on Amcrest DVR

Post by jfriend00 »

I'd like to install an SSL certificate from Let's Encrypt on my Amcrest 1080P HD-CVI DVR. The advantage of using a Let's Encrypt certificate is that it uses a certificate authority that is already trusted by modern browsers so https will "just work" without having to download something into each browser.

Right now I've got at least two obstacles to using such a certificate.

1. How to prove to Let's Encrypt that I control the ddns domain that I'm requesting the certificate for? Their usual method for doing that is described here and none of those sound like something we can do with an Amcrest DVR.

2. How to get the certificate onto the DVR and in the right place where the DVR would use it for the https connection?

So, is there any way to use an https certificate other than the one that the Amcrest DVR can generate for you?
plusfour
Posts: 113
Joined: Tue Mar 06, 2018 4:04 am

Re: https certificate installation issues on Amcrest DVR

Post by plusfour »

jfriend00 wrote:I'd like to install an SSL certificate from Let's Encrypt on my Amcrest 1080P HD-CVI DVR. The advantage of using a Let's Encrypt certificate is that it uses a certificate authority that is already trusted by modern browsers so https will "just work" without having to download something into each browser.
The protocol that Let's Encrypt uses was designed for use with public web servers and not much else. It's unlikely you'll get it working with any kind of IoT device like the NVR, unless the NVR is both running a large amount of special software that implements LE's ACME protocol and it has a publicly visible, accessible interface with an associated DNS name.

As I said, it's designed for public web servers, not things like the NVR. For browsers, there's no solution to this problem, in fact it's going to get worse over time as they make it harder and harder to use SSL without involving a public/commercial CA.
Post Reply