[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Full-Disclosure] Blowfish&B/tchX
- Subject: Re: [Full-Disclosure] Blowfish&B/tchX
- From: "the.soylent" <the.soylent@xxxxxxxxx>
- Date: Wed, 09 Feb 2005 19:39:50 +0100
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
everybody in the channel had updated their (most-win) clients, most of
them use http://fish.sekure.us
if i post something via ctcp in a channel in quakenet with a L-Bot, i
get a desync message and can't write to channel any longer via ctcp..
example:
- -user(#channel)- #channel test
- -:- #channel Cannot send to channel
- ---------------------------------------------------------------------
Valdis.Kletnieks@xxxxxx schrieb:
| 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....
i does and still do ;)
Milan 't4c' Berger schrieb:
| try reading docs and posting bitchx ML
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCClj2Y86qEhC92cgRAjLLAKCrVZdjwDG6KGqxvmY2EnrMboc4iwCeOf9K
SVnTrzwGJOc5loZP3+SurMU=
=tJXk
-----END PGP SIGNATURE-----
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html