The NikonGear Office > Site Issues

HTTPS Installation Is Underway

<< < (2/3) > >>

PeterN:
I got this message when I entered Nikongear.net plus https in front:

"This website may be impersonating “Nikongear.net” to steal your personal or financial information. You should go back to the previous page.
Safari warns you when a website has a certificate that is not valid. This may happen if the website is misconfigured or an attacker has compromised your connection"

I did not add /revival to the address.

Ann:
The warning which Peter got from Safari is the kind of thing which will frighten people away from a wb site so it is good that you are getting NikonGear certified.

Unfortunately I had no SMF Team to help me so I had to manually re-code everything on my Site myself and it was quite time-consuming!
I do (sort of!) know how to write a Script but it usually takes several attempts before it works and I didn't try doing that in this case.

Andrea B.:
Update: The automated installation of the SSL Certificate failed. So we are now initiating a manual installation which requires a certain kind of email validation of the domain name. Birna will be setting up the validation mailbox when she returns from her current trip.

Funny thing is, over on UVP the entire SSL order and installation took literally about 15 minutes. I've no idea why it's different for NG! But we soldier onwards.....

Akira:
Andrea, I tried to log in the UVP for the first time after it had been secure, but in vain.  I don't think I forgot my password, but the password recovery procedure failed as well.  :(  Apparently, my registered email address didn't work.

I hope the same thing would not happen to NG...

Seapy:
Simple Machines may be their name but programming at this level is NEVER simple!

Many thanks for the efforts and realisation that the forum needs to upgrade to the HTTPS protocol, I had been considering mentioning it.  Since upgrading to Mojave I have realised operating system security is becoming even tighter.  No doubt eventually all good browsers will reject insecure sites, maybe not even 'see' them.

We upgraded the Nikon DSLR forum to HTTPS some months ago, we were fortunate to have a member who is a retired programmer, we were contemplating moving to different software because of the complexity of the upgrade.  Chris managed to rescript and re-code as required to achieve the HTTPS certification.  This was his comment as work proceeded:

"The Ultra(bb) code is such a tangle it has taken me nearly 2 years to even start to understand it - there is a mix of html in the PHP files, some php is object oriented some isn't, some style is in the css, some is inline, some is even hidden inline in html within php!!!

I always comment the files - even if only to understand what I am doing one minute to the next!!"

Upgrading existing software is rarely straightforward.

I had to update my voting registration recently, I entered the URL carefully into the search box, it took me straight to an insecure site, full of links to unrelated sites, possibly containing booby traps... Repeatedly. (Somehow the www. .com url changed to ww1. .com).  In the end I visited the Town Hall site and used their link which took me to the secure Voting Register pages. No matter how careful you are you have to be alert for the bad boys.  If Safari hadn't flagged the site as insecure I might not have noticed.

Navigation

[0] Message Index

[#] Next page

[*] Previous page