A broad SSL recipe?

I personally would start the tiddlywiki-thread as a different user, that only has write access to the xxx/tiddlers directory and no where else in the system

I did change the wiki text quite a bit.
I did try to give it more structure.
I did change the “writer perspective” from “I” to “We” and “The wiki…”
I did add some more points to the “assumptions” about the existing setup and security.

That’s it for the beginning. The “assumptions” points would make good topics for more wikis. Every point can be 1 wiki.

IMO HTTPS doesn’t make a server secure. It only improves security for the communication to and from the server.

SSL Server Test (Powered by Qualys SSL Labs) shows you some info about your https settings. If it doesn’t show an A grade … There is some work to do

1 Like

I have made some quick edits to for better readability. I have not changed any of the actual information presented.

1 Like

Not long after this was posted, it was pointed out to me that the “name/foo” method was not the way to go, instead the best way is to make an A record on the site that hosts it. I intended to fix or ditch this site; got distracted; hiho here I am.

The site needs fixing but I’m too swamped to do a rewrite, hope to do one soon I hope, but in the meantime what would be the best way put in the oosie? Or: if page is probably not getting much traffic anyway, better to just remove it?