PS:
For those who would get the same thing. (v2.3 since build #239):
1)- Paste the following section in a file
hfs.events that you will put in the folder of
hfs.exe:
Script edited 01-18-2010[connected]
{.set|#log|{.load|stunnel.log|from={.^#stunnel.last.}.}.}
{.set|#stunnel.last|{.filesize|stunnel.log.}.}
{.if|{.^#log.}|{:
{.add to log|.
Stunnel log :
{.^#log.}|Clblue.}
:}.}
[+start]
{.set|#stunnel.last|{.filesize|stunnel.log.}.}[/color]
2)- In file
stunnel.conf of the folder of
stunnel.exe , specify the
path of HFS where the file
stunnel.log will be created.
(Debug = 6 gives a correct result)
; Some debugging stuff useful for troubleshooting
debug = 6
output = C:\path\of\hfs folder\stunnel.log3)- Enjoy
HFS and
Stunnel !
![Smiley :)](/forum/Smileys/default/smiley.gif)
----------------------------------------------------------------------------
Independently, you can add to the section
[https] of
stunnel.conf, the
internal IP of your
PC:
[https]
accept = 0.0.0.0:443
connect = 127.0.0.1:44300
local = 192.168.1.6 *TIMEOUTclose = 0* IP exampleThen you add in HFS:
Menu > Limits > Bans\127.0.0.1;192.168.1.6Then in Adress2name:
Name IP Mask
Local 127.0.0.1
Stunnel 192.168.1.6This will differentiate in the log, the local connections (http), and the distant connections from
Stunnel (https).