Project

General

Profile

Blowfish Encryption Draft » History » Version 17

johu, 02/11/2010 01:43 AM

1 1 johu
h1. Blowfish Encryption
2 1 johu
3 2 johu
{{toc}}
4 2 johu
5 2 johu
h2. Introduction
6 2 johu
7 4 johu
Blowfish is a keyed, symmetric block cipher, designed in 1993 by Bruce Schneier and included in a large number of cipher suites and encryption products. Blowfish provides a good encryption rate in software and no effective cryptanalysis of it has been found to date. However, the Advanced Encryption Standard now receives more attention. Schneier designed Blowfish as a general-purpose algorithm, intended as a replacement for the aging DES and free of the problems and constraints associated with other algorithms. At the time Blowfish was released, many other designs were proprietary, encumbered by patents or were commercial/government secrets. Schneier has stated that, "Blowfish is unpatented, and will remain so in all countries. The algorithm is hereby placed in the public domain, and can be freely used by anyone."[1]
8 2 johu
9 5 johu
h3. IRC Profit
10 1 johu
11 5 johu
Blowfish can be used in IRC to encrypt messages between 2 persons in a query or messages in a channel and the topic too. 
12 1 johu
13 5 johu
h3. Examples
14 5 johu
15 5 johu
* In XChat[2], Irssi[3] and mIRC[4] Blowfish support can be enabled with the FiSH plugin[5].
16 5 johu
* Konversation[6] has a built in Blowfish support
17 5 johu
18 8 johu
h2. Development
19 1 johu
20 5 johu
h3. Related Issues
21 2 johu
22 5 johu
* #689 Blowfish Support (in development)
23 5 johu
* -#61- Encrypted query (closed, will not implemented)
24 5 johu
25 6 johu
h3. Repository
26 6 johu
27 6 johu
The current development state can be found at http://gitorious.org/~johu/quassel/johus-quassel
28 6 johu
29 6 johu
>  *Get the source*
30 6 johu
<pre><code>git clone git://gitorious.org/~johu/quassel/johus-quassel.git</code></pre>
31 1 johu
32 15 johu
h3. TODO
33 15 johu
34 15 johu
* -Include QCA in build system- Tested in Linux *Need support for Windows, MaxOSX testing*
35 15 johu
* -Cipher implemention- Class imported from Konversation, should works
36 15 johu
* -include cipher in IrcUser and IrcChannel- 
37 15 johu
* -store keys for channel and user in Network-
38 15 johu
* -commands setkey, delkey implementation- *have to be tested*
39 17 johu
* -encrypt topic-
40 16 johu
* -decrypt topic-
41 17 johu
* -encrypt channel message-
42 1 johu
* -decrypt channel message-
43 17 johu
* -encrypt query message-
44 15 johu
* -decrypt query message-
45 17 johu
* output messages: -en-, cs, da, de, es, fi, fr, hu, it, nb, ru, sl, tr
46 15 johu
47 8 johu
h3. Library
48 8 johu
49 9 johu
The Blowfish algorithm is implemented in the *QCA* (Qt Cryptographic Architecture)[7] library. QCA works on all plattforms there are supported by QT including Unix, Windows and MacOSX. It is already included in Quassel build system at listed repository above.
50 8 johu
51 10 johu
h3. Commands
52 10 johu
53 10 johu
In first stable release of this feature in Quassel there will be 2 new user commands available.
54 10 johu
55 10 johu
a) setting a key for a user or channel 
56 10 johu
57 10 johu
> Usage
58 10 johu
<pre><code>/setkey <nick|channel> <key></code></pre>
59 10 johu
60 10 johu
b) deleting a key for a user or channel
61 10 johu
62 10 johu
> Usage
63 10 johu
<pre><code>/delkey <nick|channel></code></pre>
64 10 johu
65 11 johu
h3. Current Plan
66 11 johu
67 12 johu
After short discussion in #quassel.de with Sput, krytzz and brot Blowfish encryption will be included in core. See section discussion below for more information. The only contra argument is the unsecure path between remote core and clientvin a untrusted net in case of no ssl connection is present. But the pro argument preponderate to strong. So i will revert the first plan to implement the de-/encryption in client.
68 12 johu
69 12 johu
The other result of this discussion is this wiki article.
70 11 johu
71 7 johu
h3. Discussion
72 7 johu
73 7 johu
There are two possible ways to implement Blowfish support in Quassel architecture:
74 1 johu
75 11 johu
*a) Client side de-/encryption*
76 7 johu
77 7 johu
!client_deencryption.png!
78 1 johu
79 11 johu
All messages will be de-/encrypted on client side.
80 11 johu
81 11 johu
*Pro*
82 13 johu
* the complete path of messages from one client to an other is encrypted
83 13 johu
* core have nothing to do
84 11 johu
85 11 johu
*Contra*
86 13 johu
* Messages in backlog will be encrypted, that implies on receiving backlog all encrypted messages have to decrypt
87 13 johu
* If key for a channel/user changed, old messages will stay decrypted
88 11 johu
89 14 johu
*b) Core side de- and encryption*
90 7 johu
91 1 johu
!core_deencryption.png!
92 11 johu
93 11 johu
All messages will be de-/encrypted on core.
94 11 johu
95 11 johu
*Pro*
96 13 johu
* Backlog contains all decrypted messages
97 13 johu
* Client do not need to decrypt on receiving backlog
98 13 johu
* Key change doesnt matter
99 13 johu
* Fits better in Quassel architecture
100 11 johu
101 11 johu
*Contra*
102 13 johu
* The path between a core and client is unsecured if SSL is not enabled and it is not a monolitic build.
103 7 johu
104 1 johu
h2. References
105 1 johu
106 1 johu
[1] http://en.wikipedia.org/wiki/Blowfish_%28cipher%29
107 5 johu
[2] http://xchat.org/
108 5 johu
[3] http://irssi.org/
109 5 johu
[4] http://www.mirc.com/
110 5 johu
[5] http://fish.secure.la/
111 1 johu
[6] http://konversation.kde.org/
112 8 johu
[7] http://delta.affinix.com/qca/