First, I would like to apologize for those of you who test the sHFS confmakr v0.25
and end up with an error 0 or error -1, it was a basic coding error, it's now gone
Download stats about v0.25 gives 12 downloads for the 32 bits version and 3 for the 64 bits, also 4 peoples find interest in downloading source files.
I've got time part
Well, this release is late, because I was fighting against wind mills, in others words, I tried to implement some functionalities impossibles to achieve with AutoIt... So, once discovered, I re-oriented my walk to present you this... sorry for the long changelog...
sHFS confmakr v0.45 ERWG
correction of bugs introduced with v0.25 :
- local network in a HFS ban rule must be network.* (ie : 192.168.1.*), the base routing address (192.168.1.0) do not work properly.
- Resolve the bug stopping confmakr.exe from running if your local IP was the last one.
- Resolve the wrong parsing of the unban line when local network allowed on HTTP.
more functionality :
- add facultative hfs.events lines :
* launch Stunnel with HFS
* quit Stunnel with HFS
* del stunnel.log on quit
- remove SHFS.bat (as it becomes useless with changes up there), change the shortcut made with the button (now point to hfs.exe),
- add easy and advanced mode, easy mode automaticaly using pre defined options (switching between mode keep easy mode's visibles parameters)
- remove the scheme thing as I add a probe port button ( \o/ ), with error handling on listening (wrong IP, wrong port, port in use), and to connect to the listening port (unreachable, timeout, and all others as I link the error code to the windows error page).
- the "get my ip" button now check on avva.3ka.fr, alternative stays on whatsmyip.com
- add stunnel log level adjustment, and no stunnel log checkbox.
- add possibility to watch configurations files maded.
- add possibility to wash unnecessary files.
less schism :
- add fields characters limits, according to RFC-3280 (http://www.ietf.org/rfc/rfc3280.txt).
- insert blank lines between key and certificate, as said in Stunnel documentation.
- correct the way Certificate CN was handled with HFS custom-ip. Now, it asks to add the port to HFS's URL bar if it's determined as necessary, if you cancel you'll get exactly what was written in the domain field.
- re-arrange GUI :)
need to be tested more widely before certifying :
- I think I handle the x64/x86 problem, only one version for all Windows systems :)
- also in the same vein, searching more deeply into VC++ redist and watching dlls used by openssl.exe, I think I found all necessary dlls. \o/
That leads to a real portable version ! (But only leads not reaching, for now :)
Well I hope so, and count on all of you to tell me if I'm wrong
This release change some basics functions, I'll edit the first and second post to reflect this (screenshots, folders, needs...)
But as this version seems (at least ^^) to be independant of the Windows OS that runs it, there is no urge :p
In the meantime, the major thing to know is that I isolate the VC++ dlls
, and discover with pleasure that they were compatibles with 64 bits versions of Windows (Vista & XP, I don't test Seven for now). I don't know what wasn't right in the firsts releases for me to think I need to make à 64 and 32 bits versions :/
But well, it seems to be resolved, and I thank I to try it again, without another throw at it, I still be compiling in 64 & 32 bits nomade apps perhaps this time
These improves justify it's name part WG
The second real change is the easy/advanced mode switch
, there are still some bugs, but they concern the guys (and girls) that will search to make my GUI crash, as it concerns the advanced/easy mode switch after
having created the configurations files (this is not the normal way of using my GUI, as when files are created you just eventually create a shortcut and quit the GUI)
Anyway, they won't be here anymore in the next release.The third improvement concerns the test phase.
The "Get my IP
" button now points to one of my server, and assure you it will respond because there is no check, it only returns your public IP. The "Probe port
" button also link to one of my server and just try to connect to the port given.
The scheme is as this :
- The GUI tries to open the port in TCP in listening mode, if not possible it informs you.
- If possible it sends a request to my server with the port number.
- my server reads the port, and uses the IP that makes the call to respond.
- it just does a PHP TCPconnect, with some errors handling.
- it sends the result to the requesting IP, after 10 seconds of trying to connect, with the error code if I didn't handle it (there are too many...)
- GUI shows the server answer and close the port.
Well, that's the majors things about this release, others are in the versions infos in the quote.For those who will want to test this one, I have to inform you of an error you could fall on :
I found that sometimes, an error popup, but without crashing the GUI, still didn't found the sourcebut I have some clues..., also, if you change mode after having created the conf files, you'll have some visuals incoherences in the GUI, because of tab pos, this won't break the config files creation, it's just visually messy.
To summarize, this version won't be tolerant after configurations files are created, I still don't resign to lock the mode switch after configuration maded, I'm on it, and I'll find what's wrong for the next release. In any case, don't worry, it's not an important error, as all configurations files will be created/modified before, and your sHFS
server will work.
These bugs justify it's name part ER
I've got no time part
Well, just download the archive, eventually check the MD5, then decompress the archive.
You'll be with a sHFS v0.45 ERWG
folder, open it.
- Fill in your public IP or Domain name, a free (and redirected if behind a router) port to listen on, and click the large button at the bottom.
or - You also can click on the upper right button to switch to advanced mode, wich will show you the default values that I use in easy mode, and leave you free of modifying any of them.
Normally, you'll end up with a functionnal HTTP server wrapped HTTPS via Stunnel.
Connection info to give to your visitors will be visible in HFS URL's bar.
So, let's try it
PS : All files linked in the first post for convenience @TCube : I self would appreciate any help with my own english translations, because I know I'm far from a good translator