About the virus, perhaps changing the name makes comodo tilt, but it doesn't change the sha1/256 signature of the file, I mean that the actual 'my file' and the actual rejetto's #266 are the same, even with a different name
***
Thanks
About your suggestions, Im not sure I understood totally what you meaned, or its purpose, but let's try to answer. Feel free to correct me if I misunderstood
have an option for [default] values: port 80 for HFS and 443/80 for sTunnel
I won't default HFS connect port to 80, it is the default HTTP port, I can't see a reason to assign this specific port between Stunnel and HFS.
443 is already the default listening port.
But, you can easily switch to advanced mode (icon in the top right corner of sHFS confmakr) and set it yourself if it's what you need
then an option for custom router values: incoming port/private-forwarded port (the one the software actually listens on behind the firewall); example: HFS 80/?? or vice versa and sTunnel is ??/?? with the default port of 443 forwarding to the private ACCEPT port of sTunnel which then links to the private CONNECT port that the HFS is actually using.
This doesn't concern me as far as I know ^^
You must set a unique port between HFS and Stunnel, the only way to do so is to switch to advanced mode, if you don't, port 44300 is used, I use it only because it's usually a free port. you can't set a joker.
Now, set HFS-Stunnel link to port 80, Stunnel listening port to 443, and set your router to follow to Stunnel port 443 all requests made on port '??' you have choosen.
if you have a dynamic dns service... you can change the default port for regular web but you cant change it for web SSL which is 443
To me you're mismatching, your dynamic DNS service has to redirect requests to Stunnel listening port on your machine, it's on you to configure correctly your Dynamic DNS service.
Also, https adresses default to 443, it's useless to add port number.
On another hand, I won't do something about dynamic DNS services because each one has it's own way and application to manage its functions. This is why I just add a check box, that will indicate the fact to HFS, but you'll still have to configure it manually.
So in your example,
https://dynamic.domain/hfs_stuffs/ have to redirect to
https://your.computer/hfs_stuffs/, then Stunnel will take the request as https is on 443 port.
if you router redirect ?? port to 443 on your computer, just make your dynamic dns provider redirect to ?? on your router's IP.
... the one used for your configurator shows the SSL traffic in sTunnel. but the web broswer doesnt recognize the certificate/site as SSL enabled, even though the address is changed to https://??.??
SSL traffic showed in Stunnel can be modified with confmakr, again in advanced mode. You'll have to reduce the log level.
There is no way you'll self-make a certificate which will be approved automatically, I leave you with google to find out why
there is also a more effective certificate generation string for openSSL...
Yeah ?
Can you show me, please ?
