Skip Menu |
 

This queue is for tickets about the POE-Component-IRC-Plugin-Blowfish CPAN distribution.

Report information
The Basics
Id: 62843
Status: open
Priority: 0/
Queue: POE-Component-IRC-Plugin-Blowfish

People
Owner: johannes [...] plunien.de
Requestors: chrisbeebops.spam [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.01
Fixed in: (no value)



Subject: String Case in Blowfish Key Lookups
Download (untitled) / with headers
text/plain 411b
IRC channel names and nick names are case preserving but are case insensitive. If a user joins channel #Test, they will receive all messages sent to #Test, #TEST, #test, etc... Example $irc->yield( join => $channel ); set_blowfish_key('#Test','channelkey'); PRIVMSG #Test :+OK *blowfish* <-- decoded by plugin PRIVMSG #test :+OK *blowfish* <-- received by users on channel #Test but not decoded by plugin
Download (untitled) / with headers
text/plain 935b
On Mon Nov 08 08:55:05 2010, chrisbeebops wrote: Show quoted text
> IRC channel names and nick names are case preserving but are case > insensitive. If a user joins channel #Test, they will receive all > messages sent to #Test, #TEST, #test, etc... > > Example > > $irc->yield( join => $channel ); > set_blowfish_key('#Test','channelkey'); > > PRIVMSG #Test :+OK *blowfish* <-- decoded by plugin > PRIVMSG #test :+OK *blowfish* <-- received by users on channel #Test > but not decoded by plugin
sorry for the late response. I just tried to join #poe and #POE, but it leads me to the same channel (on irc.perl.org using irssi as a client). I've tried the same on freenode, same result, but same client. I've skimmed the IRC RFC for case sensitivity/insensitivity of channels, but couldnt see anything. Is it possible, that you connect to two different networks and have a channel #Test on one of them and #TEST on the other one? Thanks, plu


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.