full-disclosure - Blowfish&B/tchX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <200502091718.j19HIUSt010599@turing-police.cc.vt.edu>
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: Blowfish&B/tchX 

On Wed, 09 Feb 2005 18:01:41 +0100, "the.soylent" said:

> i wan`t to use B/tchX (a famous IRC-Client) with the abbility to decrypt
> all written with blowfish.
> OS is Debian-testing (Sarge)
> 
> I have already loaded the right (?) module, with a: /loaddll blowfish.so
> output :
> B/tchX blowfish encryption module v1.0 loaded.
> Adapted from eggdrop by By-Tor
> 
> 
> I can make a key for a #channel with: /encrypt #chan keyword
> output:
> #chan added to the crypt with key keyword
> 
> 
> but when i post, it is just a channelwide ctcp message and what the
> others do write isn`n decrypted...

So you have a client that supports blowfish, and when you turn it on, it
properly sends out the CTCP saying "do this".  Of course, only those other
users on the channel that actually support that CTCP will *do* it.

Have everybody on the channel upgrade their software.  There's no way a client
that doesn't support crypto can encrypt the channel messages....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20050209/2fb67827/attachment.bin