Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 days ago.
This post was edited and submitted for review 6 days ago and failed to reopen the post:
Original close reason(s) were not resolved
Improve this question
I tried to use SSL configured as in https://ktor.io/docs/ssl.html with self signed SSL Certificate and deploy it to a VPS and it worked,
[enter image description here][1]
now I want to use a real SSL Certificate.
how can I configure a real SSL Certificate to my ktor server?
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 12 months ago.
Improve this question
I could connect my ESP8266 board to my MQTT server over TLS. Everything works fine.
There is only one question (as I'm a beginner with encryption): Should I hard code CA.crt, client.crt and client.key on the board??
As I know, if my certificates expire, I have to purchase another certificate, meaning my boards won't work anymore (I sell them). Can I securely ask server for these files every time?
EDIT:
This question was closed because it was opinion-based. OK, give me an opinion! I have no idea to handle my case. Thanks.
We can't answer this for you, only you know the details how how/where the device will be deployed. This will factor into what is acceptable
What I will say is that it is possible to do Over the Air updates with ESP8266 so you can push code updates that could include updated certificate fingerprints if needed or you can not include an actual CA certificate to verify the broker certificate.
As for client certificates, these don't need to be issued by a public CA so you have full control over their expiry time, so it's perfectly reasonable to set a life longer than the expected life of the device.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
Any idea how to resolve this issue and avoid this alert? I am getting it under Qualys SSL Labs website's SSL test.
You have to upgrade your server software (server and SSL libraries) to a version supporting this fairly new option.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm thinking about using a self signed cert for a staging area of my app. However, this staging area is located on the same server as production, and I'm worried that using a self signed cert may cause the server to be flagged as malicious/suspicious. Should I just go ahead and pay for a real cert?
There is theoretically nothing wrong with a self-signed certificate, but browsers like Chrome will definitely raise a flag. I'd recommend getting a real certificate.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I'm trying to enable https://mysite.com on my Ubuntu 11.04/Apache 2
I followed several guides online, but I still cannot access https://mysite.com
The guides mentioned getting certificates from CA, does that mean I have to register somewhere?
Or, can I simply redirect all https traffic to http?
Yes. You need to get and install an SSL certificate.
The whole point of SSL is that a trusted third party verifies your identity.
You are going to need to read up on SSL or hire someone.
Good luck
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I have many servers which SSL. Now anyone working with SSL and hundereds of servers will know the pain of renwewal and distribution of SSL certificates.
I want to automate this whole process(renewal and distribution).
Is there any open source product that can do this or any perl module that could assist me in doing this?
Thanks