Project

General

Profile

Blowfish Encryption Draft » History » Version 32

johu, 01/21/2012 10:40 PM
showkey command is merged, TODO->DONE

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 25 johu
* #689 Blowfish Support (since 28.10.2010 in upstream available)
23 18 johu
* #911 DH1080 Key Exchange
24 30 johu
* #1069	showkey command
25 29 johu
* #1045 Crash of missing qca provider plugin
26 1 johu
* #1059 Crash on not decryptable text
27 30 johu
* #61 Encrypted query (closed, will not implemented)
28 5 johu
29 6 johu
h3. Repository
30 6 johu
31 6 johu
The current development state can be found at http://gitorious.org/~johu/quassel/johus-quassel
32 6 johu
33 6 johu
>  *Get the source*
34 23 Datafreak
<pre><code>git clone git://gitorious.org/~johu/quassel/johus-quassel.git
35 28 johu
git checkout -b dh1080 -t origin/dh1080</code></pre>
36 1 johu
37 15 johu
h3. TODO
38 15 johu
39 25 johu
* -Include QCA in build system- Tested in Linux Windows; Need support for *MaxOSX testing*
40 15 johu
* -Cipher implemention- Class imported from Konversation, should works
41 15 johu
* -include cipher in IrcUser and IrcChannel- 
42 15 johu
* -store keys for channel and user in Network-
43 26 johu
* -commands setkey, delkey implementation-
44 17 johu
* -encrypt topic-
45 16 johu
* -decrypt topic-
46 17 johu
* -encrypt channel message-
47 1 johu
* -decrypt channel message-
48 15 johu
* -encrypt query message-
49 19 johu
* -decrypt query message-
50 27 johu
* -extract howto for end user from this wiki site-
51 1 johu
* -gentoo ebuild-
52 32 johu
* -command showkey-
53 28 johu
* command keyx
54 28 johu
* initiliase key exchange
55 28 johu
* react on key exchange
56 15 johu
57 8 johu
h3. Library
58 8 johu
59 31 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. At runtime a QCA provider plugin is needed, for example qca-ossl.
60 10 johu
61 10 johu
h3. Commands
62 10 johu
63 10 johu
a) setting a key for a user or channel 
64 10 johu
65 10 johu
> Usage
66 10 johu
<pre><code>/setkey <nick|channel> <key></code></pre>
67 10 johu
68 10 johu
b) deleting a key for a user or channel
69 1 johu
70 1 johu
> Usage
71 1 johu
<pre><code>/delkey <nick|channel></code></pre>
72 1 johu
73 30 johu
c) show key for a user or channel
74 30 johu
75 30 johu
> Usage
76 30 johu
<pre><code>/showkey <nick|channel></code></pre>
77 30 johu
78 30 johu
d) key exchange for user or channel 
79 30 johu
80 30 johu
> Usage
81 28 johu
<pre><code>/keyx <nick|channel></code></pre>
82 10 johu
83 11 johu
h3. Current Plan
84 11 johu
85 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.
86 12 johu
87 12 johu
The other result of this discussion is this wiki article.
88 11 johu
89 7 johu
h3. Discussion
90 7 johu
91 7 johu
There are two possible ways to implement Blowfish support in Quassel architecture:
92 1 johu
93 11 johu
*a) Client side de-/encryption*
94 7 johu
95 7 johu
!client_deencryption.png!
96 1 johu
97 11 johu
All messages will be de-/encrypted on client side.
98 11 johu
99 11 johu
*Pro*
100 13 johu
* the complete path of messages from one client to an other is encrypted
101 13 johu
* core have nothing to do
102 11 johu
103 11 johu
*Contra*
104 13 johu
* Messages in backlog will be encrypted, that implies on receiving backlog all encrypted messages have to decrypt
105 13 johu
* If key for a channel/user changed, old messages will stay decrypted
106 11 johu
107 14 johu
*b) Core side de- and encryption*
108 7 johu
109 1 johu
!core_deencryption.png!
110 11 johu
111 11 johu
All messages will be de-/encrypted on core.
112 11 johu
113 11 johu
*Pro*
114 13 johu
* Backlog contains all decrypted messages
115 13 johu
* Client do not need to decrypt on receiving backlog
116 13 johu
* Key change doesnt matter
117 13 johu
* Fits better in Quassel architecture
118 11 johu
119 11 johu
*Contra*
120 13 johu
* The path between a core and client is unsecured if SSL is not enabled and it is not a monolitic build.
121 7 johu
122 24 johu
h3. Build Instructions
123 24 johu
* [[Build_Quassel_on_Windows]]
124 20 Datafreak
125 1 johu
h2. References
126 1 johu
127 1 johu
[1] http://en.wikipedia.org/wiki/Blowfish_%28cipher%29
128 5 johu
[2] http://xchat.org/
129 5 johu
[3] http://irssi.org/
130 5 johu
[4] http://www.mirc.com/
131 5 johu
[5] http://fish.secure.la/
132 1 johu
[6] http://konversation.kde.org/
133 8 johu
[7] http://delta.affinix.com/qca/