Difference between revisions of "What to Protect"
Jump to navigation
Jump to search
m (7 revisions imported) |
BenKoo>Benkoo |
||
| Line 9: | Line 9: | ||
===Nginx Reverse Proxy=== | ===Nginx Reverse Proxy=== | ||
A common practice to set up website is to use Nginx as a reverse proxy to direct web traffic through an encrypted channel, often called [[https]]. The following page on [[Nginx as Reverse Proxy]] shows how to do it. | A common practice to set up website is to use Nginx as a reverse proxy to direct web traffic through an encrypted channel, often called [[https]]. The following page on [[Nginx as Reverse Proxy]] shows how to do it. | ||
=License Protection= | |||
An article on how to set up licenses can be found here<ref>https://wiki.freephile.org/wiki/Licensing#Licensing_of_Wiki_content</ref>. | |||
=References= | =References= | ||
Revision as of 04:57, 1 May 2021
Data Protection
Login mechanisms
QRCode-based login is popular in the WeChat user community. Open Source QRCode log-in code base can be found here[1][2][3].
Network Protection
Encryption and authentication are some basic network-based security measures. A practical tool for network protection is Reverse Proxy Service.
Nginx Reverse Proxy
A common practice to set up website is to use Nginx as a reverse proxy to direct web traffic through an encrypted channel, often called https. The following page on Nginx as Reverse Proxy shows how to do it.
License Protection
An article on how to set up licenses can be found here[4].