Henning fishy

Comments and changes to this ticket

• 

  Henning Kiel January 6th, 2009 @ 01:58 AM

  10/27/07 06:20:00 changed by hennk

  Have you tried quoting the password, ie.

  /setkey "pass with spaces"

  (in reply to: ↑ 1 ; follow-up: ↓ 3 ) 10/27/07 08:25:37 changed by black_vega@gmx.net

  Replying to hennk:

  Have you tried quoting the password, ie. /setkey "pass with spaces"

  Now it stores the Key but there is the sam problem like when i store it in the keychain by hand (incompatible encoding).

  (in reply to: ↑ 2 ; follow-up: ↓ 4 ) 10/27/07 17:27:08 changed by anonymous

  Replying to black_vega@gmx.net:

  Now it stores the Key but there is the sam problem like when i store it in the keychain by hand (incompatible encoding).

  If the message is correctly decrypted, you shouldn't have to worry much about this messsage.

  "Incompatible encoding" is a message from Colloquy itself, not FiSHy. It means, that the sender is using another encoding of the text (which doesn't have anything to do with encryption) than what you have selected for the active channel. You can change the default encoding in the preferences, and the currently used encoding for the active channel in the toolbar.

  If the message doesn't get decrypted correctly then there's probably another problem.

  (in reply to: ↑ 3 ; follow-up: ↓ 5 ) 10/29/07 00:54:37 changed by anonymous

  Changing the encoding doesnt fix it at all. I tried it with a sender i set up, without encryption: no problem, encryption without whitespaces also work well, encryption with whitespaces it get the failure.

  So it is no bug in colloquy.

  (in reply to: ↑ 4 ) 10/29/07 16:52:48 changed by hennk

  status changed from new to assigned. Replying to anonymous:

  Changing the encoding doesnt fix it at all. I tried it with a sender i set up, without encryption: no problem, encryption without whitespaces also work well, encryption with whitespaces it get the failure. So it is no bug in colloquy.

  Could you try to describe exactly what you are doing to reproduce this bug? All commands entered in Colloquy, what passwords you use, what you send and what you receive.

  While investigating this, I discovered a big bug, filed as #8, which might be the problem in this case, too. Could you please have a look, if the channel/nickname appears in another password saved in you Keychain? You can search for arbitrary text in Keychain Access.app using the top-right search box.

  Did you get a warning during the first /setkey, that Colloquy wants to access an entry in Keychain?

  10/30/07 11:03:01 changed by hennk

  (From black_vega@gmx.net)

  O.k. here is what i did to reproduce the bug. First i establish a normal IRC Connection to some irc server, like irc.euirc.net and enter some empty room.

  On the other Side of the line i startet an XChat (Linux) with fish support.

  Now i set the fishkey to test.test by using the Command /setkey test.test and it works. Now i set the fishkey to test test by using the Command /setkey "test test" and it works, so the spaces doesent seem to be the real problem.

  Now i set the fishkey to "12wsayskjwfa423897´165 9/5v 6v 21 56" by using the Command /setkey "12wsayskjwfa423897´165 9/5v 6v 21 56" and it fails, if i Type test in Colloquy XChat recieves !Ä:Y3øo and the other way when XChat types test i recieve \6ùênÆè (inkompatible Kodierung)

  And now comes the trick and maybe the needed hint for a fix, if i use this key "12wsayskjwfa423897´165 9/5v 6v" (i removes the last four chars) it works.

  I get no errors when Colloquy tries to enter the Keychain

• 

  Henning Kiel January 6th, 2009 @ 02:09 AM

  • State changed from “new” to “open”