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: Luis D. L. Q. <lui...@gm...> - 2010-06-22 21:15:47
|
http://sourceforge.net/projects/msn-proxy/files/ I wonder if lawrence or any other developer could take ideas from this project and add support to imspector for http protocol LD |
|
From: Luis D. L. Q. <lui...@gm...> - 2010-05-14 17:58:08
|
Le jeudi 13 mai 2010 18:53:45, Luis Daniel Lucio Quiroz a écrit : > It is quite odd, > > but imspector.cgi doesnt show anything, i'm don tknow if i missing > something. > > 1. dameon logs and /var/log/imspector is being filled > 2. /var/log/imspector has 775 permitions at least > 3. http is running apache > 4. i did perl ./imspector.cgi and i get html output with not warnings or > sintax error > > any other advice? > > Thanx > > LD It was a proxy mis configuration, how ever i0m getting this ==> /var/log/httpd/error_log <== [Fri May 14 13:55:42 2010] [error] [client 70.82.196.169] Illegal offset (undefined ) resetting..., referer: http:/xxx.xxx.xxx.xxx/cgi-bin/imspector.cgi Under apache 2.2.14, any advice? LD |
|
From: Luis D. L. Q. <lui...@gm...> - 2010-05-13 23:53:00
|
It is quite odd, but imspector.cgi doesnt show anything, i'm don tknow if i missing something. 1. dameon logs and /var/log/imspector is being filled 2. /var/log/imspector has 775 permitions at least 3. http is running apache 4. i did perl ./imspector.cgi and i get html output with not warnings or sintax error any other advice? Thanx LD |
|
From: turgut k. <tu...@ka...> - 2010-04-03 19:07:49
|
Hi there.. for some reason, imspector does not log icq at all. I mean, even though the users use it (including me), it only created two directories: /var/log/imspector/MSN and /var/log/imspector/Yahoo.. All plugins are enabled, and all iptable commands are also working. It logs the others, but no icq.. any ideas? Thanks, -t |
|
From: Luis D. L. Q. <lui...@gm...> - 2010-03-28 21:01:45
|
Le Dimanche 28 Mars 2010 13:56:42, turgut kalfaoğlu a écrit : > Hi there.. The new imspector works great - and pidgin did connect fine > after the latest version. > Is there any hope of supporting HTML/JS based chats? Like facebook, and > pexu.com? > These two are used a lot here.. > > Regards, > -turgut > > > > --------------------------------------------------------------------------- > --- Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users I was trying to do that, programming de FB qjson pluging, however i'm not a very good coder, i got lost |
|
From: turgut k. <tu...@ka...> - 2010-03-28 19:56:46
|
Hi there.. The new imspector works great - and pidgin did connect fine after the latest version. Is there any hope of supporting HTML/JS based chats? Like facebook, and pexu.com? These two are used a lot here.. Regards, -turgut |
|
From: Frank T. <pc...@my...> - 2010-03-28 15:46:55
|
On Sun, 2010-03-28 at 10:07 +0100, Lawrence Manning wrote: > On 28 Mar 2010, at 03:14, Frank Tanner wrote: > > > On Sat, 2010-03-27 at 06:19 +0200, turgut kalfaoğlu wrote: > >> Hi there.. My imspector seems to have started working again. No idea > >> what's going on. Anyway.. > >> One glitch: Pidgin's MSN refuses to connect. Is there anything I > >> can do > >> to fix it? > >> > > > > MSN Changed their login servers a while back. I ended up having to > > use > > the Windows Live Messenger plugin for Pidgin to get it working again. > > Have you tried the latest CVS? I added some tweaks for some stuff to > make adium work again, it's probably the same issue in pidgin. > No I haven't yet. I will see about downloading it and checking it out.... No pun intended. > Lawrence -- --------------------------------------------------- Frank Tanner III (pc...@my...) ICQ: 1730844 AIM: KalokSundancer MSN: pc...@my... YIM: fbtanner |
|
From: Lawrence M. <law...@as...> - 2010-03-28 09:07:17
|
On 28 Mar 2010, at 03:14, Frank Tanner wrote: > On Sat, 2010-03-27 at 06:19 +0200, turgut kalfaoğlu wrote: >> Hi there.. My imspector seems to have started working again. No idea >> what's going on. Anyway.. >> One glitch: Pidgin's MSN refuses to connect. Is there anything I >> can do >> to fix it? >> > > MSN Changed their login servers a while back. I ended up having to > use > the Windows Live Messenger plugin for Pidgin to get it working again. Have you tried the latest CVS? I added some tweaks for some stuff to make adium work again, it's probably the same issue in pidgin. Lawrence |
|
From: Frank T. <pc...@my...> - 2010-03-28 02:27:23
|
On Sat, 2010-03-27 at 06:19 +0200, turgut kalfaoğlu wrote: > Hi there.. My imspector seems to have started working again. No idea > what's going on. Anyway.. > One glitch: Pidgin's MSN refuses to connect. Is there anything I can do > to fix it? > MSN Changed their login servers a while back. I ended up having to use the Windows Live Messenger plugin for Pidgin to get it working again. > Thanks, -turgut > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users -- --------------------------------------------------- Frank Tanner III (pc...@my...) ICQ: 1730844 AIM: KalokSundancer MSN: pc...@my... YIM: fbtanner |
|
From: Lawrence M. <law...@as...> - 2010-03-27 09:21:23
|
On 26 Mar 2010, at 20:24, Luis Daniel Lucio Quiroz wrote: > can anyone do a cvs checkout ? The daily snapshot script failed, so I guess not..... Lawrence |
|
From: turgut k. <tu...@ka...> - 2010-03-27 04:19:15
|
Hi there.. My imspector seems to have started working again. No idea what's going on. Anyway.. One glitch: Pidgin's MSN refuses to connect. Is there anything I can do to fix it? Thanks, -turgut |
|
From: Luis D. L. Q. <lui...@gm...> - 2010-03-26 20:23:46
|
can anyone do a cvs checkout ? |
|
From: turgut k. <tu...@ka...> - 2010-03-26 09:48:55
|
Hi there.. actually it is very strange -- it was working yesterday, until I rebooted.. and now it does not. pidgin does not connect, the real MSN only connects via HTTP (squid picks it up).. Same rules, same everything pretty much.. -turgut # iptables -L -n |more Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT tcp -- 192.168.0.0/16 0.0.0.0/0 tcp dpt:139 ACCEPT tcp -- 192.168.0.0/16 0.0.0.0/0 tcp dpt:139 ACCEPT udp -- 192.168.0.0/16 0.0.0.0/0 udp dpt:138 ACCEPT udp -- 192.168.0.0/16 0.0.0.0/0 udp dpt:138 ACCEPT udp -- 192.168.0.0/16 0.0.0.0/0 udp dpt:137 ACCEPT udp -- 192.168.0.0/16 0.0.0.0/0 udp dpt:137 DROP tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:139 DROP tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:139 DROP tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:139 DROP udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:137 DROP udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:137 DROP udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:137 DROP udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:138 DROP udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:138 DROP udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:138 ACCEPT tcp -- 192.168.0.0/16 0.0.0.0/0 tcp dpt:3389 DROP tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:3389 Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT) target prot opt source destination # iptables -L -n -t nat Chain PREROUTING (policy ACCEPT) target prot opt source destination REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 redir ports 3300 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:1863 redir ports 16667 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:5222 redir ports 16667 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:5223 redir ports 16667 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:5190 redir ports 16667 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:5050 redir ports 16667 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:6667 redir ports 16667 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:8074 redir ports 16667 REDIRECT tcp -- !192.168.0.0/16 0.0.0.0/0 tcp dpt:80 redir ports 82 Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE all -- 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT) target prot opt source destination REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:1863 OWNER UID match 23 redir ports 16667 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:5222 OWNER UID match 23 redir ports 16667 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:5223 OWNER UID match 23 redir ports 16667 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:5190 OWNER UID match 23 redir ports 16667 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:5050 OWNER UID match 23 redir ports 16667 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:6667 OWNER UID match 23 redir ports 16667 REDIRECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:8074 OWNER UID match 23 redir ports 16667 On 03/26/2010 10:41 AM, ozan ucar wrote: > Hello, > Log file directory is /var/log/imspector > There any records in this directory /var/log/imspector > > And can you running imspector debug mode, example ; > > *# /usr/local/sbin/imspector -c > /usr/local/etc/imspector/imspector.conf.yedek -d* > imspector: Protocol Plugin name: Gadu-Gadu IMSpector protocol plugin > imspector: Protocol Plugin name: HTTPS IMSpector protocol plugin > 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: ACL: List /usr/local/etc/imspector/acl.txt size: 7 > imspector: ACL: Action: Allow > imspector: ACL: Local: ma...@oz... > imspector: ACL: Action: Allow > imspector: ACL: Local: xx...@ho... > imspector: ACL: Action: Allow > imspector: ACL: Local: yy...@ya... > imspector: ACL: Action: Allow > imspector: ACL: Local: zz...@ho... > imspector: ACL: Action: Allow > imspector: ACL: Local: aa...@gm... > imspector: ACL: Action: Allow > imspector: ACL: Local: sem...@ho... > imspector: ACL: Action: Allow > imspector: ACL: Local: all > imspector: Filter Plugin name: ACL IMSpector filter plugin > imspector: Bad-words: Loaded 90 bad-words, replacing with 'b' and > blocking at 0 > imspector: Filter Plugin name: Bad-words IMSpector filter plugin > imspector: Misc: Blocking all file transfers > imspector: Filter Plugin name: Misc IMSpector filter plugin > imspector: Non-HTTP port listening on 0.0.0.0:16667 > imspector: Logging Plugin name: Debug IMSpector logging plugin > imspector: Logging Plugin name: File IMSpector logging plugin > imspector: HTTP port listening on 0.0.0.0:18080 > > > turgut kalfaog(lu yazm?s,: >> Hello there.. I have a linux gateway (fedora) server with two eth >> ports, eth0 is local, eth1 points to the net. >> The same machine also runs transparent proxy via squid. My aim is to >> simply log the messages, for compliance with the local law. >> >> I installed imspector, and put these rules, but they do not seem to >> work.. (imspector is running, but no logging takes place, nothing >> unusual in /var/log/messages - apart from imspector loading its >> plugins).. I tried altering the iptables but it did not help. >> >> # I first tried them like this, it did not work: >> #iptables -t nat -A PREROUTING -i eth0 -p tcp -s 192.168.0.177 >> --destination-port 5050 -j DNAT --to-destination 127.0.0.1:16667 >> >> # I currently have it like this: >> iptables -t nat -A PREROUTING -p tcp --destination-port 1863 -j >> REDIRECT --to-ports 16667 >> iptables -t nat -A PREROUTING -p tcp --destination-port 5222 -j >> REDIRECT --to-ports 16667 >> iptables -t nat -A PREROUTING -p tcp --destination-port 5223 -j >> REDIRECT --to-ports 16667 >> iptables -t nat -A PREROUTING -p tcp --destination-port 5190 -j >> REDIRECT --to-ports 16667 >> iptables -t nat -A PREROUTING -p tcp --destination-port 5050 -j >> REDIRECT --to-ports 16667 >> iptables -t nat -A PREROUTING -p tcp --destination-port 6667 -j >> REDIRECT --to-ports 16667 >> iptables -t nat -A PREROUTING -p tcp --destination-port 8074 -j >> REDIRECT --to-ports 16667 >> iptables -t nat -A OUTPUT -p tcp --destination-port 1863 -m owner >> --uid-owner 23 -j REDIRECT --to-ports 16667 >> iptables -t nat -A OUTPUT -p tcp --destination-port 5222 -m owner >> --uid-owner 23 -j REDIRECT --to-ports 16667 >> iptables -t nat -A OUTPUT -p tcp --destination-port 5223 -m owner >> --uid-owner 23 -j REDIRECT --to-ports 16667 >> iptables -t nat -A OUTPUT -p tcp --destination-port 5190 -m owner >> --uid-owner 23 -j REDIRECT --to-ports 16667 >> iptables -t nat -A OUTPUT -p tcp --destination-port 5050 -m owner >> --uid-owner 23 -j REDIRECT --to-ports 16667 >> iptables -t nat -A OUTPUT -p tcp --destination-port 6667 -m owner >> --uid-owner 23 -j REDIRECT --to-ports 16667 >> iptables -t nat -A OUTPUT -p tcp --destination-port 8074 -m owner >> --uid-owner 23 -j REDIRECT --to-ports 16667 >> (...) >> iptables --table nat --append POSTROUTING --out-interface eth1 -j >> MASQUERADE >> iptables -A FORWARD --in-interface eth0 -j ACCEPT >> >> PS: Owner 23 is squid. >> >> Here is the imspector conf file: >> # 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/lib/imspector >> >> # For dropping privs - you probably want to do this. >> #user=imspector >> #group=imspector >> >> # SSL support? >> ssl=on >> ssl_key=/usr/etc/imspector/serverkey.pem >> >> # Fixed cert? >> #ssl_cert=/usr/etc/imspector/servercert.pem >> >> # Or certs created on-the-fly and signed against a CA >> ssl_ca_key=/usr/etc/imspector/cakey.pem >> ssl_ca_cert=/usr/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=Message from IMSpector: -= >> #response_postfix==- >> >> # SQLite DB filename for automated responses >> #responder_filename=/path/to/file >> # 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 >> # Bad words filtering >> #badwords_filename=/usr/etc/imspector/badwords.txt >> #badwords_replace_character=* >> #badwords_block_count=1 >> >> # ACL >> #acl_filename=/usr/etc/imspector/acl.txt >> >> # SQLite-backed filter >> #db_filter_filename=/path/to/file >> >> # Block all filetransfers? >> #block_files=on >> >> # Block webcams? >> #block_webcams=on >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Imspector-users mailing list >> Ims...@li... >> https://lists.sourceforge.net/lists/listinfo/imspector-users >> > > |
|
From: ozan u. <by....@gm...> - 2010-03-26 08:42:13
|
Hello, Log file directory is /var/log/imspector There any records in this directory /var/log/imspector And can you running imspector debug mode, example ; *# /usr/local/sbin/imspector -c /usr/local/etc/imspector/imspector.conf.yedek -d* imspector: Protocol Plugin name: Gadu-Gadu IMSpector protocol plugin imspector: Protocol Plugin name: HTTPS IMSpector protocol plugin 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: ACL: List /usr/local/etc/imspector/acl.txt size: 7 imspector: ACL: Action: Allow imspector: ACL: Local: ma...@oz... imspector: ACL: Action: Allow imspector: ACL: Local: xx...@ho... imspector: ACL: Action: Allow imspector: ACL: Local: yy...@ya... imspector: ACL: Action: Allow imspector: ACL: Local: zz...@ho... imspector: ACL: Action: Allow imspector: ACL: Local: aa...@gm... imspector: ACL: Action: Allow imspector: ACL: Local: sem...@ho... imspector: ACL: Action: Allow imspector: ACL: Local: all imspector: Filter Plugin name: ACL IMSpector filter plugin imspector: Bad-words: Loaded 90 bad-words, replacing with 'b' and blocking at 0 imspector: Filter Plugin name: Bad-words IMSpector filter plugin imspector: Misc: Blocking all file transfers imspector: Filter Plugin name: Misc IMSpector filter plugin imspector: Non-HTTP port listening on 0.0.0.0:16667 imspector: Logging Plugin name: Debug IMSpector logging plugin imspector: Logging Plugin name: File IMSpector logging plugin imspector: HTTP port listening on 0.0.0.0:18080 turgut kalfaog(lu yazm?s,: > Hello there.. I have a linux gateway (fedora) server with two eth ports, > eth0 is local, eth1 points to the net. > The same machine also runs transparent proxy via squid. My aim is to > simply log the messages, for compliance with the local law. > > I installed imspector, and put these rules, but they do not seem to > work.. (imspector is running, but no logging takes place, nothing > unusual in /var/log/messages - apart from imspector loading its > plugins).. I tried altering the iptables but it did not help. > > # I first tried them like this, it did not work: > #iptables -t nat -A PREROUTING -i eth0 -p tcp -s 192.168.0.177 > --destination-port 5050 -j DNAT --to-destination 127.0.0.1:16667 > > # I currently have it like this: > iptables -t nat -A PREROUTING -p tcp --destination-port 1863 -j REDIRECT > --to-ports 16667 > iptables -t nat -A PREROUTING -p tcp --destination-port 5222 -j REDIRECT > --to-ports 16667 > iptables -t nat -A PREROUTING -p tcp --destination-port 5223 -j REDIRECT > --to-ports 16667 > iptables -t nat -A PREROUTING -p tcp --destination-port 5190 -j REDIRECT > --to-ports 16667 > iptables -t nat -A PREROUTING -p tcp --destination-port 5050 -j REDIRECT > --to-ports 16667 > iptables -t nat -A PREROUTING -p tcp --destination-port 6667 -j REDIRECT > --to-ports 16667 > iptables -t nat -A PREROUTING -p tcp --destination-port 8074 -j REDIRECT > --to-ports 16667 > iptables -t nat -A OUTPUT -p tcp --destination-port 1863 -m owner > --uid-owner 23 -j REDIRECT --to-ports 16667 > iptables -t nat -A OUTPUT -p tcp --destination-port 5222 -m owner > --uid-owner 23 -j REDIRECT --to-ports 16667 > iptables -t nat -A OUTPUT -p tcp --destination-port 5223 -m owner > --uid-owner 23 -j REDIRECT --to-ports 16667 > iptables -t nat -A OUTPUT -p tcp --destination-port 5190 -m owner > --uid-owner 23 -j REDIRECT --to-ports 16667 > iptables -t nat -A OUTPUT -p tcp --destination-port 5050 -m owner > --uid-owner 23 -j REDIRECT --to-ports 16667 > iptables -t nat -A OUTPUT -p tcp --destination-port 6667 -m owner > --uid-owner 23 -j REDIRECT --to-ports 16667 > iptables -t nat -A OUTPUT -p tcp --destination-port 8074 -m owner > --uid-owner 23 -j REDIRECT --to-ports 16667 > (...) > iptables --table nat --append POSTROUTING --out-interface eth1 -j MASQUERADE > iptables -A FORWARD --in-interface eth0 -j ACCEPT > > PS: Owner 23 is squid. > > Here is the imspector conf file: > # 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/lib/imspector > > # For dropping privs - you probably want to do this. > #user=imspector > #group=imspector > > # SSL support? > ssl=on > ssl_key=/usr/etc/imspector/serverkey.pem > > # Fixed cert? > #ssl_cert=/usr/etc/imspector/servercert.pem > > # Or certs created on-the-fly and signed against a CA > ssl_ca_key=/usr/etc/imspector/cakey.pem > ssl_ca_cert=/usr/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=Message from IMSpector: -= > #response_postfix==- > > # SQLite DB filename for automated responses > #responder_filename=/path/to/file > # 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 > # Bad words filtering > #badwords_filename=/usr/etc/imspector/badwords.txt > #badwords_replace_character=* > #badwords_block_count=1 > > # ACL > #acl_filename=/usr/etc/imspector/acl.txt > > # SQLite-backed filter > #db_filter_filename=/path/to/file > > # Block all filetransfers? > #block_files=on > > # Block webcams? > #block_webcams=on > > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users > > |
|
From: turgut k. <tu...@ka...> - 2010-03-26 07:51:29
|
Hello there.. I have a linux gateway (fedora) server with two eth ports, eth0 is local, eth1 points to the net. The same machine also runs transparent proxy via squid. My aim is to simply log the messages, for compliance with the local law. I installed imspector, and put these rules, but they do not seem to work.. (imspector is running, but no logging takes place, nothing unusual in /var/log/messages - apart from imspector loading its plugins).. I tried altering the iptables but it did not help. # I first tried them like this, it did not work: #iptables -t nat -A PREROUTING -i eth0 -p tcp -s 192.168.0.177 --destination-port 5050 -j DNAT --to-destination 127.0.0.1:16667 # I currently have it like this: iptables -t nat -A PREROUTING -p tcp --destination-port 1863 -j REDIRECT --to-ports 16667 iptables -t nat -A PREROUTING -p tcp --destination-port 5222 -j REDIRECT --to-ports 16667 iptables -t nat -A PREROUTING -p tcp --destination-port 5223 -j REDIRECT --to-ports 16667 iptables -t nat -A PREROUTING -p tcp --destination-port 5190 -j REDIRECT --to-ports 16667 iptables -t nat -A PREROUTING -p tcp --destination-port 5050 -j REDIRECT --to-ports 16667 iptables -t nat -A PREROUTING -p tcp --destination-port 6667 -j REDIRECT --to-ports 16667 iptables -t nat -A PREROUTING -p tcp --destination-port 8074 -j REDIRECT --to-ports 16667 iptables -t nat -A OUTPUT -p tcp --destination-port 1863 -m owner --uid-owner 23 -j REDIRECT --to-ports 16667 iptables -t nat -A OUTPUT -p tcp --destination-port 5222 -m owner --uid-owner 23 -j REDIRECT --to-ports 16667 iptables -t nat -A OUTPUT -p tcp --destination-port 5223 -m owner --uid-owner 23 -j REDIRECT --to-ports 16667 iptables -t nat -A OUTPUT -p tcp --destination-port 5190 -m owner --uid-owner 23 -j REDIRECT --to-ports 16667 iptables -t nat -A OUTPUT -p tcp --destination-port 5050 -m owner --uid-owner 23 -j REDIRECT --to-ports 16667 iptables -t nat -A OUTPUT -p tcp --destination-port 6667 -m owner --uid-owner 23 -j REDIRECT --to-ports 16667 iptables -t nat -A OUTPUT -p tcp --destination-port 8074 -m owner --uid-owner 23 -j REDIRECT --to-ports 16667 (...) iptables --table nat --append POSTROUTING --out-interface eth1 -j MASQUERADE iptables -A FORWARD --in-interface eth0 -j ACCEPT PS: Owner 23 is squid. Here is the imspector conf file: # 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/lib/imspector # For dropping privs - you probably want to do this. #user=imspector #group=imspector # SSL support? ssl=on ssl_key=/usr/etc/imspector/serverkey.pem # Fixed cert? #ssl_cert=/usr/etc/imspector/servercert.pem # Or certs created on-the-fly and signed against a CA ssl_ca_key=/usr/etc/imspector/cakey.pem ssl_ca_cert=/usr/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=Message from IMSpector: -= #response_postfix==- # SQLite DB filename for automated responses #responder_filename=/path/to/file # 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 # Bad words filtering #badwords_filename=/usr/etc/imspector/badwords.txt #badwords_replace_character=* #badwords_block_count=1 # ACL #acl_filename=/usr/etc/imspector/acl.txt # SQLite-backed filter #db_filter_filename=/path/to/file # Block all filetransfers? #block_files=on # Block webcams? #block_webcams=on |
|
From: Luis D. L. Q. <lui...@gm...> - 2010-03-05 21:47:49
|
Le Vendredi 5 Mars 2010 13:37:56, Lawrence Manning a écrit : > Hi, > > It's funny you should mention documentation. Have you looked at > www.imspector.org/doxygen ? It's not finished yet, but it's getting there. > > Unfortunately the biggest issue with FB chat is not that it is http/ > html, but that it uses the standard HTTP port. This means your > browser would have to be configured to send ALL HTTP proxy through > imspector for it to have a chance of spotting the FB messages. > IMSpector really was not designed for being a HTTP proxy... > > Lawrence > > On 4 Mar 2010, at 22:29, Luis Daniel Lucio Quiroz wrote: > > Le Samedi 6 Février 2010 09:22:46, Lawrence Manning a écrit : > >> On 6 Feb 2010, at 11:38, Terry wrote: > >>> well imspector is working great with pfsense so thank you. Are there > >>> any > >>> plans to include facebook chat as in the little messenger type thing > >>> as > >>> I am tring to monitor my kids. > >> > >> Unfortunately facecrap is completely HTTP based, and IMSpector > >> doesn't > >> currently know anything about HTTP. Also it runs in the normal port > >> 80, so without feeding all port 80 traffic through IMSpector it > >> wouldn't see the facebook chats. Unfortunately it's a job for your > >> HTTP proxy. > >> > >> Lawrence > >> > >> > >> ------------------------------------------------------------------------ > >> --- --- The Planet: dedicated and managed hosting, cloud storage, > >> colocation > >> Stay online with enterprise data centers and the best network in the > >> business Choose flexible plans and management services without long- > >> term > >> contracts Personal 24x7 support from experience hosting pros just a > >> phone > >> call away. http://p.sf.net/sfu/theplanet-com > >> _______________________________________________ > >> Imspector-users mailing list > >> Ims...@li... > >> https://lists.sourceforge.net/lists/listinfo/imspector-users > > > > Laurance, > > > > do you think you could write a template on how to write pluggins for > > imspector. I'd really like to figure out how to look fb html chats. > > > > How ever Terry, dont be panic. Facebook has published its beta of > > jabber > > service. Dont worry about redirection, there are 2 ways to redirecto 1. mark traffic with squid, dstdomain .chat.fb.com (somethin like this i have realize) 2. redireect with iptables taht's the easiest part, the hardest is to program LD |
|
From: Lawrence M. <law...@as...> - 2010-03-05 19:55:22
|
Hi, It's funny you should mention documentation. Have you looked at www.imspector.org/doxygen ? It's not finished yet, but it's getting there. Unfortunately the biggest issue with FB chat is not that it is http/ html, but that it uses the standard HTTP port. This means your browser would have to be configured to send ALL HTTP proxy through imspector for it to have a chance of spotting the FB messages. IMSpector really was not designed for being a HTTP proxy... Lawrence On 4 Mar 2010, at 22:29, Luis Daniel Lucio Quiroz wrote: > Le Samedi 6 Février 2010 09:22:46, Lawrence Manning a écrit : >> On 6 Feb 2010, at 11:38, Terry wrote: >>> well imspector is working great with pfsense so thank you. Are there >>> any >>> plans to include facebook chat as in the little messenger type thing >>> as >>> I am tring to monitor my kids. >> >> Unfortunately facecrap is completely HTTP based, and IMSpector >> doesn't >> currently know anything about HTTP. Also it runs in the normal port >> 80, so without feeding all port 80 traffic through IMSpector it >> wouldn't see the facebook chats. Unfortunately it's a job for your >> HTTP proxy. >> >> Lawrence >> >> >> --------------------------------------------------------------------------- >> --- The Planet: dedicated and managed hosting, cloud storage, >> colocation >> Stay online with enterprise data centers and the best network in the >> business Choose flexible plans and management services without long- >> term >> contracts Personal 24x7 support from experience hosting pros just a >> phone >> call away. http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> Imspector-users mailing list >> Ims...@li... >> https://lists.sourceforge.net/lists/listinfo/imspector-users > > Laurance, > > do you think you could write a template on how to write pluggins for > imspector. I'd really like to figure out how to look fb html chats. > > How ever Terry, dont be panic. Facebook has published its beta of > jabber > service. |
|
From: Luis D. L. Q. <lui...@gm...> - 2010-03-04 22:29:47
|
Le Samedi 6 Février 2010 09:22:46, Lawrence Manning a écrit : > On 6 Feb 2010, at 11:38, Terry wrote: > > well imspector is working great with pfsense so thank you. Are there > > any > > plans to include facebook chat as in the little messenger type thing > > as > > I am tring to monitor my kids. > > Unfortunately facecrap is completely HTTP based, and IMSpector doesn't > currently know anything about HTTP. Also it runs in the normal port > 80, so without feeding all port 80 traffic through IMSpector it > wouldn't see the facebook chats. Unfortunately it's a job for your > HTTP proxy. > > Lawrence > > > --------------------------------------------------------------------------- > --- The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the > business Choose flexible plans and management services without long-term > contracts Personal 24x7 support from experience hosting pros just a phone > call away. http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users Laurance, do you think you could write a template on how to write pluggins for imspector. I'd really like to figure out how to look fb html chats. How ever Terry, dont be panic. Facebook has published its beta of jabber service. |
|
From: <mi...@ma...> - 2010-03-01 13:26:41
|
> I also > how ever I did connect, > what client do you have, i use kopete, from kde4.x > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users I use pidgin from gnome. So in fact I launch proxy, launch imspector and launch icq-client on one local system, but I don't think it would be wrong because in thery packet route would be like: icq-client (localhost) - login.icq.com through socks5 (localhost:1080) - localhost:16667 - login.icq.com |
|
From: Luis D. L. Q. <lui...@gm...> - 2010-03-01 13:12:49
|
Le Lundi 1 Mars 2010 04:19:50, mi...@ma... a écrit : > Hello > > After compilation and installation of 2009-07-20 imspector on centos > (virtual machine (VirtualBox) 5.4 I tried to run it through socks5 > server. I added iptables rule for icq and root account: > > iptables -t nat -A OUTPUT -p tcp --destination-port 5190 -m owner > --uid-owner 0 -j REDIRECT --to-ports 16667 > > launched imspector "imspector -d" launched icq-client pidgin through > socks5 > > got too many messages and icq-client didn't change status to "Online" > - system started going hard and I decided to press ctrl-C > > what am I doing wrong? > > <<< CONSOLE OUTPUT >>> > imspector: Protocol Plugin name: ICQ-AIM IMSpector protocol 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: Non-HTTP connection from: 10.0.2.15:39337 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49548 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49549 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49550 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49551 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49552 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49553 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49554 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49555 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49556 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49557 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49558 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49559 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49560 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49561 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49562 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49563 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49564 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49565 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49566 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49567 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49568 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49569 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49570 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49571 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49572 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49573 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49574 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49575 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49576 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49577 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49578 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49579 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49580 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49581 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49582 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49583 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49584 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49585 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49586 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49587 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49588 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49589 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49590 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49591 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49592 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49593 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49594 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49595 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49596 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49597 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49598 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49599 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49600 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: Non-HTTP connection from: 10.0.2.15:49601 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49602 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49603 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49604 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49605 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49606 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49607 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49608 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49609 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49610 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49611 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49612 > imspector: Client is connecting to: 64.12.202.116:5190 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Non-HTTP connection from: 10.0.2.15:49613 > imspector: Client is connecting to: 64.12.202.116:5190imspector: Finished > with child: 10.0.2.15:49548 imspector: Finished with child: > 10.0.2.15:39337 > imspector: Finished with child: 10.0.2.15:49549 > imspector: Finished with child: 10.0.2.15:49551 > imspector: Finished with child: 10.0.2.15:49550 > imspector: Finished with child: 10.0.2.15:49552 > imspector: Finished with child: 10.0.2.15:49553 > imspector: Finished with child: 10.0.2.15:49558 > imspector: Finished with child: 10.0.2.15:49557 > imspector: Finished with child: 10.0.2.15:49556 > imspector: Finished with child: 10.0.2.15:49555 > imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 > imspector: Good-bye > > > --------------------------------------------------------------------------- > --- Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Imspector-users mailing list > Ims...@li... > https://lists.sourceforge.net/lists/listinfo/imspector-users I also how ever I did connect, what client do you have, i use kopete, from kde4.x |
|
From: <mi...@ma...> - 2010-03-01 10:20:07
|
Hello After compilation and installation of 2009-07-20 imspector on centos (virtual machine (VirtualBox) 5.4 I tried to run it through socks5 server. I added iptables rule for icq and root account: iptables -t nat -A OUTPUT -p tcp --destination-port 5190 -m owner --uid-owner 0 -j REDIRECT --to-ports 16667 launched imspector "imspector -d" launched icq-client pidgin through socks5 got too many messages and icq-client didn't change status to "Online" - system started going hard and I decided to press ctrl-C what am I doing wrong? <<< CONSOLE OUTPUT >>> imspector: Protocol Plugin name: ICQ-AIM IMSpector protocol 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: Non-HTTP connection from: 10.0.2.15:39337 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49548 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49549 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49550 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49551 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49552 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49553 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49554 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49555 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49556 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49557 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49558 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49559 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49560 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49561 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49562 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49563 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49564 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49565 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49566 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49567 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49568 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49569 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49570 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49571 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49572 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49573 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49574 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49575 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49576 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49577 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49578 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49579 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49580 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49581 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49582 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49583 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49584 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49585 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49586 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49587 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49588 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49589 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49590 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49591 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49592 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49593 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49594 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49595 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49596 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49597 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49598 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49599 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49600 imspector: Client is connecting to: 64.12.202.116:5190 imspector: Non-HTTP connection from: 10.0.2.15:49601 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49602 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49603 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49604 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49605 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49606 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49607 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49608 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49609 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49610 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49611 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49612 imspector: Client is connecting to: 64.12.202.116:5190 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Non-HTTP connection from: 10.0.2.15:49613 imspector: Client is connecting to: 64.12.202.116:5190imspector: Finished with child: 10.0.2.15:49548 imspector: Finished with child: 10.0.2.15:39337 imspector: Finished with child: 10.0.2.15:49549 imspector: Finished with child: 10.0.2.15:49551 imspector: Finished with child: 10.0.2.15:49550 imspector: Finished with child: 10.0.2.15:49552 imspector: Finished with child: 10.0.2.15:49553 imspector: Finished with child: 10.0.2.15:49558 imspector: Finished with child: 10.0.2.15:49557 imspector: Finished with child: 10.0.2.15:49556 imspector: Finished with child: 10.0.2.15:49555 imspector: ICQ-AIM: uin: Unknown, unknown family: 0017 subtype: 0006 imspector: Good-bye |
|
From: Luis D. L. Q. <lui...@gm...> - 2010-03-01 02:09:09
|
Le Lundi 28 Septembre 2009 20:05:09, David Trebacz a écrit : > On Monday 28 September 2009 10:17:18 am Luis Daniel Lucio Quiroz wrote: > > Le dimanche 27 septembre 2009 21:14:47, David Trebacz a écrit : > > > When I attempt to run IMspector on my smoothwall via the command: > > > > > > > > > > > > imspector -d -c "/var/smoothwall/im/imspector.conf" > > > > > > > > > > > > I get the following output: > > > > > > imspector: Protocol Plugin name: Gadu-Gadu IMSpector protocol plugin > > > > > > imspector: Protocol Plugin name: ICQ-AIM IMSpector protocol plugin > > > > > > 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: Bad-words: Loaded 86 bad-words, replacing with '*' and > > > blocking at 0 > > > > > > imspector: Filter Plugin name: Bad-words IMSpector filter plugin > > > > > > imspector: Listen socket, bind() failed > > > > > > imspector: Error: Couldn't bind to logging socket > > > > > > > > > > > > I'm assuming the problem is the Listen socket, bind failed. > > > > > > > > > > > > Below is my imspector.conf file: > > > > > > > > > > > > # The listening port > > > > > > port=16667 > > > > > > > > > > > > # This is the default location of protocol and logging plugins. > > > > > > #plugin_dir=/usr/lib/imspector > > > > > > > > > > > > # For dropping privs - you probably want to do this. > > > > > > user=imspector > > > > > > group=imspector > > > > > > > > > > > > # Location where the file logging plugin will start from. > > > > > > file_logging_dir=/var/log/imspector > > > > > > > > > > > > # Generated stuff from here > > > > > > msn_protocol=on > > > > > > yahoo_protocol=on > > > > > > icq_protocol=on > > > > > > irc_protocol=on > > > > > > gg_protocol=on > > > > > > jabber_protocol=on > > > > > > badwords_filename=/usr/etc/imspector/badwords.txt > > > > > > badwords_replace_character=* > > > > Comment your user/group lines > > > > I did have same problem > > > > ------------------------------------------------------------------------- > > -- --- Come build with us! The BlackBerry® Developer Conference in > > SF, CA > > > > is the only developer event you need to attend this year. Jumpstart your > > developing skills, take BlackBerry mobile applications to market and > > stay ahead of the curve. Join us from November 9-12, 2009. Register > > now! http://p.sf.net/sfu/devconf > > > > _______________________________________________ > > Imspector-users mailing list > > Ims...@li... > > https://lists.sourceforge.net/lists/listinfo/imspector-users > > Was your problem fixed by a change to main a couple of months ago or are > you still having issues? I noticed a commit that had expressed thanks to > you (I think). > > Revision 1.24 - (view) (download) (annotate) - [select for diffs] > Sat Jul 11 14:19:46 2009 UTC (2 months, 2 weeks ago) by aslak > Branch: MAIN > CVS Tags: HEAD, release-0_9 > Changes since 1.23: +1 -1 lines > Diff to previous 1.23 > Fix for GCC 4.4. > > Thanks to luis dot daniel dot lucio at gmail.com. I'm having same issue as you when running as other user than root, i really don tknow why. Maybe Lawrence may give us a workarround. |
|
From: Lawrence M. <law...@as...> - 2010-02-26 19:41:23
|
Hi, On 26 Feb 2010, at 10:11, pjama wrote: > I'm now running what I think is a more supported platform except > that I > have imspector and iptables running on separate machines. > > Imspector 0.9 has been compiled and installed on ubuntu 9.10. My > gateway > is a is a router running openwrt which transparently captures MSN > traffic and redirects it to por 16667 on the ubuntu box running > imspector which in turn has been given access out to the internet > (bypassing transparent proxying on the router). > ... > > imspector: Non-HTTP connection from: 192.168.x.1:1061 > imspector: Redirect address, getsockopt() failed > imspector: Client is connecting to: > imspector: Error: Don't know how to handle connection to > imspector: Finished with child: 192.168.x.1:1061 > > Help...please...:) Sadly this isn't going to work. IMSpector will never see the original address, as it's lost when the packet is put back on the network. What you need is this: http://rootmanager.com/imspector/gateway-imspector-different-computers.txt It's alittle more complex then just iptables rules, but it should work for you. Lawrence |
|
From: pjama <pj...@us...> - 2010-02-26 10:15:00
|
I'm now running what I think is a more supported platform except that I have imspector and iptables running on separate machines. Imspector 0.9 has been compiled and installed on ubuntu 9.10. My gateway is a is a router running openwrt which transparently captures MSN traffic and redirects it to por 16667 on the ubuntu box running imspector which in turn has been given access out to the internet (bypassing transparent proxying on the router). My problem is that Windows live I get: peter@mythbuntu:/opt/IMSpector/etc/imspector$ sudo /opt/IMSpector/sbin/imspector -c /opt/IMSpector/etc/imspector/imspector.conf -d imspector: Protocol Plugin name: Gadu-Gadu IMSpector protocol plugin imspector: Protocol Plugin name: HTTPS IMSpector protocol plugin imspector: Protocol Plugin name: ICQ-AIM IMSpector protocol plugin imspector: Protocol Plugin name: IRC IMSpector protocol plugin imspector: Jabber: Monitoring SSL/TLS 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 /opt/IMSpector/etc/imspector/acl.txt size: 1 imspector: ACL: Action: Allow imspector: ACL: Local: all imspector: Filter Plugin name: ACL IMSpector filter plugin imspector: Non-HTTP port listening on 192.168.x.76:16667 imspector: HTTP port listening on 192.168.x.76:18080 imspector: Logging Plugin name: Debug IMSpector logging plugin imspector: Logging Plugin name: File IMSpector logging plugin imspector: Non-HTTP connection from: 192.168.x.1:1061 imspector: Redirect address, getsockopt() failed imspector: Client is connecting to: imspector: Error: Don't know how to handle connection to imspector: Finished with child: 192.168.x.1:1061 Help...please...:) Cheers Peter -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. |
|
From: Lawrence M. <law...@as...> - 2010-02-10 22:40:57
|
On 9 Feb 2010, at 06:15, Luis Daniel Lucio Quiroz wrote: > hi there > under imspector 0.9 i get connected and then disconnected > i'm using kopete (kde4.4rc3), does anyone has same behaivor? Without > imspector, yahoo msg works okay. Do you get anything interesting if you run in debug with -d? Lawrence |
4 messages has been excluded from this view by a project administrator.