<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:foaf="https://xmlns.com/foaf/0.1/" xmlns:og="https://ogp.me/ns#" xmlns:rdfs="https://www.w3.org/2000/01/rdf-schema#" xmlns:schema="https://schema.org/" xmlns:sioc="https://rdfs.org/sioc/ns#" xmlns:sioct="https://rdfs.org/sioc/types#" xmlns:skos="https://www.w3.org/2004/02/skos/core#" xmlns:xsd="https://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/tag/wickr">
  <channel>
    <title>Wickr</title>
    <link>https://www.linuxjournal.com/tag/wickr</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>Wickr: Redefining the Messaging Platform, an Interview with Co-Founder, Chris Howell</title>
  <link>https://www.linuxjournal.com/content/wickr-redefining-messaging-platform-interview-co-founder-chris-howell</link>
  <description>  &lt;div data-history-node-id="1340692" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/wickrlogo.jpg" width="555" height="542" alt="wickr logo" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/petros-koutoupis" lang="" about="https://www.linuxjournal.com/users/petros-koutoupis" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Petros Koutoupis&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
In the modern era, messaging applications are a constant target for
attackers,
exposing vulnerabilities, disclosing sensitive information of nation states
and insider-employee inappropriate behaviors or practices. There is a
constant need to prioritize one's cybersecurity and upgrade one's
infrastructure to the latest and greatest of defensive technologies.
However, the messaging tools that these same organizations tend to rely on
often are the last to be secured, if at all. This is where Wickr comes in.
Wickr is an instant-messaging application and platform offering end-to-end
encryption and content-expiring messages. Its parent company of the same
name takes security seriously and has built a product to showcase that. I
was able chat with co-founder and CTO, Chris Howell, who was
gracious enough to provide me with more information on what Wickr can achieve,
how it works and who would benefit from it.
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;Petros Koutoupis:&lt;/strong&gt; Please introduce yourself and tell us
about your role
at Wickr.
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;Chris Howell:&lt;/strong&gt; I'm co-founder/CTO and responsible for
technical strategy, security and product design. You can read my full bio
&lt;a href="https://wickr.com/wickr_employees/chris-howell"&gt;here&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;Petros:&lt;/strong&gt; What do you see as a weak point in today's messaging
apps?
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;Chris:&lt;/strong&gt; By far, at least when it comes to security, the weak
point of virtually all messaging apps to date (and all other apps and
services, really) is that they're built with the assumption that users will
have to trust the service. The problem with that way of thinking is can
we really trust the service? That's not to say there are bad people running
them, necessarily, but how many breaches (for example, Equifax 2017) or abuses
(for example, Snapchat 2019) do we need to see to answer that question? Once the
service is built that way, messaging users generally suffer in two ways.
First, at some key point on their way to the recipient, messages are
readable by some number of folks beyond the recipient. Now, the service
typically will point to various security certifications and processes to
make us feel okay about that, but in most cases where there are humans
involved, what can happen will happen, and whatever controls are put in place
to limit access to user data amount to little more than a pinky
promise—which when broken, of course, leaves the user with a loss of privacy and
security. Second, having been so trusted, the service typically prioritizes
"virility" and its own growth over the users' need to control their own
data, leading to behavior like scanning message content for marketing
purposes, retaining messages longer than necessary, and abusing contacts to
aid the growth of the service.
&lt;/p&gt;

&lt;p&gt;
&lt;strong&gt;Petros:&lt;/strong&gt; How does Wickr help address that?
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/wickr-redefining-messaging-platform-interview-co-founder-chris-howell" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Fri, 14 Jun 2019 11:30:00 +0000</pubDate>
    <dc:creator>Petros Koutoupis</dc:creator>
    <guid isPermaLink="false">1340692 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
