I just tried the Windows installer, it installed fine, but it won't run from the exes. I can run it from the console fine. There are no error messages, it just dies after "config logger}"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I finally captured the error message. It was there, but the console closes so quickly you can't see it. IT went away when I used a default cfg so I started playing with options and discoverd it was XMLRPC, then I was also lucky enough to capture the error:
Can't locate XMLRPC/Transport/HTTP.pm in @INC (@INC contains: d:\progra~1\popfile d:/Program Files/POPFile/lib .) at d:\progra~1\popfile/UI/XMPRPC.pm line 104.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The security upgrade worked OK for me on an XMLRPC-free installation. So I also tried it after installing XMLRPC.
I made a clean install of 0.21.1a, letting the installer create the 4 default buckets, shut it down and used the Add XMLRPC installer (v0.0.4) to add the XMLRPC components. Then I shut that down and used the new 0.21.2 installer to install the security fix and found that POPFile started up without any complaints.
>> It was there, but the console closes so quickly you can't see it. <<
This is just the sort of situation the new Message Capture utility was designed for. All you do is run msgcapture.exe and it will use the current POPFILE_ROOT and POPFILE_USER environment variables to start POPFile and capture the output. I sabotaged my working installation and then ran msgcapture.exe to get this report (it does not matter where msgcapture.exe is stored):
------------------------------------------------------------
POPFile Message Capture Utility v0.0.53
------------------------------------------------------------
POPFILE_ROOT = c:\progra~1\clean0~1
POPFILE_USER = c:\windows\applic~1\popfile\clean0~1
Using 'popfileif.exe' to run POPFile
------------------------------------------------------------
(report started 03-Aug-2004 @ 10:34:06)
------------------------------------------------------------
It takes longer to describe what to do than it does to actually do it (if you use Win9x a small batch file is needed to set the environment variables and start msgcapture.exe so it takes a little longer to set this up).
Notice that my error message refers to line 108 and Joseph's refers to line 104. I tried the earlier versions of the add-on installer and found that v0.0.2 uses line 104 in the error message.
I uninstalled and started again: 0.21.1a plus "Add XMLRPC" v0.0.2 plus 0.21.2 and it worked OK.
I've recently noticed that sometimes the Perl error messages use LFN format instead of SFN - at the moment I don't know why this happens. Joseph's error message contains both LFN and SFN references which might be significant.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Folks,
I've made v0.21.2 release of cross platform and Windows and placed them here:
http://popfile.sf.net/popfile-0.21.2-windows.zip
http://popfile.sf.net/popfile-0.21.2.zip
which contain the bug fix for the security problem that Sam found.
John.
PS.
How to test if the bug is gone.
Put a GIF file with the extension ".gif" somewhere on your disk and then go to the POPFile UI like this:
http://127.0.0.1:8080/full_path_to_file
e.g. imagine the file is in C:\test.gif then go to
http://127.0.0.1:8080/c:\test.gif
or imagine the file is in /home/test/test.gif then go to
http://127.0.0.1:8080/home/test/test.gif
In v0.21.1 you should get the gif, in v0.21.2 you'll get a 404.
John.
I just tried the Windows installer, it installed fine, but it won't run from the exes. I can run it from the console fine. There are no error messages, it just dies after "config logger}"
That was an upgrade only. I haven't tried a clean install.
I finally captured the error message. It was there, but the console closes so quickly you can't see it. IT went away when I used a default cfg so I started playing with options and discoverd it was XMLRPC, then I was also lucky enough to capture the error:
Can't locate XMLRPC/Transport/HTTP.pm in @INC (@INC contains: d:\progra~1\popfile d:/Program Files/POPFile/lib .) at d:\progra~1\popfile/UI/XMPRPC.pm line 104.
The security upgrade worked OK for me on an XMLRPC-free installation. So I also tried it after installing XMLRPC.
I made a clean install of 0.21.1a, letting the installer create the 4 default buckets, shut it down and used the Add XMLRPC installer (v0.0.4) to add the XMLRPC components. Then I shut that down and used the new 0.21.2 installer to install the security fix and found that POPFile started up without any complaints.
>> It was there, but the console closes so quickly you can't see it. <<
This is just the sort of situation the new Message Capture utility was designed for. All you do is run msgcapture.exe and it will use the current POPFILE_ROOT and POPFILE_USER environment variables to start POPFile and capture the output. I sabotaged my working installation and then ran msgcapture.exe to get this report (it does not matter where msgcapture.exe is stored):
------------------------------------------------------------
POPFile Message Capture Utility v0.0.53
------------------------------------------------------------
POPFILE_ROOT = c:\progra~1\clean0~1
POPFILE_USER = c:\windows\applic~1\popfile\clean0~1
Using 'popfileif.exe' to run POPFile
------------------------------------------------------------
(report started 03-Aug-2004 @ 10:34:06)
------------------------------------------------------------
POPFile Engine loading
Loading...
{core: windows}
{core: mq logger config}
{classifier: bayes wordmangle}
{interface: html xmlrpc}
{proxy: pop3}
POPFile Engine v0.21.2 starting
Initializing...
{core: mq windows config logger}
{interface: html xmlrpc}
{classifier: wordmangle bayes}
{proxy: pop3}
Starting...
{core: mq windows config logger}
{interface: htmlCan't locate XMLRPC/Transport/HTTP.pm in @INC (@INC contains: C:\PROGRAM FILES\CLEAN0211 C:/Program Files/clean0211/lib .) at C:\PROGRAM FILES\CLEAN0211/UI/XMLRPC.pm line 108.
------------------------------------------------------------
Status code: 0
------------------------------------------------------------
(report finished 03-Aug-2004 @ 10:34:08)
------------------------------------------------------------
It takes longer to describe what to do than it does to actually do it (if you use Win9x a small batch file is needed to set the environment variables and start msgcapture.exe so it takes a little longer to set this up).
Notice that my error message refers to line 108 and Joseph's refers to line 104. I tried the earlier versions of the add-on installer and found that v0.0.2 uses line 104 in the error message.
I uninstalled and started again: 0.21.1a plus "Add XMLRPC" v0.0.2 plus 0.21.2 and it worked OK.
I've recently noticed that sometimes the Perl error messages use LFN format instead of SFN - at the moment I don't know why this happens. Joseph's error message contains both LFN and SFN references which might be significant.
Brian