<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//TaxonX//DTD Taxonomic Treatment Publishing DTD v0 20100105//EN" "../../nlm/tax-treatment-NS0.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:tp="http://www.plazi.org/taxpub" article-type="research-article" dtd-version="3.0" xml:lang="en">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">109</journal-id>
      <journal-id journal-id-type="index">urn:lsid:arphahub.com:pub:3dc5f44e-8666-58db-bc76-a455210e8891</journal-id>
      <journal-title-group>
        <journal-title xml:lang="en">JUCS - Journal of Universal Computer Science</journal-title>
        <abbrev-journal-title xml:lang="en">jucs</abbrev-journal-title>
      </journal-title-group>
      <issn pub-type="ppub">0948-695X</issn>
      <issn pub-type="epub">0948-6968</issn>
      <publisher>
        <publisher-name>Journal of Universal Computer Science</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.3217/jucs-023-10-0969</article-id>
      <article-id pub-id-type="publisher-id">23601</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Research Article</subject>
        </subj-group>
        <subj-group subj-group-type="scientific_subject">
          <subject>H.4.3 - Communications Applications</subject>
          <subject>H.5.1 - Multimedia Information Systems</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>OnionSIP: Preserving Privacy in SIP with Onion Routing</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Fakis</surname>
            <given-names>Alexandros</given-names>
          </name>
          <email xlink:type="simple">alfa@aegean.gr</email>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Karopoulos</surname>
            <given-names>Georgios</given-names>
          </name>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Kambourakis</surname>
            <given-names>Georgios</given-names>
          </name>
          <xref ref-type="aff" rid="A3">3</xref>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">University of the Aegean, Samos, Greece</addr-line>
        <institution>University of the Aegean</institution>
        <addr-line content-type="city">Samos</addr-line>
        <country>Greece</country>
      </aff>
      <aff id="A2">
        <label>2</label>
        <addr-line content-type="verbatim">National and Kapodistrian University of Athens, Athens, Greece</addr-line>
        <institution>National and Kapodistrian University of Athens</institution>
        <addr-line content-type="city">Athens</addr-line>
        <country>Greece</country>
      </aff>
      <aff id="A3">
        <label>3</label>
        <addr-line content-type="verbatim">Engineering, University of the Aegean, Samos, Greece</addr-line>
        <institution>Engineering, University of the Aegean</institution>
        <addr-line content-type="city">Samos</addr-line>
        <country>Greece</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Alexandros Fakis (<email xlink:type="simple">alfa@aegean.gr</email>).</p>
        </fn>
        <fn fn-type="edited-by">
          <p>Academic editor: </p>
        </fn>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2017</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>28</day>
        <month>10</month>
        <year>2017</year>
      </pub-date>
      <volume>23</volume>
      <issue>10</issue>
      <fpage>969</fpage>
      <lpage>991</lpage>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/E201DEEC-6182-5D16-BE8A-5BEAF63C3A4C">E201DEEC-6182-5D16-BE8A-5BEAF63C3A4C</uri>
      <uri content-type="zenodo_dep_id" xlink:href="https://zenodo.org/record/5505681">5505681</uri>
      <history>
        <date date-type="received">
          <day>21</day>
          <month>03</month>
          <year>2017</year>
        </date>
        <date date-type="accepted">
          <day>20</day>
          <month>10</month>
          <year>2017</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>Alexandros Fakis, Georgios Karopoulos, Georgios Kambourakis</copyright-statement>
        <license license-type="creative-commons-attribution" xlink:href="" xlink:type="simple">
          <license-p>This article is freely available under the J.UCS Open Content License.</license-p>
        </license>
      </permissions>
      <abstract>
        <label>Abstract</label>
        <p>While more and more users turn to IP-based communication technologies, privacy and anonymity remain largely open issues. One of the most prominent VoIP protocols for multimedia session management is SIP which, despite its popularity, suffers from security and privacy aws. As SIP messages are sent in plain text, user data are exposed to intermediate proxies and eavesdroppers. As a result, information about users participating in a call can leak from header data, which cannot be omitted since they are needed for the correct routing of SIP messages to their final destination. Even more, traffic analysis attacks can be mounted with data stemming from lower layers. To redress this kind of problems, privacy can be achieved either by the construction of a lower level tunnel (via the use of SSL or IPsec protocols) or by employing a customtailored solution. However, SSL and IPsec are known for leading to undesirable, non affordable delays, and thus the need for a SIP-oriented solution is preferable. In the context of this article, we evaluate three alternative solutions to encounter the above issues. More specifically, we use two well-known anonymity networks, Tor and I2P, for secluding both caller's and callee's actions by securing SIP messages content. As a third solution, we present our proposal for preserving privacy in SIP signaling, by using an onion-routing approach, where selected sensitive fields of SIP messages are encrypted using either asymmetric or symmetric encryption. We compare these three alternatives in terms of performance, mentioning the pros and cons that come up with each proposal. Our work also presents the reasons why other existing anonymity networks fail to be considered as appropriate for preserving anonymity in SIP.</p>
      </abstract>
    </article-meta>
  </front>
</article>
