Ændringer

480 bytes tilføjet ,  14. sep 2016, 14:38
ingen ændringskommentar
Linje 7: Linje 7:  
=== Hosting Providers ===
 
=== Hosting Providers ===
 
Internet provider [http://www.methfessel-computers.de/produkte/ssl/ Methfessel Computers,Wiesbaden] is used as an example.<p>
 
Internet provider [http://www.methfessel-computers.de/produkte/ssl/ Methfessel Computers,Wiesbaden] is used as an example.<p>
The (currently recommended) hosting provider [https://www.simplyhosting.net/index.php Simply Hosting] include SSL by default, for no extra cost. (As at 15 Sep 2016) Anyone with them should be able to see their secure site by simply changing the address in the address bar to https. To get your users to enter your secure address site by default you will need to get redirection from your http address to your https address put in place. If you ask them nicely, Simply Hosting may do this for you for free. Only time will tell whether Simply Hosting will put in place a policy of redirecting all their TNG sites to https by default or not. So if you are with Simply Hosting you may not have to do anything and it will eventually happen automatically free of charge and you may go directly to the [[#Trouble.2FProblems_with_TNG_and_SSL|Trouble/Problems section]]
+
The (currently recommended) hosting provider [https://www.simplyhosting.net/index.php Simply Hosting] include SSL by default, for no extra cost. (As at 15 Sep 2016) Anyone with them should be able to see their secure site by simply changing the address in the address bar to https. To get your users to enter your secure address site by default you will need to get a redirection from your http address to your https address put in place. If you ask them nicely, Simply Hosting may do this for you for free. Only time will tell whether Simply Hosting will put in place a policy of redirecting all their TNG sites to https by default or not. So if you are with Simply Hosting you may not have to do anything and it will eventually happen automatically free of charge and you may go directly to the [[#Trouble.2FProblems_with_TNG_and_SSL|Trouble/Problems section]]
    
=== SSL und IP ===
 
=== SSL und IP ===
Linje 73: Linje 73:  
* The TNG [[Captcha Mod]] provided by Roger Moffat that uses Google reCaptcha will not be displayed. So you will need to use a different Captcha mod (e.g. of Rick Bisbee)<br />
 
* The TNG [[Captcha Mod]] provided by Roger Moffat that uses Google reCaptcha will not be displayed. So you will need to use a different Captcha mod (e.g. of Rick Bisbee)<br />
 
* Other Google-scripts (Google Maps) running over non-secured connections to Google servers. With Google addresses one can modify the URL to use HTTPS, so that the security warning are no longer displayed. - After all, with TNG, one  would not want to do without Google maps.
 
* Other Google-scripts (Google Maps) running over non-secured connections to Google servers. With Google addresses one can modify the URL to use HTTPS, so that the security warning are no longer displayed. - After all, with TNG, one  would not want to do without Google maps.
<p>
+
 
 
Update (15 Sep 2016)- The basic TNG installations from version 10 have no known insecure content and should not generate any browser security messages. The only issues that you may encounter are due to any modifications and/or customisations that have been added to the basic TNG package. Some of the more common types of insecure content are listed below
 
Update (15 Sep 2016)- The basic TNG installations from version 10 have no known insecure content and should not generate any browser security messages. The only issues that you may encounter are due to any modifications and/or customisations that have been added to the basic TNG package. Some of the more common types of insecure content are listed below
   Linje 109: Linje 109:  
The map display, which is integrated in TNG, load the needed scripts fit to http or https. Only if additional or separate pages are installed with maps from Google, which recharge the API scripts separately, the API link to https must be changed if necessary.
 
The map display, which is integrated in TNG, load the needed scripts fit to http or https. Only if additional or separate pages are installed with maps from Google, which recharge the API scripts separately, the API link to https must be changed if necessary.
    +
*Insecure Images and Scripts
 +
Insecure images and scripts will need to be sourced from a secure (https) source or removed from customisations and modifications. In many cases this will only involve changing the source address from http to https. Otherwise you will need to get the secure version of the source material, This may require contacting the author of the content.
 +
 +
*Mods
 +
If a mod is found that has SSL issues, the Mod Developer would be person to contact for resolution.
    
[[Category:Security]]
 
[[Category:Security]]
'''Experienced'''
51

redigeringer