Website security

[Jarhead0331]

P.S. In fact now that I think aboutit sadly, their are probably records right here of people that no longer even exist. I wonder if any kids would do a search for their ancestors writings in places like this or if anybody will for my posts once I am gone.... ok, now I have gone completely wierd. Backup the internet, we may have degrees on the study of old communities in places like this some day when computers become good enough to discover patterns from internet periods of time, like prehistoric periods of time.

Aside from the social aspects of the forum and the value all of that discourse brings, the point you raise is really another aspect to the priceless nature of the site. We have ten years of data here and it would be terrible if something happened and...all those moments were lost to time...like tears in the rain. 

[Gusington]

^Are you displaying...emotion? I do not understand.

There is definitely data/info here from people who no longer exist. Our old friends Bismarck and Mr. Bigglesworth come to mind, amongst others.

Am I understanding the info above to mean that if our security certificates are updated that will help the security warning issue somewhat?

[Jarhead0331]

Am I understanding the info above to mean that if our security certificates are updated that will help the security warning issue somewhat?

I don't think that is correct. I wish it was that simple. I think Grim's initial post explained it in terms I can somewhat understand. Basically, the main page is secure, but it uses other pages, particularly related to style and format, that are not, and as a result of the mismatch, on certain browsers, the forum won't load the style pages that are not secure and so it displays all FUBAR.

In order to correct it, we need to go to each of those unsecured elements within the back-end and reconfigure them.

[Gusington]

Ok, got it

[Grim.Reaper]

Am I understanding the info above to mean that if our security certificates are updated that will help the security warning issue somewhat?

I don't think that is correct. I wish it was that simple. I think Grim's initial post explained it in terms I can somewhat understand. Basically, the main page is secure, but it uses other pages, particularly related to style and format, that are not, and as a result of the mismatch, on certain browsers, the forum won't load the style pages that are not secure and so it displays all FUBAR.

In order to correct it, we need to go to each of those unsecured elements within the back-end and reconfigure them.

That is basically it.   Although I have done web development, never have supported a forum site like this so I am not sure how the change would be made.  It could be as simple to find the page/links that reference http and change to https.  Or as you mentioned a config setting somewhere, not sure.  Completely understand it could open a can of worms if done incorrectly so understandable in using caution to make any changes.