Menu
▾
▴
imspector-users — IMSpector users mailing list
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(11) |
Feb
(20) |
Mar
(5) |
Apr
(8) |
May
(7) |
Jun
(4) |
Jul
(2) |
Aug
(9) |
Sep
(2) |
Oct
(3) |
Nov
(4) |
Dec
(2) |
| 2008 |
Jan
(12) |
Feb
(18) |
Mar
(5) |
Apr
(10) |
May
(3) |
Jun
(8) |
Jul
(19) |
Aug
(5) |
Sep
(37) |
Oct
(14) |
Nov
(7) |
Dec
|
| 2009 |
Jan
(3) |
Feb
(14) |
Mar
(13) |
Apr
(5) |
May
(10) |
Jun
(2) |
Jul
(31) |
Aug
(3) |
Sep
(5) |
Oct
|
Nov
(6) |
Dec
|
| 2010 |
Jan
(14) |
Feb
(12) |
Mar
(18) |
Apr
(1) |
May
(2) |
Jun
(1) |
Jul
(3) |
Aug
|
Sep
|
Oct
(11) |
Nov
(3) |
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(1) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: DB <db...@m-...> - 2013-05-10 11:10:08
|
The regular imspector package did not work in Pfsense2, but imspector-dev does and it's great. All seems to work, except that it does not log IMs from my users who are running Pidgin on linux (Ubuntu 12.04 and 13.04). I see their replies to users who are running Yahoo messsenger on Windows. I have Pidgin users on Windows and their IMs are logged. Seems that only those running Pidgin under linux are missing from the log. Any thoughts? |
|
From: Burak Y. <bu...@gm...> - 2011-12-20 15:24:37
|
Hello, Imspector is a nice tool. I use it on a gateway machine. It works nice when a user on the local network use MSN with a client outsite of the network. But when both of the clients are on the local network, it took about 20 seconds to get answers. Sistem is Ubuntu Lucid 10.04, 443 port is open, 1863 is redirected. I use shorewall to redirect the port. Would you please help me to solve the problem ? |
|
From: Alexis M. <ale...@gm...> - 2011-11-25 12:13:59
|
Lo tengo funcionando en 31 servidores distintos, ubuntu y centos. Bajé el tgz, compilé e instalé, nada más.. sin ningún tipo de GUI. Y la verdad que me funciona todo, el bloqueo, los logs en mysql, etc etc. El 25 de noviembre de 2011 08:50, hector castro <hec...@ho...>escribió: > Hola, > > Quisiera saber si alguien tiene funcionando el Imspector, y sobre que > sistema lo tienen instalado? > Yo lo instale en Pfsense y me funciona el log pero no pude bloquear > conversaciones entre contactos. > > Quisiera saber sobre que otro sistema lo han probado, para instalarlo. > > Desde ya muchas gracias. > > Héctor Castro > Montevideo Uruguay > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users > > |
|
From: hector c. <hec...@ho...> - 2011-11-25 11:50:25
|
Hola, Quisiera saber si alguien tiene funcionando el Imspector, y sobre que sistema lo tienen instalado? Yo lo instale en Pfsense y me funciona el log pero no pude bloquear conversaciones entre contactos. Quisiera saber sobre que otro sistema lo han probado, para instalarlo. Desde ya muchas gracias. Héctor Castro Montevideo Uruguay |
|
From: hector c. <hec...@ho...> - 2011-11-15 13:42:36
|
Hi, Fist at all, sorry for my english, i'm a uruguayan guy trying to write english, I have installed pfsense 2.0 with packages squid 2.7.9, squidguard 1.4_2 and imspector 0.9-4. I can block msn service using squid proxy but i want to discriminate some contacts, but i can`t block msn contacts with imspector. For example: I want to allow us...@ho... and block us...@ho.... I configured imspector using the web interface from pfsense, and acl.txt file from command line, without success. Anybody have any idea what's going on here? Thanks in advance, Kind regards Héctor Castro |
|
From: Kerem E. <ker...@gm...> - 2011-06-25 17:52:28
|
I think you should contact the pfsense package maintainer or build your own package... Kerem On Sat, Jun 25, 2011 at 8:36 PM, Terry Danter <ter...@gm...> wrote: > Hi I know its more pfsense related could some one advise me on how too > upgrade imspector to the latest snapshot. The current package seems not too > be logging live messenger 2010 but it is logging the older versions fine. > This is apparently corrected in a snapshot after 27-10-2010. > The current package i have installed is 0.8-10 installed on 2.0-RC3 > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense.. > http://p.sf.net/sfu/splunk-d2d-c1 > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users > > -- Kerem Erciyes - Sistem Danismani http://keremerciyes.com |
|
From: Terry D. <ter...@gm...> - 2011-06-25 17:36:39
|
Hi I know its more pfsense related could some one advise me on how too upgrade imspector to the latest snapshot. The current package seems not too be logging live messenger 2010 but it is logging the older versions fine. This is apparently corrected in a snapshot after 27-10-2010. The current package i have installed is 0.8-10 installed on *2.0-RC3* |
|
From: İbrahim E. <ibr...@en...> - 2011-06-13 08:17:59
|
Hi, When I try to connect gtalk and log it, I get that error from imspector. I dont know how I can log Gtalk? imspector: Error: Don't know how to handle connection to 74.125.39.125:5222 imspector: Finished with child: 192.168.0.198:43442 Note that I created cert files, and I configure .conf file... ** ** |
|
From: Emre Ö. <emr...@gm...> - 2011-03-05 13:56:44
|
Hello everybody, i need like complete tutorail about imspector. I was installed it but i can't logging on mysql. i must learn it. thanks all -- Kendi halinde bir blog - www.emreoner.com Registered Linux User #481714. |
|
From: Lawrence M. <law...@as...> - 2010-11-04 09:24:56
|
> Hi, > in the version that i tedted ; > $ grep SDG msnprotocolplugin.cpp > if (command == "SDG" && argc > 1) > "SDG 0 %d\r\n" \ > > Where is the CVS repo !.. Hmm, so you have the code. How odd. A few (3 or 4) people have run this code and get good results logging etc. CVS repo is on sourceforge: sourceforce.net/projects/imspector Lawrence |
|
From: Ozan U. <ma...@oz...> - 2010-11-03 14:58:03
|
Hi, in the version that i tedted ; $ grep SDG msnprotocolplugin.cpp if (command == "SDG" && argc > 1) "SDG 0 %d\r\n" \ Where is the CVS repo !.. Thanks 2010/10/31 Lawrence Manning <law...@as...>: > Hi, > > It looks very much like you are not using the cVS code to compile the MSN plugin? Are you sure you have done a CVS update? > > Please do > > grep SDG msnprotocolplugin.cpp > > And see if the code mentions the SDG command. > > Lawrence > On 30 Oct 2010, at 11:55, Ozan UÇAR wrote: > >> Hello Lawrence, >> >> I installed and tried >> http://www.imspector.org/downloads/snapshots/imspector-20101030.tar.gz >> codes in freebsd. >> Right now it is running in debug mode and here is the output; >> >> # /usr/local/sbin/imspector -c /usr/local/etc/imspector/imspector.conf-ozanus -d >> imspector: Protocol Plugin name: Gadu-Gadu IMSpector protocol plugin >> imspector: Protocol Plugin name: Jabber IMSpector protocol plugin >> imspector: Protocol Plugin name: MSN IMSpector protocol plugin >> imspector: Protocol Plugin name: Yahoo IMSpector protocol plugin >> imspector: ACL: List /usr/local/etc/imspector/acl.txt size: 3 >> imspector: ACL: Action: Allow >> imspector: ACL: Local: ma...@oz... >> imspector: ACL: Action: Allow >> imspector: ACL: Local: all >> imspector: ACL: Remote: su...@co... >> imspector: ACL: Action: Deny >> imspector: ACL: Local: all >> imspector: Filter Plugin name: ACL IMSpector filter plugin >> imspector: Misc: Blocking all file transfers >> imspector: Filter Plugin name: Misc IMSpector filter plugin >> imspector: Logging Plugin name: Debug IMSpector logging plugin >> imspector: Logging Plugin name: File IMSpector logging plugin >> imspector: Non-HTTP port listening on 0.0.0.0:16667 >> imspector: HTTP port listening on 0.0.0.0:18080 >> imspector: Non-HTTP connection from: 192.168.5.233:55483 >> imspector: Client is connecting to: 64.4.45.62:1863 >> imspector: MSN: Got 47 bytes of header >> imspector: MSN: Command: VER >> imspector: MSN: Got 117 bytes of header >> imspector: MSN: Command: CVR >> imspector: MSN: Got 31 bytes of header >> imspector: MSN: Command: USR >> imspector: MSN: Got 14 bytes of header >> imspector: MSN: Command: VER >> imspector: MSN: Got 188 bytes of header >> imspector: MSN: Command: CVR >> imspector: MSN: Got 67 bytes of header >> imspector: MSN: Command: XFR >> imspector: Finished with child: 192.168.5.233:55483 >> imspector: Non-HTTP connection from: 192.168.5.233:55485 >> imspector: Client is connecting to: 64.4.44.51:1863 >> >> I can login with MSN2011 but chats are not logged. /var/log/imspector is empty. >> And chat logs' records are as follows; >> >> imspector: MSN: Got 2 bytes of header >> imspector: MSN: Command: >> imspector: MSN: Got 69 bytes of header >> imspector: MSN: Command: testing >> >> >> imspector: MSN: Command: X-MMS-IM-Format: >> imspector: MSN: Got 2 bytes of header >> imspector: MSN: Command: >> imspector: MSN: Got 13 bytes of header >> imspector: MSN: Command: :)SDG >> >> imspector: MSN: Got 2 bytes of header >> imspector: MSN: Command: >> imspector: MSN: Got 374 bytes of header >> imspector: MSN: Command: <user><s >> >> >> imspector: MSN: Got 2 bytes of header >> imspector: MSN: Command: >> imspector: MSN: Got 25 bytes of header >> imspector: MSN: Command: testttttttttttttttttNFY >> imspector: MSN: Got 13 bytes of header >> imspector: MSN: Command: SDG >> imspector: MSN: Got 14 bytes of header >> imspector: MSN: Command: Routing: >> imspector: Finished with child: 192.168.5.233:55275 >> >> I compile without the icq and irc plugins and compile with "gmake". >> That would not cause any problems i presume ? >> >> Best regards, >> Ozan UÇAR. >> >> 2010/10/28 Lawrence Manning <law...@as...> >>> >>>> Currently I can not open msn, did not do anything except change msntrace. >>>> Imspector off the stake, MSN opened. >>>> >>>> Msntrace file is attached >>> >>> I wasn't able to work much out from the traces, but I have reworked the >>> plugin a bit to add support for group chats logging. Try the CVS code >>> again? >>> >>> Lawrence >>> >>> > > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users > |
|
From: Luis D. L. Q. <lui...@gm...> - 2010-11-01 04:25:20
|
Le mardi 26 octobre 2010 11:32:05, Lawrence Manning a écrit : > Hi, > > MSN 2011 support has been added to the MSN plugin. 2011 (MSNP21) is the > biggest change to the MSN protocol that I've seen, and this work is a tad > experimintal. :) > > Checkout the CVS build, or wait until tomorrow for the next snapshot build. > > Changes that I've noticed (and this work has been done reverse-engineered > style!) > > * Each chat to a different person now uses a shared TCP connection to the > server. This is clearly better for everyone (less resources) but bad for > IMSpector as we use one process per connection, and this means storing the > remote user ID cannot be done in a simple global variable. Because of > this group chats probably do not quite work right yet for logging > * Messages are sent in a brand new SDG command, which raps the old MSG > command for a few things like file transfers, but is alittle different for > normal messages and typing events. > * Because of the different format in messages, when generating messages > itself IMSpector needs to know the version of the client. For this reason > the version info is now stored for each connection. I'm assuming MSNP21 > is the newest version that has this new format, but I might be wrong... > * File transfer logging, content replacement, typing events, message > events, and message generation have all be tested. > * But I've done hardly any testing to make sure no old clients are broken! > > If people can test this out, and try old and new clients, that would be > super. Let me know if you have any success, or problems. > > Lawrence > > PS. See, IMSpector is not dead! It's just having a bit of a nap. I will > try to get back to giving more time over to working on it, but I continue > to be very busy doing my main job @ Smoothwall. > > > > --------------------------------------------------------------------------- > --- Nokia and AT&T present the 2010 Calling All Innovators-North America > contest Create new apps & games for the Nokia N8 for consumers in U.S. > and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M > in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish > to Ovi Store http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users Thanx I've ported into Mandriva cooke (2011.0) please test so i may push official stable update Regards, LD |
|
From: Lawrence M. <law...@as...> - 2010-10-31 17:13:05
|
Hi, It looks very much like you are not using the cVS code to compile the MSN plugin? Are you sure you have done a CVS update? Please do grep SDG msnprotocolplugin.cpp And see if the code mentions the SDG command. Lawrence On 30 Oct 2010, at 11:55, Ozan UÇAR wrote: > Hello Lawrence, > > I installed and tried > http://www.imspector.org/downloads/snapshots/imspector-20101030.tar.gz > codes in freebsd. > Right now it is running in debug mode and here is the output; > > # /usr/local/sbin/imspector -c /usr/local/etc/imspector/imspector.conf-ozanus -d > imspector: Protocol Plugin name: Gadu-Gadu IMSpector protocol plugin > imspector: Protocol Plugin name: Jabber IMSpector protocol plugin > imspector: Protocol Plugin name: MSN IMSpector protocol plugin > imspector: Protocol Plugin name: Yahoo IMSpector protocol plugin > imspector: ACL: List /usr/local/etc/imspector/acl.txt size: 3 > imspector: ACL: Action: Allow > imspector: ACL: Local: ma...@oz... > imspector: ACL: Action: Allow > imspector: ACL: Local: all > imspector: ACL: Remote: su...@co... > imspector: ACL: Action: Deny > imspector: ACL: Local: all > imspector: Filter Plugin name: ACL IMSpector filter plugin > imspector: Misc: Blocking all file transfers > imspector: Filter Plugin name: Misc IMSpector filter plugin > imspector: Logging Plugin name: Debug IMSpector logging plugin > imspector: Logging Plugin name: File IMSpector logging plugin > imspector: Non-HTTP port listening on 0.0.0.0:16667 > imspector: HTTP port listening on 0.0.0.0:18080 > imspector: Non-HTTP connection from: 192.168.5.233:55483 > imspector: Client is connecting to: 64.4.45.62:1863 > imspector: MSN: Got 47 bytes of header > imspector: MSN: Command: VER > imspector: MSN: Got 117 bytes of header > imspector: MSN: Command: CVR > imspector: MSN: Got 31 bytes of header > imspector: MSN: Command: USR > imspector: MSN: Got 14 bytes of header > imspector: MSN: Command: VER > imspector: MSN: Got 188 bytes of header > imspector: MSN: Command: CVR > imspector: MSN: Got 67 bytes of header > imspector: MSN: Command: XFR > imspector: Finished with child: 192.168.5.233:55483 > imspector: Non-HTTP connection from: 192.168.5.233:55485 > imspector: Client is connecting to: 64.4.44.51:1863 > > I can login with MSN2011 but chats are not logged. /var/log/imspector is empty. > And chat logs' records are as follows; > > imspector: MSN: Got 2 bytes of header > imspector: MSN: Command: > imspector: MSN: Got 69 bytes of header > imspector: MSN: Command: testing > > > imspector: MSN: Command: X-MMS-IM-Format: > imspector: MSN: Got 2 bytes of header > imspector: MSN: Command: > imspector: MSN: Got 13 bytes of header > imspector: MSN: Command: :)SDG > > imspector: MSN: Got 2 bytes of header > imspector: MSN: Command: > imspector: MSN: Got 374 bytes of header > imspector: MSN: Command: <user><s > > > imspector: MSN: Got 2 bytes of header > imspector: MSN: Command: > imspector: MSN: Got 25 bytes of header > imspector: MSN: Command: testttttttttttttttttNFY > imspector: MSN: Got 13 bytes of header > imspector: MSN: Command: SDG > imspector: MSN: Got 14 bytes of header > imspector: MSN: Command: Routing: > imspector: Finished with child: 192.168.5.233:55275 > > I compile without the icq and irc plugins and compile with "gmake". > That would not cause any problems i presume ? > > Best regards, > Ozan UÇAR. > > 2010/10/28 Lawrence Manning <law...@as...> >> >>> Currently I can not open msn, did not do anything except change msntrace. >>> Imspector off the stake, MSN opened. >>> >>> Msntrace file is attached >> >> I wasn't able to work much out from the traces, but I have reworked the >> plugin a bit to add support for group chats logging. Try the CVS code >> again? >> >> Lawrence >> >> |
|
From: Ozan U. <ma...@oz...> - 2010-10-30 10:55:34
|
Hello Lawrence, I installed and tried http://www.imspector.org/downloads/snapshots/imspector-20101030.tar.gz codes in freebsd. Right now it is running in debug mode and here is the output; # /usr/local/sbin/imspector -c /usr/local/etc/imspector/imspector.conf-ozanus -d imspector: Protocol Plugin name: Gadu-Gadu IMSpector protocol plugin imspector: Protocol Plugin name: Jabber IMSpector protocol plugin imspector: Protocol Plugin name: MSN IMSpector protocol plugin imspector: Protocol Plugin name: Yahoo IMSpector protocol plugin imspector: ACL: List /usr/local/etc/imspector/acl.txt size: 3 imspector: ACL: Action: Allow imspector: ACL: Local: ma...@oz... imspector: ACL: Action: Allow imspector: ACL: Local: all imspector: ACL: Remote: su...@co... imspector: ACL: Action: Deny imspector: ACL: Local: all imspector: Filter Plugin name: ACL IMSpector filter plugin imspector: Misc: Blocking all file transfers imspector: Filter Plugin name: Misc IMSpector filter plugin imspector: Logging Plugin name: Debug IMSpector logging plugin imspector: Logging Plugin name: File IMSpector logging plugin imspector: Non-HTTP port listening on 0.0.0.0:16667 imspector: HTTP port listening on 0.0.0.0:18080 imspector: Non-HTTP connection from: 192.168.5.233:55483 imspector: Client is connecting to: 64.4.45.62:1863 imspector: MSN: Got 47 bytes of header imspector: MSN: Command: VER imspector: MSN: Got 117 bytes of header imspector: MSN: Command: CVR imspector: MSN: Got 31 bytes of header imspector: MSN: Command: USR imspector: MSN: Got 14 bytes of header imspector: MSN: Command: VER imspector: MSN: Got 188 bytes of header imspector: MSN: Command: CVR imspector: MSN: Got 67 bytes of header imspector: MSN: Command: XFR imspector: Finished with child: 192.168.5.233:55483 imspector: Non-HTTP connection from: 192.168.5.233:55485 imspector: Client is connecting to: 64.4.44.51:1863 I can login with MSN2011 but chats are not logged. /var/log/imspector is empty. And chat logs' records are as follows; imspector: MSN: Got 2 bytes of header imspector: MSN: Command: imspector: MSN: Got 69 bytes of header imspector: MSN: Command: testing imspector: MSN: Command: X-MMS-IM-Format: imspector: MSN: Got 2 bytes of header imspector: MSN: Command: imspector: MSN: Got 13 bytes of header imspector: MSN: Command: :)SDG imspector: MSN: Got 2 bytes of header imspector: MSN: Command: imspector: MSN: Got 374 bytes of header imspector: MSN: Command: <user><s imspector: MSN: Got 2 bytes of header imspector: MSN: Command: imspector: MSN: Got 25 bytes of header imspector: MSN: Command: testttttttttttttttttNFY imspector: MSN: Got 13 bytes of header imspector: MSN: Command: SDG imspector: MSN: Got 14 bytes of header imspector: MSN: Command: Routing: imspector: Finished with child: 192.168.5.233:55275 I compile without the icq and irc plugins and compile with "gmake". That would not cause any problems i presume ? Best regards, Ozan UÇAR. 2010/10/28 Lawrence Manning <law...@as...> > > > Currently I can not open msn, did not do anything except change msntrace. > > Imspector off the stake, MSN opened. > > > > Msntrace file is attached > > I wasn't able to work much out from the traces, but I have reworked the > plugin a bit to add support for group chats logging. Try the CVS code > again? > > Lawrence > > |
|
From: Lawrence M. <law...@as...> - 2010-10-28 10:41:29
|
> Currently I can not open msn, did not do anything except change msntrace. > Imspector off the stake, MSN opened. > > Msntrace file is attached I wasn't able to work much out from the traces, but I have reworked the plugin a bit to add support for group chats logging. Try the CVS code again? Lawrence |
|
From: Lawrence M. <law...@as...> - 2010-10-27 09:47:48
|
Hey,
On 27 Oct 2010, at 09:14, Ozan UÇAR wrote:
> Hello,
> Thank you for your extraordinary work.
>
> I'm now build from daily snapshots and tested msn 2011. I make and
> install on freebsd 7.
> Firs test, saving msn 2011 messages typing this test fine.
So, you had typing events and messages logged ok?
> Second test was to use ACLs, in this case, ACL rule did not work and
> the messages were not logged.
> Imspector is running debug mode, this is the last part. nothing
> comes after this.
>
> imspector: MSN: 397 bytes of SDG data
> imspector: MSN: header: Routing value: 1.0
> imspector: MSN: header: To value:
> 1:ma...@oz...;epid={f7eb5e20-0ccc-4b82-8aa4-b253cc916328}
> imspector: MSN: header: From value:
> 1:na_...@ho...;epid={7571b102-cdd2-4702-bc2c-d4288f52e3db}
> imspector: MSN: header: Options value: 0
> imspector: MSN: header: Service-Channel value: PE
> imspector: MSN: header: Reliability value: 1.0
> imspector: MSN: header: Messaging value: 2.0
> imspector: MSN: header: Message-Type value: Data
> imspector: MSN: header: Content-Type value: application/x-msnmsgrp2p
> imspector: MSN: header: Content-Transfer-Encoding value: binary
> imspector: MSN: header: Content-Length value: 20
> imspector: MSN: header: Pipe value: 2
> imspector: MSN: header: Bridging-Offsets value: 0
> imspector: MSN: P2P
> imspector: MSN: sessionid: 16 id: 463885222 offset: 160709427069954
> datasize: 0 messagesize: 0
> imspector: MSN: Got 11 bytes of header
> imspector: MSN: Command: SDG
> imspector: MSN: 390 bytes of SDG data
This is strange. The MSN packets above are not "events" so should not
be blocked by the ACL. Could you turn on tracing in IMSpector by
adding "msn_trace=on" to the imspector.conf, and :
mkdir /tmp/trace
chmod 777 /tmp/trace
Then send me the last 5 or so packets in the /tmp/trace dir?
I just tried ACL blocking and it worked fine here.
Lawrence |
|
From: Ozan U. <ma...@oz...> - 2010-10-27 08:14:14
|
Hello,
Thank you for your extraordinary work.
I'm now build from daily snapshots and tested msn 2011. I make and install
on freebsd 7.
Firs test, saving msn 2011 messages typing this test fine.
Second test was to use ACLs, in this case, ACL rule did not work and the
messages were not logged.
Imspector is running debug mode, this is the last part. nothing comes after
this.
imspector: MSN: 397 bytes of SDG data
imspector: MSN: header: Routing value: 1.0
imspector: MSN: header: To value: 1:ma...@oz...<1%3A...@oz...>
;epid={f7eb5e20-0ccc-4b82-8aa4-b253cc916328}
imspector: MSN: header: From value:
1:na_...@ho...<1%3An...@ho...>
;epid={7571b102-cdd2-4702-bc2c-d4288f52e3db}
imspector: MSN: header: Options value: 0
imspector: MSN: header: Service-Channel value: PE
imspector: MSN: header: Reliability value: 1.0
imspector: MSN: header: Messaging value: 2.0
imspector: MSN: header: Message-Type value: Data
imspector: MSN: header: Content-Type value: application/x-msnmsgrp2p
imspector: MSN: header: Content-Transfer-Encoding value: binary
imspector: MSN: header: Content-Length value: 20
imspector: MSN: header: Pipe value: 2
imspector: MSN: header: Bridging-Offsets value: 0
imspector: MSN: P2P
imspector: MSN: sessionid: 16 id: 463885222 offset: 160709427069954
datasize: 0 messagesize: 0
imspector: MSN: Got 11 bytes of header
imspector: MSN: Command: SDG
imspector: MSN: 390 bytes of SDG data
2010/10/26 Lawrence Manning <law...@as...>
> Hi,
>
> MSN 2011 support has been added to the MSN plugin. 2011 (MSNP21) is the
> biggest change to the MSN protocol that I've seen, and this work is a tad
> experimintal. :)
>
> Checkout the CVS build, or wait until tomorrow for the next snapshot build.
>
> Changes that I've noticed (and this work has been done reverse-engineered
> style!)
>
> * Each chat to a different person now uses a shared TCP connection to the
> server. This is clearly better for everyone (less resources) but bad for
> IMSpector as we use one process per connection, and this means storing the
> remote user ID cannot be done in a simple global variable. Because of
> this group chats probably do not quite work right yet for logging
> * Messages are sent in a brand new SDG command, which raps the old MSG
> command for a few things like file transfers, but is alittle different for
> normal messages and typing events.
> * Because of the different format in messages, when generating messages
> itself IMSpector needs to know the version of the client. For this reason
> the version info is now stored for each connection. I'm assuming MSNP21
> is the newest version that has this new format, but I might be wrong...
> * File transfer logging, content replacement, typing events, message
> events, and message generation have all be tested.
> * But I've done hardly any testing to make sure no old clients are broken!
>
> If people can test this out, and try old and new clients, that would be
> super. Let me know if you have any success, or problems.
>
> Lawrence
>
> PS. See, IMSpector is not dead! It's just having a bit of a nap. I will
> try to get back to giving more time over to working on it, but I continue
> to be very busy doing my main job @ Smoothwall.
>
>
>
>
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America
> contest
> Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in
> marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
> http://p.sf.net/sfu/nokia-dev2dev
> _______________________________________________
> Imspector-users mailing list
> Ims...@li...
> https://lists.sourceforge.net/lists/listinfo/imspector-users
>
|
|
From: Luis D. L. Q. <lui...@gm...> - 2010-10-26 17:56:33
|
Le mardi 26 octobre 2010 11:32:05, Lawrence Manning a écrit : > Hi, > > MSN 2011 support has been added to the MSN plugin. 2011 (MSNP21) is the > biggest change to the MSN protocol that I've seen, and this work is a tad > experimintal. :) > > Checkout the CVS build, or wait until tomorrow for the next snapshot build. > > Changes that I've noticed (and this work has been done reverse-engineered > style!) > > * Each chat to a different person now uses a shared TCP connection to the > server. This is clearly better for everyone (less resources) but bad for > IMSpector as we use one process per connection, and this means storing the > remote user ID cannot be done in a simple global variable. Because of > this group chats probably do not quite work right yet for logging > * Messages are sent in a brand new SDG command, which raps the old MSG > command for a few things like file transfers, but is alittle different for > normal messages and typing events. > * Because of the different format in messages, when generating messages > itself IMSpector needs to know the version of the client. For this reason > the version info is now stored for each connection. I'm assuming MSNP21 > is the newest version that has this new format, but I might be wrong... > * File transfer logging, content replacement, typing events, message > events, and message generation have all be tested. > * But I've done hardly any testing to make sure no old clients are broken! > > If people can test this out, and try old and new clients, that would be > super. Let me know if you have any success, or problems. > > Lawrence > > PS. See, IMSpector is not dead! It's just having a bit of a nap. I will > try to get back to giving more time over to working on it, but I continue > to be very busy doing my main job @ Smoothwall. > > > > --------------------------------------------------------------------------- > --- Nokia and AT&T present the 2010 Calling All Innovators-North America > contest Create new apps & games for the Nokia N8 for consumers in U.S. > and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M > in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish > to Ovi Store http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users Cool!!1 |
|
From: Lawrence M. <law...@as...> - 2010-10-26 17:05:37
|
Hi, MSN 2011 support has been added to the MSN plugin. 2011 (MSNP21) is the biggest change to the MSN protocol that I've seen, and this work is a tad experimintal. :) Checkout the CVS build, or wait until tomorrow for the next snapshot build. Changes that I've noticed (and this work has been done reverse-engineered style!) * Each chat to a different person now uses a shared TCP connection to the server. This is clearly better for everyone (less resources) but bad for IMSpector as we use one process per connection, and this means storing the remote user ID cannot be done in a simple global variable. Because of this group chats probably do not quite work right yet for logging * Messages are sent in a brand new SDG command, which raps the old MSG command for a few things like file transfers, but is alittle different for normal messages and typing events. * Because of the different format in messages, when generating messages itself IMSpector needs to know the version of the client. For this reason the version info is now stored for each connection. I'm assuming MSNP21 is the newest version that has this new format, but I might be wrong... * File transfer logging, content replacement, typing events, message events, and message generation have all be tested. * But I've done hardly any testing to make sure no old clients are broken! If people can test this out, and try old and new clients, that would be super. Let me know if you have any success, or problems. Lawrence PS. See, IMSpector is not dead! It's just having a bit of a nap. I will try to get back to giving more time over to working on it, but I continue to be very busy doing my main job @ Smoothwall. |
|
From: Lawrence M. <law...@as...> - 2010-10-23 18:05:47
|
Hi, Is anyone able to get a packet capture of a working session? Failing that, I'll install the client sometime in the week and see what's what. Lawrence On 22 Oct 2010, at 00:31, Doum wrote: > Same problem > > Dominic Ouellette > Référence Systèmes > 418-650-0997 > > On 2010-10-21, at 17:07, Luis Daniel Lucio Quiroz <lui...@gm... > > wrote: > >> Since laste update of msn: >> 2011, compilacion 15.4.3502.922 >> >> it seems that imspector closes connextion. >> >> LD >> >> ------------------------------------------------------------------------------ >> Nokia and AT&T present the 2010 Calling All Innovators-North >> America contest >> Create new apps & games for the Nokia N8 for consumers in U.S. and >> Canada >> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in >> marketing >> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi >> Store >> http://p.sf.net/sfu/nokia-dev2dev >> _______________________________________________ >> Imspector-users mailing list >> Ims...@li... >> https://lists.sourceforge.net/lists/listinfo/imspector-users > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America > contest > Create new apps & games for the Nokia N8 for consumers in U.S. and > Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in > marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi > Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users |
|
From: Doum <do...@gm...> - 2010-10-21 23:31:08
|
Same problem Dominic Ouellette Référence Systèmes 418-650-0997 On 2010-10-21, at 17:07, Luis Daniel Lucio Quiroz <lui...@gm...> wrote: > Since laste update of msn: > 2011, compilacion 15.4.3502.922 > > it seems that imspector closes connextion. > > LD > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users |
|
From: Luis D. L. Q. <lui...@gm...> - 2010-10-21 21:06:57
|
Since laste update of msn: 2011, compilacion 15.4.3502.922 it seems that imspector closes connextion. LD |
|
From: cgslp n. <cg...@gm...> - 2010-07-13 18:09:16
|
>> imspector: Error: Couldn't bind to logging socket This is you can't write to the file (unix-socket). #define LOGGING_SOCKET "/tmp/.imspectorlog" #define COOKIE_SOCKET "/tmp/.imspectoricqcookie" You can't write to that files, that is why bind() fails. Maybe they are already created as root, and your user can't write them. In order to run imspector as non-root, /dev/pf has to be read/writable to your user, but this error happens when a client connects, not at startup. On 7/13/10, Luis Daniel Lucio Quiroz <lui...@gm...> wrote: > Le mardi 13 juillet 2010 10:56:25, Chris a écrit : >> I have recently noticed that i can't get imspector to start properly. I >> have tried commenting out the user/group, and specifying a listenaddr, and >> trying different port ranges(even stopping apache and binding to port 80) >> without any luck. >> >> >> Below is the output of imspector -d >> >> fw06 ) imspector -d >> imspector: Protocol Plugin name: Gadu-Gadu IMSpector protocol plugin >> imspector: Protocol Plugin name: ICQ-AIM IMSpector protocol plugin >> imspector: Listen socket, bind() failed >> imspector: Error: Couldn't bind to icq cookie socket >> imspector: Protocol Plugin name: IRC IMSpector protocol plugin >> imspector: Protocol Plugin name: Jabber IMSpector protocol plugin >> imspector: Protocol Plugin name: MSN IMSpector protocol plugin >> imspector: Protocol Plugin name: Yahoo IMSpector protocol plugin >> imspector: Listen socket, bind() failed >> imspector: Error: Couldn't bind to logging socket >> >> >> Below is my conf. i'm running on openbsd4.6 >> >> # $ComixWall: imspector.conf,v 1.6 2009/11/03 12:12:38 soner Exp $ >> # The listening port for redirected connections >> port=16667 >> # The HTTP CONNECT proxy port >> #http_port=18080 >> >> # This is the default location of protocol and logging plugins. >> plugin_dir=/usr/local/lib/imspector >> >> # For dropping privs - you probably want to do this. >> user=_imspector >> group=_imspector >> >> # SSL support? >> #ssl=on >> #ssl_key=/etc/imspector/serverkey.pem >> >> # Fixed cert? >> #ssl_cert=/etc/imspector/servercert.pem >> >> # Or certs created on-the-fly and signed against a CA >> #ssl_ca_key=/etc/imspector/cakey.pem >> #ssl_ca_cert=/etc/imspector/cacert.pem >> # And finally a directory to store the created certs >> #ssl_cert_dir=/var/lib/imspector >> >> # Directory of CA certs for IM server cert validation >> #ssl_verify_dir=/usr/lib/ssl/certs >> # Drop connection when the IM server has a bad cert >> #ssl_verify=block >> >> # Prefix and postfix to all responses using all responder plugins >> #response_prefix=(E) ***ComixWall WARNING: >> #response_postfix= *** >> >> # SQLite DB filename for automated responses >> #responder_filename=/var/db/imspector/responder.db >> # Inform parties that chats are monitored every N days (default is never) >> #notice_days=7 >> # Customised notice text >> #notice_response=Your activities are being logged >> # Inform of a blocked event, but upto a max of every N mins (default is >> never) >> #filtered_mins=15 >> # Customised filtered text (message text or filename follows in response) >> #filtered_response=The message or action was blocked >> >> # Will load enabled plugins in plugin_dir >> icq_protocol=on >> irc_protocol=on >> msn_protocol=on >> yahoo_protocol=on >> gg_protocol=on >> jabber_protocol=on >> >> # MSN via HTTP proxy needs https >> #https_protocol=on >> >> # Log typing events? >> #log_typing_events=on >> >> # Location where the file logging plugin will start from. >> file_logging_dir=/var/log/imspector >> >> # MySQL logging plugin stuff >> #mysql_server=localhost >> #mysql_database=imspector >> #mysql_username=imspector >> #mysql_password=password >> >> # For SQLite >> #sqlite_file=/var/db/imspector/sqlite.db >> >> # Bad words filtering >> #badwords_filename=/etc/imspector/badwords.txt >> #badwords_replace_character=* >> #badwords_block_count=1 >> >> # ACL >> #acl_filename=/etc/imspector/acl.txt >> >> # SQLite-backed filter >> #db_filter_filename=/var/db/imspector/filter.db >> >> # Block all filetransfers? >> #block_files=on >> >> # Block webcams? >> #block_webcams=on > This is a OS restriction > try to run it as root, ti will work > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users > |
|
From: Luis D. L. Q. <lui...@gm...> - 2010-07-13 17:59:09
|
Le mardi 13 juillet 2010 10:56:25, Chris a écrit : > I have recently noticed that i can't get imspector to start properly. I > have tried commenting out the user/group, and specifying a listenaddr, and > trying different port ranges(even stopping apache and binding to port 80) > without any luck. > > > Below is the output of imspector -d > > fw06 ) imspector -d > imspector: Protocol Plugin name: Gadu-Gadu IMSpector protocol plugin > imspector: Protocol Plugin name: ICQ-AIM IMSpector protocol plugin > imspector: Listen socket, bind() failed > imspector: Error: Couldn't bind to icq cookie socket > imspector: Protocol Plugin name: IRC IMSpector protocol plugin > imspector: Protocol Plugin name: Jabber IMSpector protocol plugin > imspector: Protocol Plugin name: MSN IMSpector protocol plugin > imspector: Protocol Plugin name: Yahoo IMSpector protocol plugin > imspector: Listen socket, bind() failed > imspector: Error: Couldn't bind to logging socket > > > Below is my conf. i'm running on openbsd4.6 > > # $ComixWall: imspector.conf,v 1.6 2009/11/03 12:12:38 soner Exp $ > # The listening port for redirected connections > port=16667 > # The HTTP CONNECT proxy port > #http_port=18080 > > # This is the default location of protocol and logging plugins. > plugin_dir=/usr/local/lib/imspector > > # For dropping privs - you probably want to do this. > user=_imspector > group=_imspector > > # SSL support? > #ssl=on > #ssl_key=/etc/imspector/serverkey.pem > > # Fixed cert? > #ssl_cert=/etc/imspector/servercert.pem > > # Or certs created on-the-fly and signed against a CA > #ssl_ca_key=/etc/imspector/cakey.pem > #ssl_ca_cert=/etc/imspector/cacert.pem > # And finally a directory to store the created certs > #ssl_cert_dir=/var/lib/imspector > > # Directory of CA certs for IM server cert validation > #ssl_verify_dir=/usr/lib/ssl/certs > # Drop connection when the IM server has a bad cert > #ssl_verify=block > > # Prefix and postfix to all responses using all responder plugins > #response_prefix=(E) ***ComixWall WARNING: > #response_postfix= *** > > # SQLite DB filename for automated responses > #responder_filename=/var/db/imspector/responder.db > # Inform parties that chats are monitored every N days (default is never) > #notice_days=7 > # Customised notice text > #notice_response=Your activities are being logged > # Inform of a blocked event, but upto a max of every N mins (default is > never) > #filtered_mins=15 > # Customised filtered text (message text or filename follows in response) > #filtered_response=The message or action was blocked > > # Will load enabled plugins in plugin_dir > icq_protocol=on > irc_protocol=on > msn_protocol=on > yahoo_protocol=on > gg_protocol=on > jabber_protocol=on > > # MSN via HTTP proxy needs https > #https_protocol=on > > # Log typing events? > #log_typing_events=on > > # Location where the file logging plugin will start from. > file_logging_dir=/var/log/imspector > > # MySQL logging plugin stuff > #mysql_server=localhost > #mysql_database=imspector > #mysql_username=imspector > #mysql_password=password > > # For SQLite > #sqlite_file=/var/db/imspector/sqlite.db > > # Bad words filtering > #badwords_filename=/etc/imspector/badwords.txt > #badwords_replace_character=* > #badwords_block_count=1 > > # ACL > #acl_filename=/etc/imspector/acl.txt > > # SQLite-backed filter > #db_filter_filename=/var/db/imspector/filter.db > > # Block all filetransfers? > #block_files=on > > # Block webcams? > #block_webcams=on This is a OS restriction try to run it as root, ti will work |
|
From: Chris <ch...@ae...> - 2010-07-13 17:39:40
|
I have recently noticed that i can't get imspector to start properly. I have tried commenting out the user/group, and specifying a listenaddr, and trying different port ranges(even stopping apache and binding to port 80) without any luck. Below is the output of imspector -d fw06 ) imspector -d imspector: Protocol Plugin name: Gadu-Gadu IMSpector protocol plugin imspector: Protocol Plugin name: ICQ-AIM IMSpector protocol plugin imspector: Listen socket, bind() failed imspector: Error: Couldn't bind to icq cookie socket imspector: Protocol Plugin name: IRC IMSpector protocol plugin imspector: Protocol Plugin name: Jabber IMSpector protocol plugin imspector: Protocol Plugin name: MSN IMSpector protocol plugin imspector: Protocol Plugin name: Yahoo IMSpector protocol plugin imspector: Listen socket, bind() failed imspector: Error: Couldn't bind to logging socket Below is my conf. i'm running on openbsd4.6 # $ComixWall: imspector.conf,v 1.6 2009/11/03 12:12:38 soner Exp $ # The listening port for redirected connections port=16667 # The HTTP CONNECT proxy port #http_port=18080 # This is the default location of protocol and logging plugins. plugin_dir=/usr/local/lib/imspector # For dropping privs - you probably want to do this. user=_imspector group=_imspector # SSL support? #ssl=on #ssl_key=/etc/imspector/serverkey.pem # Fixed cert? #ssl_cert=/etc/imspector/servercert.pem # Or certs created on-the-fly and signed against a CA #ssl_ca_key=/etc/imspector/cakey.pem #ssl_ca_cert=/etc/imspector/cacert.pem # And finally a directory to store the created certs #ssl_cert_dir=/var/lib/imspector # Directory of CA certs for IM server cert validation #ssl_verify_dir=/usr/lib/ssl/certs # Drop connection when the IM server has a bad cert #ssl_verify=block # Prefix and postfix to all responses using all responder plugins #response_prefix=(E) ***ComixWall WARNING: #response_postfix= *** # SQLite DB filename for automated responses #responder_filename=/var/db/imspector/responder.db # Inform parties that chats are monitored every N days (default is never) #notice_days=7 # Customised notice text #notice_response=Your activities are being logged # Inform of a blocked event, but upto a max of every N mins (default is never) #filtered_mins=15 # Customised filtered text (message text or filename follows in response) #filtered_response=The message or action was blocked # Will load enabled plugins in plugin_dir icq_protocol=on irc_protocol=on msn_protocol=on yahoo_protocol=on gg_protocol=on jabber_protocol=on # MSN via HTTP proxy needs https #https_protocol=on # Log typing events? #log_typing_events=on # Location where the file logging plugin will start from. file_logging_dir=/var/log/imspector # MySQL logging plugin stuff #mysql_server=localhost #mysql_database=imspector #mysql_username=imspector #mysql_password=password # For SQLite #sqlite_file=/var/db/imspector/sqlite.db # Bad words filtering #badwords_filename=/etc/imspector/badwords.txt #badwords_replace_character=* #badwords_block_count=1 # ACL #acl_filename=/etc/imspector/acl.txt # SQLite-backed filter #db_filter_filename=/var/db/imspector/filter.db # Block all filetransfers? #block_files=on # Block webcams? #block_webcams=on |
4 messages has been excluded from this view by a project administrator.