MyCrypNet development is currently suspended.Skip to content
The free and scalable technologies that we use for MyCrypNet service allows multiple configurations to meet different needs. The configuration we offer on each tutorial page is the one we consider the most universal, which will work in almost all situations users come accross. However, the service allows other alternative configurations of which we will describe advantages and disadvantages.
The default configuration
On each of our MyCrypNet installation tutorial pages, there’s a download configuration file called “MyCrypNet.ovpn” or “MyCrypNet.conf” depending on the platform you chose.
To access the installation tutorials:
The settings we include in these files contain our security informations, allowing the transfer of your data safely, but also the addresses of our servers that your device will contact to establish your MyCrypNet private secure network.
Our default configuration uses the same settings as a connection to a secure HTTPS Internet website (TCP port 443). We have chosen these settings so that the connection to your MyCrypNet network is possible in most real-life situations. Of course, HTTPS traffic is very rarely filtered. Our MyCrypNet service uses the same settings, so the connection will mostly run smoothly.
We allow the most people to access our service, in the most diverse situations.
When your MyCrypNet access is configured to work with two factors authentication, you must use the specific configuration file, as specified in the article “How to set the 2 factor authentication on MyCrypNet“.
If you want to see technical informations for MyCrypNet, take a look here.
Algorithms chosen for the websites
SSL certificate signed by Let’s Encrypt.
Activated and preloaded HSTS.
Keys Exchange: Diffie-Hellman
- default-src: self, *.limawi.io
- script-src: self, unsafe-inline, unsafe-eval, *.limawi.io
- style-src: self, unsafe-inline, *.limawi.io
- child-src: self, *.limawi.io
- frame-ancestors: none