#32 Bot sentry 1.3.0 doesn't work with pidgin 2.5.1

v1.3.0
closed-works-for-me
Bug (11)
1
2008-09-16
2008-09-12
Sergey
No

First message triggers question, but all next messages
bypass sentry. So it doesn't work anymore. Please check.

How to reproduce:
tar xjf /usr/src/packages/SOURCES/pidgin-2.5.1.tar.bz2
./configure --prefix=/tmp/pidgin
make install

tar xjf \ /usr/src/packages/SOURCES/bot-sentry-1.3.0.tar.bz2
PKG_CONFIG_PATH=/tmp/pidgin/lib/pkgconfig/ \ ./configure --prefix=/tmp/pidgin
make install

/tmp/pidgin/bin/pidgin
# Enable bot sentry, select grant all authorization,
# remove buddy from list and ask him
# to write you without giving a correct answer

Discussion

1 2 > >> (Page 1 of 2)
  • David Everly

    David Everly - 2008-09-12

    what other plugins are enabled?

    Is it possible pidgin is picking up an old bob-sentry along with the new one? (Pidgin searches several directories for its plugins.)

    Have you seleced the option to auto-add senders of messages to your buddy list or permit list?

    Is this only with msn or msn-pecan users? (If so, this is a possible duplicate of the https://sourceforge.net/tracker/index.php?func=detail&aid=2002718&group_id=156021&atid=798112 bug.)

     
  • David Everly

    David Everly - 2008-09-12
    • priority: 5 --> 1
    • status: open --> pending
     
  • Sergey

    Sergey - 2008-09-12
    • status: pending --> open
     
  • Sergey

    Sergey - 2008-09-12

    > what other plugins are enabled?
    I've removed .gaim and .purpe directories.
    Checking right now... None, only bot sentry enabled.

    > Is it possible pidgin is picking up an old bob-sentry along with the new
    one?
    No, I've removed old bot-sentry and pidgin rpms from system before checking.
    $ sudo find / -name bot-sentry.so
    /tmp/pidgin/lib/purple-2/bot-sentry.so
    /usr/src/packages/BUILD/bot-sentry-1.2.1/src/.libs/bot-sentry.so
    /usr/src/packages/BUILD/bot-sentry-1.3.0/src/.libs/bot-sentry.so

    > Have you seleced the option to auto-add senders of messages to your buddy
    list or permit list?
    No, all marks cleared.

    > Is this only with msn or msn-pecan users? (If so, this is a possible
    duplicate of the
    https://sourceforge.net/tracker/index.php?func=detail&aid=2002718&group_id=156021&atid=798112
    bug.)

    No, I don't use MSN at all. It's ICQ(oscar) related issue.

     
  • David Everly

    David Everly - 2008-09-12

    Ok. And you say the first message triggers the bot sentry question back to the sender, but after that what happens (please give exact sequence of actions taken by both you and the other person as well as bot sentry enties for that session from the debug window)?

    Note that if you have an IM window open to that user when s/he sends a message, bot sentry will let it through.

     
  • David Everly

    David Everly - 2008-09-12
    • status: open --> pending
     
  • Sergey

    Sergey - 2008-09-12
    • status: pending --> open
     
  • Sergey

    Sergey - 2008-09-12

    Ok, my second test messenger was Kopete..

    I sent first message to myself from Kopete, it was successfully blocked.
    No pidgin's icon status, bot question returned. Then I typed second
    message (not a correct answer, just a text message) and it was passed
    by botsentry. I see icon status, clicked on it, got a message passed, third
    and fourth are also passed ... :(

    So first message blocked and all other passed. No Pidgin's message window at
    this moment* because I've not seen icon status yet....

    * no message window when second message recieved, has a message window for third, forth,etc....

     
  • David Everly

    David Everly - 2008-09-12
    • status: open --> pending
     
  • David Everly

    David Everly - 2008-09-12

    Are you able to paste the bot-sentry debug messages from such a test into this report please?

     
  • David Everly

    David Everly - 2008-09-14
    • assigned_to: nobody --> deckrider
    • labels: --> Bug
    • milestone: --> v1.3.0
    • status: pending --> pending-works-for-me
     
  • David Everly

    David Everly - 2008-09-14

    I've finally had time to try this on my system (debian/stable). I did essentially something similar to you (except I installed to --prefix=/home/deckrider/pidgin251 instead of under /tmp/.

    Also instead of aim, I used irc, since it is easy to have two temporary accounts.

    Everything appears to work for me as expected. Perhaps there is some overlap of an existing pidgin and associated headers that is being picked up during configure/make/install or at runtime?

    Anyway, let me know what appears in the debug window filtered by 'bot-sentry'. And also, can you please try again using an install under your home directory instead of '/tmp'?

    For instance, here's what I did:

    for i in intltool-0.40.3.tar.bz2 bot-sentry-1.3.0.tar.bz2 pidgin-2.5.1.tar.bz2 ; do tar jxvf $i ; done
    cd intltool-0.40.3
    ./configure --prefix=/home/deckrider/pidgin251
    make
    make install
    cd ../pidgin-2.5.1
    ./configure --prefix=/home/deckrider/pidgin251
    make
    make install
    cd ../bot-sentry-1.3.0
    make
    make install
    ./configure --prefix=/home/deckrider/pidgin251 PKG_CONFIG_PATH=/home/deckrider/pidgin251/lib/pkgconfig
    make
    make install

    Also, I did NOT have an existing pidgin or gaim or dev headers installed anywhere on my system.

     
  • Sergey

    Sergey - 2008-09-15

    Confirmed! It works as expected sometimes, but sometimes had a problem.
    I can't catch exact sequence yet, but it's related with Authorization
    request-response windows ...

    Will publish sequence & debug window output later...

     
  • Sergey

    Sergey - 2008-09-15
    • status: pending-works-for-me --> open-works-for-me
     
  • Sergey

    Sergey - 2008-09-15

    Debug output

     
  • Sergey

    Sergey - 2008-09-15

    Here is tricky sequence...
    Me (pidgin) - 11354606
    Buddy (kopete) - 494904321

    1. Removed 11354606 from kopete list, quit pidgin, rm -rf ~/.purple
    2. Start /tmp/.../pidgin. Configure for 11354606 account.
    Checked that buddy is removed from privacy list:
    Privacy allow only this users - ok, no 494904321 in this list.
    Block only this users - ok, empty list. Leave this option.
    3. Enable bot sentry plugin,
    add this person to allow list - flag cleared,
    add this person to buddy list - flag cleared,
    policy - grant auth reqests.
    4. Kopete: Add 11354606, send message to him, got auth question.
    5. Kopete: got Auth reqest from 11354606, manually grant it.
    6. Pidgin: no incoming messages yet.
    7. Kopete: send second message. It bypassed bot-sentry now!!
    8. Pidgin: got incoming message.

    Debug output attached.

    File Added: purple-debug.log

     
  • David Everly

    David Everly - 2008-09-15

    This is expexted behavior. When you (auto) approve auth requests, you add the person requesting auth to your buddy list. Once that person is in your buddy list, bot sentry assumes you must know the buddy and does not get involved (since known buddies are not spam).

     
  • David Everly

    David Everly - 2008-09-15
    • status: open-works-for-me --> pending-works-for-me
     
  • Sergey

    Sergey - 2008-09-15

    Don't you think that this makes bot useless?

     
  • Sergey

    Sergey - 2008-09-15
    • status: pending-works-for-me --> open-works-for-me
     
  • David Everly

    David Everly - 2008-09-15
    • status: open-works-for-me --> pending-works-for-me
     
  • David Everly

    David Everly - 2008-09-15

    Bot sentry works with a variety of protocol behavior and user desires. And with respect to auth requests, bot sentry makes available all auth handling options presented by the pidgin api.

    If you don't like the results of configuring bot sentry to always grant auth requests, why not change this setting? (The default is to always ask you what to do.)

     
  • Sergey

    Sergey - 2008-09-15

    Yeah, we've got to point. :)

    Why did we use bot? We want bot to filter out ALL SPAM robots.
    So we do not want to talk with any SPAM robot in anyway.

    If we got an auth request - we don't know is it human or robot yet.
    So we do not want to talk with him, we still wait for correct
    answer on our riddle. But bot should reply with auth-response
    in anyway.

    Auth replies means (I maybe wrong here):
    policy "deny" - don't add me to his list, never show my status to him
    policy "allow" - ok, add me to his list, show him my status

    In both cases we do not need to add him to _our_ list yet.
    We need just answer him with auth-deny or auth-allow
    and continue waiting answer for our riddle.

    I guess that this behaviour was default for previous versions.
    Am I wrong?

     
  • Sergey

    Sergey - 2008-09-15
    • status: pending-works-for-me --> open-works-for-me
     
  • David Everly

    David Everly - 2008-09-16
    • status: open-works-for-me --> closed-works-for-me
     
1 2 > >> (Page 1 of 2)

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks