Hi,
Have you considered using letsencrypt for SSL certificates?
It provides the ability to renew certificates automatically (using a
cron job for example), and it's free so when it is set up, there is
nothing else to do excepting being sure letsencrypt tools are up to date.
And every NVAccess and NVDA related websites could provide HTTPS.
Best regards,
Patrick
Le 15/01/2017 à 06:45, James Teh a écrit :
addons.nvda-project.org <http://addons.nvda-project.org> doesn't support
SSL at all. When you access it via https, the server is falling back to
nvaccess.org <http://nvaccess.org>, so the certificate will show as
invalid. I'm doing some server upgrades in the next few weeks and will
hopefully move everything to https in the process. Thanks for the
reminder that I need to include the addons site in this work.
Btw, while this used to be hosted on Mesar's server, it's all hosted by
NV Access now, so I configured the server and manage everything server
related.
On Sun, Jan 15, 2017 at 11:56 AM, Joseph Lee <joseph.lee22590@xxxxxxxxx
<mailto:joseph.lee22590@xxxxxxxxx>> wrote:
Hi,____
__ __
When I try to go to add-ons website via HTTPS (URL:
https://addons.nvda-project.org ;<https://addons.nvda-project.org>),
I get certificate error and unsecure connection errors in IE and FF,
respectively. This might be due to domains, or something Mesar did
when he configured the current add-ons website. I recommend that we
try to use HTTPS, both for the website as well as when accessing a
future add-ons database via add-on update client. Thanks.____
Cheers,____
Joseph____
Attachment:
0x70E87597.asc
Description: application/pgp-keys
Attachment:
signature.asc
Description: OpenPGP digital signature
