As the official server administrator(s) of proxmark.org did not response to this
Well, you are not the official server administrator. You are very close to it! But if you would be the administrator, you would have root access to the server. And with that you could setup HTTPS very easily.
but neither 0xFFFF nor I have server access to the site. We have FTP access.
Within this discussion I was told "Roel" has the server access. And we did not here from him here.
]]>As the official server administrator(s) of proxmark.org did not response to this, user gator96100 was kind enough to provide a HTTPS proxy service. Now you can use this forum and other resources of proxmark.org at:
* https://www.proxmark.eu/
* https://www.proxmark3.org/
Please don't mistake the HTTPS proxy by gator96100 with native HTTPS support by the proxmark.org web server. Using these URLs will route your traffic to gator96100's server in an encrypted fashion and then in plain text to the proxmark.org server. However, this is way better than nothing. Especially if you are in a public WiFi! And I personally trust gator96100 anyways.
Have fun & thank you gator96100!
]]>Personally me using a DynaDot service and strongly recommend it.
At the moment you have two wariants:
1. You can order an SSL for your Site & FluxBB - only $16.99/yr
2. You can transfer your proxmark.org domain and each 3 month obtain a new SSL certificate for free.
There is cupon for the $5 for your certificate: 617T8n6y9N8o726Z
About transfer data to other forums, you can find a lot of scripts to do that's.
]]>However I'm still not giving up hope here. One of these days it will happen. I'm sure of it. If I get better access I know whom to contact who will sort this out in a jiffy
]]>Well, not much to discuss here.
* The server configuration is outdated.
* We need full access to the webserver config to fix it.
* We need full access to the server to use letsencrypt
* We don't have full access. Roel does.
* Reaching out to Roel was tried may times and never worked
Too bad... ¯\_(ツ)_/¯
]]>So we'd need to understand what's causing that redirect- if it's the web server configuration then, unfortunately, there's not much we can do unless Roel removes the redirect to this new URL and redirects https://www.proxmark.org back to this site.
It is quite simple to understand what is happening here. The server that hosts proxmark.org is also hosting swetika.nl. The webserver is configured to redirect any https traffic to https://www.swetika.nl , probably to redirect from https://swetika.nl to https://www.swetika.nl.
That https://www.proxmark.org/ even works is just a side effect of an improper configuration.
yeah, we don't have much access too high up. A bit further than .html/.php like user level. Not more.
Darn. I guess Roel also configured HTTPS connections to redirect to some other site (https://www.swetika.nl/) because that's where I get redirected to when I attempt to navigate here using https.
So we'd need to understand what's causing that redirect- if it's the web server configuration then, unfortunately, there's not much we can do unless Roel removes the redirect to this new URL and redirects https://www.proxmark.org back to this site.
]]>They do have FTP access to the site, but I am not sure if they have access to the configuration file. The configuration file of the webserver is usually in a different folder than the site contents (.html/.php files) and most of the time you only have FTP access to the site contents and not the configuration file.
That's what I'm worried about- that stuff's usually almost certainly requires additional permissions to read/write to the web server config directories. At least with Let's Encrypt you can specify where the certs are saved and as long as you reference them properly in the web server config you should be good.
I guess let's see what they have to say and go from there.
]]>I was thinking iceman/0xFFFF had administrative download/upload FTP access. Idea is that they download the appropriate web config file according to the web server documentation, edit it to include the paths to the SSL certificates, and upload it back onto the box, over-writing the previous config.
They do have FTP access to the site, but I am not sure if they have access to the configuration file. The configuration file of the webserver is usually in a different folder than the site contents (.html/.php files) and most of the time you only have FTP access to the site contents and not the configuration file.
]]>I am not familiar with Let’s Encrypts manual mode, but a cron job on a maschine with shell access that renews the certificate for a remote server with ftp access should work.
I can definitely put some commands and a cron job idea together if this is the route we'd like to take.
This would require access to the configuration file and I am not sure who has access to it.
I was thinking iceman/0xFFFF had administrative download/upload FTP access. Idea is that they download the appropriate web config file according to the web server documentation, edit it to include the paths to the SSL certificates, and upload it back onto the box, over-writing the previous config.
]]>Super janky idea- can the cert be renewed locally and then remotely copied via FTP? Someone would just need to set up a Cron Job that runs the renewal command every three months and then uploads the new certificate via FTP into the proper place.
I am not familiar with Let’s Encrypts manual mode, but a cron job on a maschine with shell access that renews the certificate for a remote server with ftp access should work.
Regarding webserver configuration, not sure what web server this site is running on but it should be possible to clone the current webserver config, manually add in the SSL cert path, and upload the new config and SSL certs?
This would require access to the configuration file and I am not sure who has access to it.
]]>