Released IMSpector 0.7, pfsense build is needed



  • Released IMSpector 0.7  but pFsense package build is 0.4 older  :-\

    How it make?



  • IMSpector 0.5 is in the latest build of 1.3, but IMSpector is at version 0.7.  Anyway to get a push for this?  I need the gtalk portion of it mainly.



  • Open a bounty?



  • I'm also very much interestet in the newest version of Imspector.

    Can anybody bind the newest version into pfsense? Or make a script wherewith
    we are able to install it over shell?

    I hope mr Ryan Wagoner can make this happen :)
    (i think that he has implemented the last version into pfsense).



  • As long as the new version is not in the ports system it is unlikely that it will be included in pfsense. For the moment imspector for FreeBSD is at version 0.5: http://www.freebsd.org/cgi/ports.cgi?query=imspector&stype=all



  • Hi for all,
    the last version is 0.8 and in the freebsd ports, is 0.5
    have some chance to compile that without ports and put in pfsense.
    Some features, like inject messages into the conversation, that respect privacy laws in some countrys, is very important.
    Have some other changes in the pfsense imspector gui necessary like:
    Loggin rotate
    Export conversation history to other formats like html or pdf.



  • freebe, can you compile it for pfsense?



  • i can make some tbz, but is in freebsd general setup. For pfSense, need upgrade the gui to support this new functions and in php, i'm very novice. If someone understand php and the pfsense framework, in some way, i can help.



  • I would also like to see a bounty for this..



  • thank you freebe.

    I think you should check the tgz file of imspector 0.4 (which is already included in pfsense)

    I think I can modify the php files for version 0.8



  • Please see the bounty post on this.  I've started work on an update.  0.8 is working fine here so far (for IRC at least) - I'll finish it up regardless, but any donations to the cause would be appreciated.

    –Bill



  • Great work bill!

    It seems the latest version of msn does has some kind of security, the chat logs are not being logged with the current imspector version Sad

    edit : Actually it does seem to log, but not using the contact names anymore, it displays weird strings : {90ef587c-b7cb-4110-9b5a-db95dd1c2339} and groupchat. I hope the latest build from Bill solves this problem.



  • New build seems to be broken, atleast on 1.2.3. The gui is messed up (buttons outside the pfsense frame) and the messages (wich were logged with the 0.4 version) doesnt show correctly. I tried reinstalling and removing and installing, no luck.

    The problem is that there two many lines shown in the conversations. You know like

    n1ko: hi
    Fei Tang: hi

    shows up like

    n1ko: hi
    n1ko:
    n1ko:
    n1ko:
    Fei Tang: hi
    Fei Tang:
    Fei Tang:
    Fei Tang:
    Fei Tang:

    There are also totally empty lines (with only timestamp logged). And the spacing seems to be b0rked too or maybe theres two 'lines' on one line. Like "Hi              how are you", even tought it might have been "hi" and "after that how are you"

    EDIT: I was using google chrome before, now I tried with ff3. FF3 shows the buttons etc in their right places but the messages are messed up there too.



  • @n1ko:

    New build seems to be broken, atleast on 1.2.3. The gui is messed up (buttons outside the pfsense frame) and the messages (wich were logged with the 0.4 version) doesnt show correctly. I tried reinstalling and removing and installing, no luck.

    The problem is that there two many lines shown in the conversations. You know like

    n1ko: hi
    Fei Tang: hi

    shows up like

    n1ko: hi
    n1ko:
    n1ko:
    n1ko:
    Fei Tang: hi
    Fei Tang:
    Fei Tang:
    Fei Tang:
    Fei Tang:

    There are also totally empty lines (with only timestamp logged). And the spacing seems to be b0rked too or maybe theres two 'lines' on one line. Like "Hi              how are you", even tought it might have been "hi" and "after that how are you"

    What protocol was this?  IRC is working fine for me.

    @n1ko:

    EDIT: I was using google chrome before, now I tried with ff3. FF3 shows the buttons etc in their right places but the messages are messed up there too.

    I can only test FF3 and Safari - it's too late tonight to test out Safari, this is probably an alignment issue due to adding the category field.

    –Bill



  • MSN and IRC. I only have these two.

    The logging format probably changed in some version because all the new things (logged with 0.8) are just fine. So I guess I just have to live with the old logs being a little bit b0rked :)

    I snooped around some more, like i guessed the problem is with the loggin format:

    OLD: 192.168.2.2:35408,1234243652,0,1,0,n1ko: message here

    NEW: 192.168.2.2:41211,1234250056,0,1,0,,n1ko: new message here

    Theres an second , before the nick. This is the only difference I found.



  • @n1ko:

    MSN and IRC. I only have these two.

    The logging format probably changed in some version because all the new things (logged with 0.8) are just fine. So I guess I just have to live with the old logs being a little bit b0rked :)

    I snooped around some more, like i guessed the problem is with the loggin format:

    OLD: 192.168.2.2:35408,1234243652,0,1,0,n1ko: message here

    NEW: 192.168.2.2:41211,1234250056,0,1,0,,n1ko: new message here

    Theres an second , before the nick. This is the only difference I found.

    Ahh, that's the category field :)  New logs are fine though right?  I'll see if I can change the regexp to support both formats - it's kind of a fast and loose regexp and needs some tightening anyway.

    –Bill



  • Yes, everything new is fine. The log viewer / settings buttons are messed up with chrome but thats only a little annoyance. Firefox works  fine



  • about imspector 0.8:

    how to tune connection to mysql-server?

    i have create user/password on server: imspector/imspector
    then i feel fields in "imspector settings"(server, user etc…)

    imspector was create table "messages" on my server.

    trouble: no one message not inserted to table:( table is empty:(

    anybody know what's happened?

    Thanks!



  • Pleas read the bounty thread on this.

    –Bill



  • Microsoft released a new version of msn recently, imspector fails to work with this version and it's logging unfort :(

    See :

    The groupchat logs are all from the same person/conversation Leaving impsector running for an hour results into a horrible amount of groupchat logs..

    Any idea's if this is the imspector code which needs changing? Or is this related to the pfsense frontend?



  • Can anyone confirm if the previous pfs version (0.4?) is experiencing problems? I had no problems what so ever until I updated the package to 0.8-0.



  • @0tt0:

    Can anyone confirm if the previous pfs version (0.4?) is experiencing problems? I had no problems what so ever until I updated the package to 0.8-0.

    And these problems are….?



  • @AudiAddict:

    Microsoft released a new version of msn recently, imspector fails to work with this version and it's logging unfort :(

    See :

    The groupchat logs are all from the same person/conversation Leaving impsector running for an hour results into a horrible amount of groupchat logs..

    Any idea's if this is the imspector code which needs changing? Or is this related to the pfsense frontend?

    I don't have, use MSN chat, or even known anyone that uses it.  I'll need to see the raw logs from /var/imspector to see if we're parsing something wrong.  I think I saw something about MSN and IMSpector somewhere, but I can't for the life of me find it now - I swear it had something to do with your issue and the problem was that it needed to catch the initial sign in, which is on a different port.

    –Bill



  • Hey Bill,

    I e-mailed the author of imspector for you regarding this issue, see below his feedback :

    We have been using your imspector application and we are very happy with it!!

    The only main problem we are having now is that microsoft recently released a new version of msn which is causing a horrible amount of groupchat logs.

    See screenshot : (see above for screenshot)

    Any idea's if this can be fixed somehow? I expect most people to start upgrading there msn versions soon..

    _Good news: this is fixed in CVS.  You can get a tarball from the daily snapshot directory:

    http://www.imspector.org/downloads/snapshots/

    Give the latest checkout a go._
    I guess they fixed this issue in the latest snapshot?Is this something you can include in the package Bill?

    MSN is used mainly in the netherlands, other protocols and chat programs are barely used here, so I would love to get this working properly with the latest msn version. Thanks in advance for your efforts!



  • Hi good afternoon everyone :)
    I installed version Imspector verio 8 now. But users who use yahoo messenger and msn disconnect after sending messages. I disabled the mysql server (ip 192.168.1.4 - windows mysql) . Same thing they disconnect. How to get rid of this? How to install mysql in pfsense?



  • @jigpe:

    Hi good afternoon everyone :)
    I installed version Imspector verio 8 now. But users who use yahoo messenger and msn disconnect after sending messages. I disabled the mysql server (ip 192.168.1.4 - windows mysql) . Same thing they disconnect. How to get rid of this? How to install mysql in pfsense?

    You be patient, or don't use the package and roll it yourself.

    –Bill



  • @AudiAddict:

    Hey Bill,

    I e-mailed the author of imspector for you regarding this issue, see below his feedback :

    We have been using your imspector application and we are very happy with it!!

    The only main problem we are having now is that microsoft recently released a new version of msn which is causing a horrible amount of groupchat logs.

    See screenshot : (see above for screenshot)

    Any idea's if this can be fixed somehow? I expect most people to start upgrading there msn versions soon..

    _Good news: this is fixed in CVS.  You can get a tarball from the daily snapshot directory:

    http://www.imspector.org/downloads/snapshots/

    Give the latest checkout a go._
    I guess they fixed this issue in the latest snapshot?Is this something you can include in the package Bill?

    MSN is used mainly in the netherlands, other protocols and chat programs are barely used here, so I would love to get this working properly with the latest msn version. Thanks in advance for your efforts!

    Thanks for the legwork, I'll see what I can do today…hopefully I don't need to do too much more to the port to make it work, I'd like to get to the other features. :)

    --Bill



  • @n1ko:

    @0tt0:

    Can anyone confirm if the previous pfs version (0.4?) is experiencing problems? I had no problems what so ever until I updated the package to 0.8-0.

    And these problems are….?

    Have you looked at the screenshots posted…...?



  • @0tt0:

    @n1ko:

    @0tt0:

    Can anyone confirm if the previous pfs version (0.4?) is experiencing problems? I had no problems what so ever until I updated the package to 0.8-0.

    And these problems are….?

    Have you looked at the screenshots posted…...?

    Are you referring to AudiAddicts screenshots?  I don't see any from you.

    –Bill



  • @billm:

    @0tt0:

    @n1ko:

    @0tt0:

    Can anyone confirm if the previous pfs version (0.4?) is experiencing problems? I had no problems what so ever until I updated the package to 0.8-0.

    And these problems are….?

    Have you looked at the screenshots posted…...?

    Are you referring to AudiAddicts screenshots?  I don't see any from you.

    –Bill

    Yes I was. But I'll try to attach 2 pics using the attach feature here.






  • Most of this should be solved in the latest update/snapshot from Imspector Otto.

    Now we wait for bill, hopefully he will be able to update the pfsense imspector package with the latest update from the imspector website.

    No rush btw bill, I'm glad your willing to take some time to fix this!



  • @0tt0:

    Have you looked at the screenshots posted…...?

    Yes I have but since you were referring to a problem that you didnt specify (=you didnt post the shots) and to an problem that was discussed in this very topic only couple posts before (and with an solution/answer from Bill) I tought you had something else.

    @AudiAddict:

    Most of this should be solved in the latest update/snapshot from Imspector Otto.

    Now we wait for bill, hopefully he will be able to update the pfsense imspector package with the latest update from the imspector website.

    No rush btw bill, I'm glad your willing to take some time to fix this!

    You mean old logs will be parsed properly in the new snapshots? Because like discussed on the previous page the problem doesnt occur on new material.



  • @0tt0:

    Have you looked at the screenshots posted…...?

    Yes I have but since you were referring to a problem that you didnt specify (=you didnt post the shots) and to an problem that was discussed in this very topic only couple posts before (and with an solution/answer from Bill) I tought you had something else.

    @AudiAddict:

    Most of this should be solved in the latest update/snapshot from Imspector Otto.

    Now we wait for bill, hopefully he will be able to update the pfsense imspector package with the latest update from the imspector website.

    No rush btw bill, I'm glad your willing to take some time to fix this!

    You mean old logs will be parsed properly in the new snapshots? Because like discussed on the previous page the problem doesnt occur on new material.



  • @n1ko:

    @0tt0:

    Have you looked at the screenshots posted…...?

    Yes I have but since you were referring to a problem that you didnt specify (=you didnt post the shots) and to an problem that was discussed in this very topic only couple posts before (and with an solution/answer from Bill) I tought you had something else.

    @AudiAddict:

    Most of this should be solved in the latest update/snapshot from Imspector Otto.

    Now we wait for bill, hopefully he will be able to update the pfsense imspector package with the latest update from the imspector website.

    No rush btw bill, I'm glad your willing to take some time to fix this!

    You mean old logs will be parsed properly in the new snapshots? Because like discussed on the previous page the problem doesnt occur on new material.

    Audi refers to the MSN issues.  The parsing of old logs is going to take some more work, the regexp that matches the new logs (needed so you don't have stray commas in them), fails to properly match the old logs.  Now that I've seen the output, I'm going to see what I can do to match them both.

    Here's what I'm working on in order:
      Post a minor update tonight that fixes the MySQL logging
      Update the IMSpector binary to the latest snapshot to fix MSN (the commit log says the code was untested, so who knows)
      Fix parsing of old logs if possible (if not, just go to the shell and read the logs yourself, sheesh), new logs are FINE
      Split package up into three (MySQL, PostgreSQL, and plain text logging) as I have zero desire to install 50M of MySQL crap I don't need and won't use
      Add new protocols and options that came with updated IMSpector (this includes message injection)

    –Bill



  • Keep up the great work bill, I have imspector turned off right now, because the current used msn versions in our network seem to spam "groupchat" logs like crazy, thus causing the webinterface to be a complete mess.

    I'm hoping the new update will fix this issue, do you have any idea's if you will be able to include the update/fix before the end of feb?

    Btw, Mysql was working for me on the older version which(before you did the updates) (0,4?). It decided to not use it anymore, I don't want to keep this kind data logged for too long.

    I just want to verify which users use msn and talk to them about it if needed. (msn or chat software may not be used in our network)



  • Starting a new topic to track updates to this package - locking this one.

    –Bill


Locked