Please I need help with blowssi/mircrytpion: 3 problems

[KiTTy]

I'm running I'm running: Linux Debian /lenny2 OpenSSL/0.9.8g

1. KEY WITH SPACES: What is the proper way to /blowkey #channel if the key has spaces in it?
Doing this /blowkey #channel i am the key , sets key to: i
Doing this: /blowkey #channel 'i am the key' , sets key to: 'i etc.
I finally just edited the blowssi.conf and put that key in myself- works.

2. NOT DECRYPTING ALL USERS: I can't read all users.. they just aren't decrypted (they can read me).. and for those that I can't read they have before their text: mcps.. if that matters?. Where I have before my text in non cbc key channels: ebc, and in cbc key channels: cbc
example (channel not using cbc: in their key):
<Me{ecb}> testing
<@User1> mcps 47mZ81W/Ra9/NtcTzL0898.Z1KX1.4ItNZ0AOzp9/nsngD.XvAGK0
<@User1> mcps qw/3z./Bl.
<@User1> mcps v.K971Ojq9Wgl606IUzj0it1lL1Bqx3R1oSh39/zXK.JHpOW/
<Me{ecb}> I can't read you
<User2{ecb}> test

3. AUTOLOAD: What is the proper way to have it autoload/or accessible for all users?
I have installed irssi system wide (as root). According to the README to have blowssi autoload:
pico /root/.irssi/startup (this is where it is for me)
put:
/load ~/.irssi/scripts/blowssi.pl

When I start irssi up as a user it didn't autoload.
So then I:
cp /root/blowssi-0.0.2/blowssi.pl /usr/share/irssi/scripts/blowssi.pl
mkdir /usr/share/irssi/scripts/autorun
ln -s /usr/share/irssi/scripts/blowssi.pl /usr/share/irssi/scripts/autorun/blowssi.pl
Still didn't autoload.
I issue the cmd as user: /load ~/.irssi/scripts/blowssi.pl
get error the file not in my home dir. So finally I just set it up in my home dir:
mkdir /home/me/.irssi/scripts
mkdir /home/me/.irssi/scripts/autorun
cp /root/blowssi-0.0.2/blowssi.pl /home/me/.irssi/scripts/blowssi.pl
ln -s /home/me/.irssi/scripts/blowssi.pl /home/me/.irssi/scripts/autorun/blowssi.pl
Still didnt auto load, but it did accept the cmd: /load ~/.irssi/scripts/blowssi.pl

Thank you!

PS. I'm pretty sure I've installed all that is needed: dpkg -l
For perl
perl 5.10.0-19 Larry Wall's Practical Extraction and Report Language
perl-base 5.10.0-19 minimal Perl system
perl-doc 5.10.0-19 Perl documentation
perl-modules 5.10.0-19 Core Perl modules

For Crypt::ircBlowfish
libcrypt-cbc-perl 2.29-1 Implementation of cipher block chaining (CBC) mode
libcrypt-blowfish-perl 2.10-1+b1 Blowfish cryptography for Perl

For Crypt::CBC
libcrypt-blowfish-perl  2.10-1+b1 Blowfish cryptography for Perl
libcrypt-cbc-perl 2.29-1 Implementation of cipher block chaining (CBC) mode

For MIME:Base64
libmime-types-perl 1.24- Perl extension for determining MIME types and Transfer Encoding
perl-modules 5.10.0-19 Core Perl modules

[housetier]

This will be very confusing because we have to deal with so many issues at once...

Regarding system-wide autoload: I assume irrsi does not always work the way documentation says, even if you happen to find documentation.


And it is important to actually quote the whole complete error message and not the user's interpretation of same.

[mouser]

1+2 sound like minor bugs in the plugin and should be easy to fix.

[KiTTy]

Thank you housetier & mouser for the replies.
Ok then lets just solve issue "2. NOT DECRYPTING ALL USERS:" since the others I have found a workaround for.

There were no error msg's that I could see to paste for that, just what I saw in my window.
Is there a place to look on server for any error msgs?

Thank you

[Gothi[c]]

First of all, blowssi needs lots of polishing yet. That's why the version number starts with a zero, followed by a dot, and ... another zero! One of these days I'm going to have to spend a day fixing the ever growing list of bugs,.... soon(tm).

1) just a minor bug in the command handler. Setting it manually in the config file is the best way for now.
2) Firstly, know that there's a known bug in irssi not ENCRYPTING /me actions etc... What you're running into is something I haven't seen before yet. What software was the other end using? Curious that they all start with mcps.. normally stuff is prefixed with +OK unless there's something else I'm not aware of.
3) The irssi man page only mentions ~/.irssi - a configuration/script folder for every user. It makes no mention of a system wide configuration...

[mouser]

the mcps prefix and the +OK prefix should be treated identically.. they serve identical roles and the actual encryption is identical.
basically it's a historical legacy.. mircryption uses mcps by default but can be set to use +OK.
fish uses +OK only.

[KiTTy]

Thank you Gothi[c] for the replies and your time

1.) OK, thank you.

2.) Yes as mouser suggested;
User1 is using mIRC/Mircryption. (the one only one, so far, that I can not read)
User2 is a bot using Mircryption - I can read.
Another user (not on post) using mIRC/Fish- I can read.
And I login again via mIRC/Mircryption and I can read  myself (in my other login shell window).

If you need me to post anything else / do other tests please let me know.

3.) Very new to nix and all its goodies, so I learn as I go I installed it as root then found any user can now type irsssi and it will load and also any user can type /load fish so I presumed the same for blowssi .. never assume haha. So no problem there either. I've created the paths and the copies to fix that.



<mouser> the number you have reached
<mouser> M O U S E R
<mouser> has been disconnected
<mouser> please hang up and try again

[Gothi[c]]

Re 2) If that's the case, then that should be a very simple fix I'll just add mcps as possible prefix

Re 3)

I installed it as root then found any user can now type irsssi and it will load and also any user can type /load fish so I presumed the same for blowssi .. never assume haha. So no problem there either. I've created the paths and the copies to fix that.

Anything in root's .irssi folder won't affect other users, but if you put blowssi in /usr/share/irssi/scripts it should work with just /root as long as there's proper permissions on the script.

[KiTTy]

Great Gothi[c]  Thank you!
I shall give that path a try and: chmod -R 777 /usr/share/irssi/scripts/

[Gothi[c]]

NEVERRRrrrrrrrrrrrrr use 777

Just make sure other users can read+execute it...

[Select]

chmod u=rwx,o=rx,g=rx /usr/share/irssi/scripts/blowssi.pl

Then from any user you still have to /load blowssi.pl

The advantage of putting it in /usr/share/irssi/scripts is that you don't have to type the full path after /load

If you want it to auto-load you still have to put the /load line in the ~/.irssi/startup file of every user using irssi. It would be nice if there was a system-wide startup file, but there isn't afaik....

[Gothi[c]]

All the above is fixed in the latest, just released, blowssi 0.1.0  

[mouser]

Thanks Gothic! 

[KiTTy]

Woweeee Thank You Gothi[c]
I hope to try this out by tomorrow. Can't wait, will round up the victims   

Btw I have tried this beautiful nix IRC chat program called `WeeChat' http://weechat.flashtux.org/
Problem is there isn't any mircryption, blowssi, or fish support so it ended up not being useful for me.
There is a nice script for encryption `crypt.py' by blackpenguin http://weechat.flashtux.org/plugins.php .
But as you know that would only be good for others using the same.

I spoke with blackpenguin about making it fish compatible. He said it would probably be easier, not to mention more secure than fish, to just port blowssi to weechat.
He explained a bit to how, but since I don't know python, etc it's not a path I want to go down right now
"you would have to edit blowssi.pl - the irssi-hooks are easy to find, they all have Irssi in their names.
 you would have to find the similar function for the same thing in weechat's API, and you probably need to adapt the parameters of these functions."

Long question short lol : Is there any chance of having a plugin for WeeChat? Please please with catnip on top? 

btw THANK YOU AGAIN

[Gothi[c]]

Sure, why not.
WeeChat looks fun to try out too, nice find.
I'll give it a shot. Can't tell you when though
Blowssi is written in perl, and weechat seems to have perl scripting support (as well as python and ruby), so it should be fairly easy.
It's not quite as simple as replacing the hooks, as you also have to change the function parameter parsing to however their api works, but it should still be fairly easy.

[Gothi[c]]

It appears that the weechat scripting api for 0.2.6.3 is completely different from the upcomming 0.3 branch. The 0.3 branch will be a complete rewrite, therefore I am going to write it for 0.3, to save myself from having to rewrite it again later. But it won't work with the latest stable then.

[KiTTy]

Again Thank you Gothi[c]!
Fantastic!
btw: 03:31 -!- Irssi: blowssi script 0.1.0 loaded < beautiful, yes
I'm still waiting for my mcps victim to show up, but couldn't wait to post to express my gratitude.
Encryption key with spaces works just fine too.. but of course

Purfect on the WeeChat version as I have installed:
weechat-curses           0.2.6-1+lenny1           
weechat-dev-core         0.3.0-1~dev20090611     
weechat-dev-curses       0.3.0-1~dev20090611     
weechat-dev-plugins      0.3.0-1~dev20090611

At least I hope that is the correct version needed. I will gladly try another version for blowssi
I actually woke up last night thinking hmm I wonder if I should mention I have that version :p

[KiTTy]

mcps victim passed test! Thank you!!
It also help me to solve a reason why a fish encrypted bot won't respond to this user only (mcps).