3.3 Cryptography
As mentioned previously, the cryptography will be
done through OpenVPN. There are lots of symmet-
ric algorithms supported by OpenVPN, but we choose
only the algorithms that have the most interesting fea-
tures for our work. The algorithms chosen to ci-
pher the VoIP calls in this work are AES, DES and
BlowFish, that were designed to be block cipher al-
gorithms.
3.3.1 AES
The AES (Advanced Encryption Standard) is a block
cipher cryptographic algorithm, created by Vincent
Rijmen and Joan Daemen for a competition of the
United States government in 2001 (NIST, 2001),
which proposal was to choose a new cryptographic al-
gorithm to be the new default algorithm of the north-
american government to protect secret documents.
In the test scenario proposed, a 128 bits sized key
and 2 operations modes for the AES will be used: the
CBC (Cipher-block chaining) and CFB (Cipher feed-
back).
The objective in using two different operation
modes for AES is to discover whether there are signif-
icant differences in the use of CBC or CFB mode, be-
cause in transmissions in which packages are slightly
smaller in size, like in a VoIP communication, the ten-
dency is that a block cipher algorithm, using CFB op-
eration mode, will have a better performance when
compared with CBC operation mode (Elbayoumy and
Shepherd, 2007).
3.3.2 DES
DES is an algorithm created by IBM in 1976 at the
request of the United States government, and support
keys with only 56 bits long, which can be broken with
brute force attack methods. It is also vulnerable to
techniques of linear cryptanalysis since 1993 (Matsui,
1994).
Because of the importance of DES in the past, it
will be included in the tests to compare it to newer,
faster and more secure cryptographic algorithms.
3.3.3 Blowfish
Blowfish was created in 1993 by Bruce Schneier,
and it is the default cryptographic algorithm used by
OpenVPN. It is an algorithm considered secure be-
cause, as the AES, there are no techniques of crypt-
analysis effective against it nowadays (RSA Security,
2009). The key size supported by Blowfish corre-
sponds to all multiples of 8 between 32 and 448 bits,
thus showing itself a flexible algorithm concerning
key size. In the tests a 128 bits key will be used, which
is the default key size of this algorithm.
3.4 Analysis of the Call Quality
When making VoIP calls, we need a method to an-
alyze each call and evaluate its quality. To ver-
ify the VoIP transmission quality, we will use the
ManageEngine VQManager 6 (AdventNet, 2009), a
VoIP monitoring software. This software is com-
mercial, but free and totally functional to monitor up
to 10 phones/softphones, compatible with SIP and
RTP/RTCP, and that will be enough for our work. The
ManageEngine VQManager 6 provides details about
the voice communications in the network, like jitter,
packet loss, latency and informations directly con-
nected to the call quality, like MOS, that is a metric
calculated from the network data, which determines
the expected VoIP transmission quality.
4 TEST SCENARIOS
The test scenarios will be used to highlight the dif-
ferences among the cryptographic algorithms. We
will create 4 different network scenarios with differ-
ent network bandwidth with these problems: packet
loss, latency, packets out of order and packet dupli-
cation. These network anomalies will be created us-
ing the Netem (Hemminger, 2005) tool, available for
Linux by the collection of utilities called iproute2.
The band limitation will be made by TC (Traffic Con-
trol) tool, that also part of iproute2.
The 4 scenarios were divided in “bad”, “regular”,
“good” and “excellent”, with different features. These
features were determined by measurements of the net-
work conditions in hotels, Wi-Fi hot-spots, and others
locales (Snyder, 2008). The scenarios are:
• Bad: the band is limited to 0.1Mbps, with 60 mil-
liseconds latency, 20 milliseconds jitter, packet
loss of 2%, 1% packets out of order, 1% dupli-
cated packets, and a congestion every 20 seconds
of 30% packet loss and 1.000 milliseconds la-
tency;
• Regular: the band is limited to 0.5Mbps, with
60 milliseconds latency, 20 milliseconds jitter,
packet loss of 2%, 1% packets out of order, 1%
duplicated packages, and a congestion every 20
seconds of 30% packet loss and 1.000 millisec-
onds latency;
• Good: the band is limited to 0.5Mbps, with
45 milliseconds latency, 10 milliseconds jitter,
SECRYPT 2009 - International Conference on Security and Cryptography
146