When communicating between an unbuntu and windows user on yim protocol with
pidgin 2.0 and pidgin-encryption 2.0 locks are experienced when accepting
keys over 1024-bit.
steps to reproduce:
1) generate key > 1024-bit
2) attempt to send message to party with same setup.
3) accept incoming key in any fashion.
4) 50% CPU usage and unresponsive app.
Workaround is to generate a 512-bit certificate whereupon there are only
reported "Error in decryption- asking for resend...". (message does not
retransmit)
Noted symptoms:
1) even with workaround, sending large messages elicits massive quantities
of the described error.
2) occasionally wraps encrypted messages at 37 characters. This
occasionally generates the same error as above but does occasionally
transmit.
example:
lil_kreen: PECRYPT: 1234567890123456789012345678901234567890</fo
lil_kreen: PECRYPT: nt>
Nobody/Anonymous
None
None
Public
|
Date: 2007-11-05 03:20
|
|
Date: 2007-10-22 01:13
|
| Field | Old Value | Date | By |
|---|---|---|---|
| status_id | Pending | 2007-11-05 03:20 | sf-robot |
| close_date | 2007-10-22 01:13 | 2007-11-05 03:20 | sf-robot |
| status_id | Open | 2007-10-22 01:13 | obobo |
| resolution_id | None | 2007-10-22 01:13 | obobo |
| close_date | - | 2007-10-22 01:13 | obobo |