| Summary: | konversation crash, when writing in a channel with blowfish encryption with very long key | ||
|---|---|---|---|
| Product: | [Applications] konversation | Reporter: | srudloff |
| Component: | encryption | Assignee: | Konversation Bugs <konversation-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | crash | CC: | hein, konversation-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
srudloff
2007-05-05 09:47:07 UTC
The blowfish code in Konversation has just seen revision and a number of bugfixes, related to key management and encoding, in the SVN version. If possible, please re-test with the SVN version. Instructions for how to retrieve the SVN version can be found here: http://konversation.kde.org/wiki/SVN Note: In order for backtraces to be useful, debug symbols need to be installed. Many distributions provide these in separate packages, e.g. a 'konversation-dbg' package. For self-compiled versions or source-based distributions, the advice given in http://www.gentoo.org/proj/en/qa/backtraces.xml broadly applies. Does this still happen for you with Konversation 1.1 or the pre-release KDE 4 port? The Blowfish code has been nearly entirely rewritten for the KDE 4 version and development of the KDE 3 codebase has ceased. |