Refine instant messenger section (centralized, federated, peer to peer)
This commit is contained in:
Daniel Gray
parent
e4cc828a35
commit
b0e178f4d1
|
|
@ -1,64 +1,264 @@
|
|||
<h1 id="im" class="anchor"><a href="#im"><i class="fas fa-link anchor-icon"></i></a> Encrypted Instant Messenger</h1>
|
||||
|
||||
<div class="alert alert-warning" role="alert">
|
||||
<strong>If you are currently using an Instant Messenger like Telegram, LINE, Viber, <a href="https://www.eff.org/deeplinks/2016/10/where-whatsapp-went-wrong-effs-four-biggest-security-concerns">WhatsApp</a>, or plain SMS you should pick an alternative here.</strong>
|
||||
<div>
|
||||
<p>We only recommend instant messenger programs or apps that support <a href="https://en.wikipedia.org/wiki/End-to-end_encryption">end-to-end encryption (E2EE)</a>. When E2EE is used, all transmissions (messages, voice, video, etc.) are encrypted <strong>before</strong> they are sent from your device. E2EE protects both the authenticity and confidentiality of the transmission as they pass through any part of the network (servers, etc.).</p>
|
||||
|
||||
<p>All the client programs/apps we chose are <a href="https://en.wikipedia.org/wiki/Free_and_open-source_software">free and open-source software</a> unless otherwise mentioned. This to ensure that the code can be independently verified by experts now and in the future.</p>
|
||||
|
||||
<p>We have described the three main types of messaging programs that exist: Centralized, Federated and Peer-to-Peer (P2P), with the advantages and disadvantages of each.</p>
|
||||
|
||||
<h2 id="centralized" class="anchor"><a href="#centralized"><i class="fas fa-link anchor-icon"></i></a> Centralized</h2>
|
||||
|
||||
<p>Centralized messengers are those where every participant is on the same server or network of servers controlled by the same organization.</p>
|
||||
|
||||
<h3>Advantages</h3>
|
||||
<ul>
|
||||
<li>New features and changes can be implemented more quickly.</li>
|
||||
<li>Easier to get started with and to find contacts.</li>
|
||||
</ul>
|
||||
|
||||
<h3>Disadvantages</h3>
|
||||
<ul>
|
||||
<li>Centralized services could be more susceptible to <a href="#exploiting-centralized-networks">legislation requiring backdoor access</a>.</li>
|
||||
<li>Can include <a href="https://drewdevault.com/2018/08/08/Signal.html">restricted control or access</a>. This can include things like:</li>
|
||||
<ul>
|
||||
<li>Being <a href="https://github.com/LibreSignal/LibreSignal/issues/37#issuecomment-217211165">forbidden from connecting third-party clients</a> to the centralized network that might provide for greater customization or better user experience. Often defined in Terms and Conditions of usage.</li>
|
||||
<li>Poor or no documentation for third-party developers.</li>
|
||||
</ul>
|
||||
<li>The <a href="https://blog.privacytools.io/delisting-wire">ownership</a>, privacy policy, and operations of the service can change easily when a single entity controls it, potentially compromising the service later on.</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
<div class="alert alert-warning" role="alert">
|
||||
<strong>If you are currently using an Instant Messenger like Telegram, LINE, Viber, <a href="https://www.eff.org/deeplinks/2016/10/where-whatsapp-went-wrong-effs-four-biggest-security-concerns">WhatsApp</a>, or plain SMS, you should pick an alternative here.</strong></div>
|
||||
|
||||
{% include cardv2.html
|
||||
title="Signal"
|
||||
image="/assets/img/tools/Signal.png"
|
||||
description="Signal is a mobile app developed by Open Whisper Systems. The app provides instant messaging, as well as voice and video calling.
|
||||
All communications are end-to-end encrypted. Signal is free and open source."
|
||||
labels="success:VoIP"
|
||||
website="https://signal.org/"
|
||||
forum="https://forum.privacytools.io/t/discussion-signal/664"
|
||||
github="https://github.com/signalapp"
|
||||
windows="https://signal.org/download/"
|
||||
mac="https://signal.org/download/"
|
||||
linux="https://signal.org/download/"
|
||||
googleplay="https://play.google.com/store/apps/details?id=org.thoughtcrime.securesms"
|
||||
android="https://signal.org/android/apk/#apk-danger"
|
||||
ios="https://apps.apple.com/us/app/signal-private-messenger/id874139669"
|
||||
{%
|
||||
include cardv2.html
|
||||
title="Signal"
|
||||
image="/assets/img/tools/Signal.png"
|
||||
description='Signal is a mobile app developed by Signal Messenger LLC. The app provides instant messaging, as well as voice and video calling. All communications are E2EE unless you choose to send as SMS. Its protocol has also been <a href="https://eprint.iacr.org/2016/1013.pdf">indepedently audited (PDF)</a>'
|
||||
labels="warning:<a>Requires phone number</a>:Signal requires your phone number as an personal identifier which means anyone you communicate with will see it.|success:VoIP"
|
||||
website="https://signal.org/"
|
||||
forum="https://forum.privacytools.io/t/discussion-signal/664"
|
||||
github="https://github.com/signalapp"
|
||||
windows="https://signal.org/download/"
|
||||
mac="https://signal.org/download/"
|
||||
linux="https://signal.org/download/"
|
||||
googleplay="https://play.google.com/store/apps/details?id=org.thoughtcrime.securesms"
|
||||
android="https://signal.org/android/apk/#apk-danger"
|
||||
ios="https://apps.apple.com/app/signal-private-messenger/id874139669"
|
||||
%}
|
||||
|
||||
<h3>Complete Comparison</h3>
|
||||
<ul>
|
||||
<li><a href="https://securechatguide.org/effguide.html">securechatguide.org</a> - Guide to Choosing a Messenger.</li>
|
||||
<li><a href="https://www.securemessagingapps.com/">securemessagingapps.com</a> - Secure Messaging Apps Comparison.</li>
|
||||
<li><a href="https://www.thinkprivacy.io/messengers.html">thinkprivacy.io</a> - Simple Secure Messaging Apps Comparison.</li>
|
||||
</ul>
|
||||
{%
|
||||
include cardv2.html
|
||||
title="Keybase"
|
||||
image="/assets/img/tools/keybase.png"
|
||||
description='Keybase provides a hosted team chat with E2EE. Its protocol has also been <a href="https://keybase.io/docs-assets/blog/NCC_Group_Keybase_KB2018_Public_Report_2019-02-27_v1.3.pdf">indepedently audited (PDF)</a>. Keybase can help you prove you own social media accounts though the use of cryptographic signing of "<a href="https://en.wikipedia.org/wiki/Keybase#Identity_proofs">identity proofs</a>".'
|
||||
labels="warning:<a href=//github.com/keybase/client/issues/6374>Warning</a>:This software relies on a closed-source central server."
|
||||
website="https://keybase.io/"
|
||||
forum="https://forum.privacytools.io/t/discussion-keybase/1224"
|
||||
tor="http://keybase5wmilwokqirssclfnsqrjdsi7jdir5wy7y7iu3tanwmtp6oid.onion/"
|
||||
github="https://github.com/Keybase"
|
||||
windows="https://keybase.io/docs/the_app/install_windows"
|
||||
mac="https://keybase.io/docs/the_app/install_macos"
|
||||
linux="https://keybase.io/docs/the_app/install_linux"
|
||||
freebsd="https://www.freshports.org/security/keybase/"
|
||||
googleplay="https://play.google.com/store/apps/details?id=io.keybase.ossifrage"
|
||||
ios="https://apps.apple.com/app/keybase-crypto-for-everyone/id1044461770"
|
||||
firefox="https://addons.mozilla.org/firefox/addon/keybase-for-firefox/"
|
||||
chrome="https://chrome.google.com/webstore/detail/keybase-for-reddit/ognfafcpbkogffpmmdglhbjboeojlefj"
|
||||
%}
|
||||
|
||||
<div>
|
||||
<h2 id="federated" class="anchor"><a href="#federated"><i class="fas fa-link anchor-icon"></i></a> Federated</h2>
|
||||
|
||||
<p>Federated messengers use multiple, independent servers that are able to talk to each other (email is one example of a federated service). Federation allows system administrators to control their own server and still be a part of the larger communications network.</p>
|
||||
|
||||
<h3>Advantages</h3>
|
||||
<ul>
|
||||
<li>Allows for greater control over your own data when running your own server.</li>
|
||||
<li>Allows you to choose who to trust your data with by choosing between multiple "public" servers.</li>
|
||||
<li>Often allows for third party clients which can provide a more native, customized, or accessible experience.</li>
|
||||
<li>Generally a less juicy target for governments wanting <a href="#exploiting-centralized-networks">backdoor access to everything</a> as the trust is decentralized. The server may be hosted independently from the organization developing the software.</li>
|
||||
<li>Server software can be verified that it matches public source code, assuming you have access to the server or you trust the person who does (eg family member)</li>
|
||||
<li>Third-party developers can contribute code and add new features, instead of waiting for a private development team to do so.</li>
|
||||
</ul>
|
||||
|
||||
<h3>Disadvantages</h3>
|
||||
<ul>
|
||||
<li>Adding new features is more complex, because these features need to be standardized and tested to ensure they work with all servers on the network.</li>
|
||||
<li>Some metadata may be available. Information like "who is talking to whom," but not actual message content if E2EE is used.</li>
|
||||
<li>Federated servers generally require trusting your server's administrator. They may be a hobbyist or otherwise not a "security professional," and may not serve standard documents like a privacy policy or terms of service detailing how your data is utilized.</li>
|
||||
<li>Server administrators sometimes choose to block other servers, which are a source of unmoderated abuse or break general rules of accepted behavior. This will hinder your ability to communicate with users on those servers.</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
{%
|
||||
include cardv2.html
|
||||
title="Matrix"
|
||||
image="/assets/img/tools/Matrix.png"
|
||||
image-dark="/assets/img/tools/Matrix-dark.png"
|
||||
description='<a href="https://matrix.org/docs/guides/introduction">Matrix</a> is an open-source project that publishes the <a href="https://matrix.org/docs/spec">Matrix open standard</a> for secure, decentralized, real-time communication.<br />
|
||||
<a href="https://en.wikipedia.org/wiki/Riot.im">Riot.im</a> is the popular reference client produced by the Matrix.org team. It offers optional E2EE for 1:1 and group conversations that <strong>must</strong> be turned on by the user. (This can be done by clicking on the toggle switch which is accessed by clicking the room name or user name of the chat → Security & Privacy → Encrypted). In the future it will be <a href="https://github.com/vector-im/riot-web/issues/6779">on by default.</a>'
|
||||
website="https://about.riot.im/"
|
||||
forum="https://forum.privacytools.io/t/discussion-riot-im/665/"
|
||||
github="https://github.com/vector-im/riot-web/"
|
||||
windows="https://riot.im/download/desktop/"
|
||||
mac="https://riot.im/download/desktop/"
|
||||
linux="https://riot.im/download/desktop/"
|
||||
fdroid="https://f-droid.org/repository/browse/?fdid=im.vector.alpha"
|
||||
googleplay="https://play.google.com/store/apps/details?id=im.vector.app"
|
||||
ios="https://itunes.apple.com/app/vector.im/id1083446067"
|
||||
web="https://riot.im/app/"
|
||||
%}
|
||||
|
||||
<div>
|
||||
<h4>Worth Mentioning</h4>
|
||||
|
||||
<ul>
|
||||
<li>Other <a href="https://matrix.org/clients">Matrix</a> clients, that may however be less feature complete than Riot.im.</li>
|
||||
<li><a href="https://xmpp.org/about">XMPP</a> (Extensible Messaging and Presence Protocol) is an open-source communications protocol that began development in 1999. Since then, XMPP has been extended by the publishing of XEPs (XMPP Extension Protocols). <a href="https://conversations.im/omemo/">OMEMO</a> is the most popular XEP (XMPP extension) for E2EE. Unlike Matrix, clients are only developed by the community and not by the foundation itself. <span class="badge badge-warning" data-toggle="tooltip" title="Inconsistent E2EE:VoIP and file transfers/names may not be end-to-end encrypted.">Warning</span></li>
|
||||
<ul>
|
||||
<li><a href="https://gajim.org/">Gajim</a></li>
|
||||
<li><a href="https://conversations.im">Conversations</a></li>
|
||||
<li><a href="https://siskin.im/">Siskin</a></li>
|
||||
<li>Other <a href="https://omemo.top">OMEMO</a> capable clients for XMPP.</li>
|
||||
</ul>
|
||||
<li><a href="https://www.kontalk.org">Kontalk</a> is a community-driven instant messaging network based on XMPP.</li>
|
||||
</ul>
|
||||
</ul>
|
||||
|
||||
<h2 id="peer-to-peer" class="anchor"><a href="#peer-to-peer"><i class="fas fa-link anchor-icon"></i></a> Peer to Peer (P2P)</h2>
|
||||
|
||||
<p>Peer-to-Peer instant messengers connect directly to each other without requiring third-party servers. Clients (peers) usually find each other through the use of a <a href="https://en.wikipedia.org/wiki/Distributed_computing">distributed computing</a> network. Examples of this include <a href="https://en.wikipedia.org/wiki/Distributed_hash_table">DHT (distributed hash table)</a> (used with technologies like <a href="https://en.wikipedia.org/wiki/BitTorrent_(protocol)">torrents</a> and <a href="https://en.wikipedia.org/wiki/InterPlanetary_File_System">IPFS</a>, for example), or <a href="https://en.wikipedia.org/wiki/Ethereum">Ethereum</a>'s <a href="https://github.com/ethereum/wiki/wiki/Whisper">Whisper</a> protocol (used with some newer DApps). Another approach is proximity based networks, where a connection is established over WiFi or Bluetooth (for example, Briar or the <a href="https://www.scuttlebutt.nz">Scuttlebutt</a> social networking protocol). Once a peer has found a route to its contact via any of these methods, a direct connection between them is made.</p>
|
||||
|
||||
|
||||
<h3>Worth Mentioning</h3>
|
||||
<h3>Advantages</h3>
|
||||
<ul>
|
||||
<li>Minimal information is exposed to third parties.</li>
|
||||
<li>Modern P2P platforms implement end-to-end encryption by default. There are no servers that could potentially intercept and decrypt your transmissions, unlike centralized and federated models.</li>
|
||||
</ul>
|
||||
|
||||
<ul>
|
||||
<li><a href="https://briarproject.org/">Briar</a> - An ultra-secure peer-to-peer instant messenger that connects to contacts via Direct Wi-Fi, Bluetooth, or Tor over the internet, keeping its users protected from surveillance and censorship.</li>
|
||||
<li><a href="https://about.riot.im/">Riot</a> - An open-source, federated messenger that utilizes the Matrix protocol. This application is primarily recommended as a large group/team chat solution. While Riot has the ability to perform 1-on-1 communications we believe there are better solutions for direct communications.</li>
|
||||
<li><a href="https://retroshare.cc/">RetroShare</a> - An end-to-end encrypted instant messaging and voice/video call client. RetroShare supports both TOR and I2P. </li>
|
||||
<li><a href="https://xmpp.org/">XMPP</a> - Federated instant messaging protocol with <a href="https://conversations.im/omemo/">OMEMO</a>, OTR, or OpenPGP end-to-end encryption:</li>
|
||||
<ul>
|
||||
<li><a href="https://conversations.im/">Conversations</a> (Android) - An open-source Jabber/XMPP client for Android 4.4+ smartphones. <span class="badge badge-success">OMEMO</span></li>
|
||||
<li><a href="https://gajim.org/">Gajim</a> (FreeBSD, Linux, Windows) - An open-source fully featured XMPP client. <span class="badge badge-success">OMEMO</span></li>
|
||||
<li><a href="https://monal.im/">Monal</a> (iOS, MacOS) - An XMPP client in active development. <span class="badge badge-success">OMEMO</span> <span class="badge badge-success">VoIP</span></li>
|
||||
<li><a href="https://omemo.top/">Other OMEMO-ready clients</a>.</li>
|
||||
</ul>
|
||||
<li><a href="https://www.kontalk.org/">Kontalk</a> - A community-driven instant messaging network. Supports end-to-end encryption. Both client-to-server and server-to-server channels are fully encrypted.</li>
|
||||
<li><a href="https://keybase.io/">Keybase</a> - <span class="badge badge-warning" data-toggle="tooltip" title="This software relies on a closed-source central server.">Warning</span> End-to-end encrypted messaging with social verification.</li>
|
||||
<li><a href="https://status.im/">Status</a> - <span class="badge badge-warning">Experimental</span> A free and open-source, peer-to-peer, encrypted instant messanger with support for DAPPs.</li>
|
||||
<li> <a href="https://tox.chat/">Tox</a> - <span class="badge badge-warning">Experimental</span> A free and open-source, peer-to-peer, encrypted instant messaging, and video calling software. <span class="badge badge-success">VoIP</span></li>
|
||||
<li><a href="https://jami.net/">Jami (formerly Ring/SFLphone)</a> - Gives you full control over your communications and an unmatched level of privacy. Jami has text messaging, video and audio calls, file transfer, and video conferencing. <span class="badge badge-success">VoIP</span></li>
|
||||
</ul>
|
||||
<h3>Disadvantages</h3>
|
||||
<ul>
|
||||
<li>Reduced feature set:</li>
|
||||
<ul>
|
||||
<li>Messages can only be sent when both peers are online, however, your client may store messages locally to wait for the contact to return online.</li>
|
||||
<li>Generally increases battery usage on mobile devices, because the client must stay connected to the distributed network to learn about who is online.</li>
|
||||
</ul>
|
||||
<li>Your <a href="https://en.wikipedia.org/wiki/IP_address">IP address</a> and that of the contacts you're communicating with may be visible if you do not use the software in conjunction with a <a href="/software/networks">self contained network</a>, such as <a href="https://www.torproject.org">Tor</a> or <a href="https://geti2p.net/">I2P</a>. Many countries have some form of mass surveillance and/or metadata retention.</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
{%
|
||||
include cardv2.html
|
||||
title="Briar"
|
||||
image="/assets/img/tools/Briar.png"
|
||||
description="Encrypted instant messenger that connects to contacts via Wi-Fi, Bluetooth, or Tor over the internet to synchronize messages. Technology such as this has proven to be useful when Internet availability is an issue, such as in times of crisis."
|
||||
website="https://briarproject.org"
|
||||
forum="https://forum.privacytools.io/t/discussion-briar/2114"
|
||||
gitlab="https://code.briarproject.org/briar/briar"
|
||||
fdroid="https://f-droid.org/packages/org.briarproject.briar.android/"
|
||||
googleplay="https://play.google.com/store/apps/details?id=org.briarproject.briar.android"
|
||||
%}
|
||||
|
||||
<h3>Related Information</h3>
|
||||
{%
|
||||
include cardv2.html
|
||||
title="Jami"
|
||||
image="/assets/img/tools/Jami.png"
|
||||
description="Encrypted instant messaging and video calling software. Uses <a href=//jami.net/improving-performance-and-security-with-tls-1-3/>TLS 1.3</a> for encryption."
|
||||
labels="success:VoIP"
|
||||
website="https://jami.net/"
|
||||
forum="https://forum.privacytools.io/t/discussion-jami/2116"
|
||||
gitlab="https://git.jami.net/savoirfairelinux"
|
||||
windows="https://jami.net/download-jami-windows"
|
||||
mac="https://jami.net/download-jami-macos"
|
||||
linux="https://jami.net/download-jami-linux"
|
||||
fdroid="https://f-droid.org/packages/cx.ring/"
|
||||
googleplay="https://play.google.com/store/apps/details?id=cx.ring"
|
||||
ios="https://itunes.apple.com/app/ring-a-gnu-package/id1306951055?mt=8"
|
||||
%}
|
||||
|
||||
<ul>
|
||||
<li><a href="https://firstlook.org/theintercept/2015/07/14/communicating-secret-watched/">Chatting in Secret While We're All Being Watched - firstlook.org</a></li>
|
||||
<li><a href="https://signal.org/android/apk/">Advanced users with special needs can download the Signal APK directly. Most users should not do this under normal circumstances.</a></li>
|
||||
<li>Independent security audits</li>
|
||||
<ul>
|
||||
<li><a href="https://eprint.iacr.org/2016/1013.pdf">A Formal Security Analysis of the Signal Messaging Protocol (2019)</a> by Katriel Cohn-Gordon, Cas Cremers, Benjamin Dowling, Luke Garratt and Douglas Stebila</li>
|
||||
<li><a href="https://keybase.io/docs-assets/blog/NCC_Group_Keybase_KB2018_Public_Report_2019-02-27_v1.3.pdf">Keybase's Protocol Security Review (2019)</a> by <a href="https://www.nccgroup.trust/">NCC Group</a></li>
|
||||
</ul>
|
||||
</ul>
|
||||
{%
|
||||
include cardv2.html
|
||||
title="qTox"
|
||||
image="/assets/img/tools/qtox.png"
|
||||
image-dark="/assets/img/tools/qtox-dark.png"
|
||||
description='Encrypted instant messaging and video calling software. Uses its <a href="https://toktok.ltd/spec.html"> own encryption protocol</a> that has not yet been officially audited by cryptographers.'
|
||||
labels="warning:<a href=//tox.chat/download.html#warning>Experimental</a>:Encryption has not been audited by professional cryptographers|success:VoIP"
|
||||
website="https://tox.chat"
|
||||
forum="https://forum.privacytools.io/t/discussion-tox/2115"
|
||||
github="https://github.com/qTox/qTox"
|
||||
windows="https://tox.chat/download.html#oses"
|
||||
mac="https://tox.chat/download.html#oses"
|
||||
linux="https://tox.chat/download.html#oses"
|
||||
%}
|
||||
|
||||
<div>
|
||||
<h4>Worth Mentioning</h4>
|
||||
|
||||
<ul>
|
||||
<li><a href="https://status.im">Status.im</a> - Encrypted instant messenger with an integrated <a href="https://en.wikipedia.org/wiki/Ethereum">Ethereum</a> wallet (cryptocurrency) that also includes support for <a href="https://our.status.im/tag/dapps">DApps (decentralized apps)</a> (web apps in a curated store). Uses the <a href="https://blog.enuma.io/update/2018/08/08/decentralized-application-messaging-with-whisper.html">Whisper protocol</a> for P2P communication. <span class="badge badge-warning">Experimental</span></li>
|
||||
<li><a href="https://retroshare.cc">Retroshare</a> - Encrypted instant messaging and voice/video call client. RetroShare supports both <a href="https://www.torproject.org/">Tor</a> and <a href="https://geti2p.net">I2P</a>.</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="exploiting-centralized-networks" class="anchor">
|
||||
<a href="#exploiting-centralized-networks">
|
||||
<i class="fas fa-link anchor-icon"></i>
|
||||
</a>
|
||||
Recent news about breaking E2EE on centralized instant messengers
|
||||
</h3>
|
||||
|
||||
<h5>November 2019</h5>
|
||||
<ul>
|
||||
<li><a href="https://www.reuters.com/article/us-interpol-encryption-exclusive-idUSKBN1XR0S7">Exclusive: Interpol plans to condemn encryption spread, citing predators, sources say (Reuters)</a></li>
|
||||
<li><a href="https://arstechnica.com/tech-policy/2019/11/think-of-the-children-fbi-sought-interpol-statement-against-end-to-end-crypto/">Think of the children: FBI sought Interpol statement against end-to-end crypto (ArsTechnica)</a></li>
|
||||
</ul>
|
||||
|
||||
<h5>October 2019</h5>
|
||||
<ul>
|
||||
<li><a href="https://www.eff.org/deeplinks/2019/10/open-letter-governments-us-uk-and-australia-facebook-all-out-attack-encryption">The Open Letter from the Governments of US, UK, and Australia to Facebook is An All-Out Attack on Encryption (EFF)</a></li>
|
||||
<li><a href="https://arstechnica.com/tech-policy/2019/10/the-broken-record-why-barrs-call-against-end-to-end-encryption-is-nuts/">The broken record: Why Barr’s call against end-to-end encryption is nuts (ArsTechnica)</a></li>
|
||||
<li><a href="https://arstechnica.com/information-technology/2019/10/ag-barr-is-pushing-facebook-to-backdoor-whatsapp-and-halt-encryption-plans">US wants Facebook to backdoor WhatsApp and halt encryption plans (ArsTechnica)</a></li>
|
||||
</ul>
|
||||
|
||||
<h5>August 2019</h5>
|
||||
<ul>
|
||||
<li><a href="https://arstechnica.com/tech-policy/2019/08/post-snowden-tech-became-more-secure-but-is-govt-really-at-risk-of-going-dark">Post Snowden tech became more secure, but is government really at risk of going dark? (ArsTechnica)</a></li>
|
||||
</ul>
|
||||
|
||||
<h5>July 2019</h5>
|
||||
<ul>
|
||||
<li><a href="https://techcrunch.com/2019/07/23/william-barr-consumers-security-risks-backdoors/">US attorney general William Barr says Americans should accept security risks of encryption backdoors (TechCrunch)</a></li>
|
||||
<li><a href="https://www.theregister.co.uk/2019/07/23/us_encryption_backdoor/">Low Barr: Don't give me that crap about security, just put the backdoors in the encryption, roars US Attorney General (The Register)</a></li>
|
||||
</ul>
|
||||
|
||||
<h5>May 2019</h5>
|
||||
<ul>
|
||||
<li><a href="https://www.theguardian.com/uk-news/2019/may/30/apple-and-whatsapp-condemn-gchq-plans-to-eavesdrop-on-encrypted-chats">Apple and WhatsApp condemn GCHQ plans to eavesdrop on encrypted chats (The Guardian)</a></li>
|
||||
</ul>
|
||||
|
||||
<h5>January 2019</h5>
|
||||
<ul>
|
||||
<li><a href="https://www.justsecurity.org/62114/give-ghost-backdoor/">Give Up the Ghost: A Backdoor by Another Name (Just Security)</a></li>
|
||||
</ul>
|
||||
|
||||
<h5>December 2018</h5>
|
||||
<ul>
|
||||
<li><a href="https://www.zdnet.com/article/whats-actually-in-australias-encryption-laws-everything-you-need-to-know/">What's actually in Australia's encryption laws? Everything you need to know (ZDnet)</a></li>
|
||||
</ul>
|
||||
|
||||
<h3>Complete Comparison</h3>
|
||||
<ul>
|
||||
<li><a href="https://securechatguide.org/effguide.html">securechatguide.org</a> - Guide to Choosing a Messenger.</li>
|
||||
<li><a href="https://www.securemessagingapps.com/">securemessagingapps.com</a> - Secure Messaging Apps Comparison.</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="#rtc-independent-security-audits">Independent security audits</h3>
|
||||
<ul>
|
||||
<li><a href="https://eprint.iacr.org/2016/1013.pdf">A Formal Security Analysis of the Signal Messaging Protocol (2019)</a> by Katriel Cohn-Gordon, Cas Cremers, Benjamin Dowling, Luke Garratt and Douglas Stebila</li>
|
||||
<li><a href="https://keybase.io/docs-assets/blog/NCC_Group_Keybase_KB2018_Public_Report_2019-02-27_v1.3.pdf">Keybase's Protocol Security Review (2019)</a> by <a href="https://www.nccgroup.trust/">NCC Group</a></li>
|
||||
<li><a href="https://www.nccgroup.trust/us/our-research/matrix-olm-cryptographic-review/">Matrix Olm Cryptographic Review</a></li>
|
||||
<li><a href="https://briarproject.org/news/2017-beta-released-security-audit">Briar - Darknet Messenger Releases Beta, Passes Security Audit</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -6,10 +6,11 @@
|
|||
|
||||
{%
|
||||
include cardv2.html
|
||||
title="Riot.im (Matrix)"
|
||||
image="/assets/img/tools/Riot.png"
|
||||
description="Riot.im is a federated free-software messaging application based on the <a href\"https://matrix.org/\">Matrix</a> protocol, a recent open protocol for real-time communication offering optional E2E encryption. It also has bridging functionality, allowing you to connect to other chat protocols such as IRC or Telegram."
|
||||
labels="warning:<a href=//github.com/vector-im/riot-web/issues/6779>Experimental E2EE</a>:The end-to-end encryption is currently in beta, and the mobile client states 'End-to-end encryption is in beta and may not be reliable. You should not yet trust it to secure data.'"
|
||||
title="Matrix"
|
||||
image="/assets/img/tools/Matrix.png"
|
||||
image-dark="/assets/img/tools/Matrix-dark.png"
|
||||
description='<a href="https://matrix.org/docs/guides/introduction">Matrix</a> is an open-source project that publishes the <a href="https://matrix.org/docs/spec">Matrix open standard</a> for secure, decentralized, real-time communication.<br />
|
||||
<a href="https://en.wikipedia.org/wiki/Riot.im">Riot.im</a> is the popular reference client produced by the Matrix.org team. It offers optional E2EE for 1:1 and group conversations that <strong>must</strong> be turned on by the user. (This can be done by clicking on the toggle switch which is accessed by clicking the room name or user name of the chat → Security & Privacy → Encrypted). In the future it will be <a href="https://github.com/vector-im/riot-web/issues/6779">on by default.</a>'
|
||||
website="https://about.riot.im/"
|
||||
forum="https://forum.privacytools.io/t/discussion-riot-im/665/"
|
||||
github="https://github.com/vector-im/riot-web/"
|
||||
|
|
@ -18,7 +19,7 @@
|
|||
linux="https://riot.im/download/desktop/"
|
||||
fdroid="https://f-droid.org/repository/browse/?fdid=im.vector.alpha"
|
||||
googleplay="https://play.google.com/store/apps/details?id=im.vector.app"
|
||||
ios="https://itunes.apple.com/us/app/vector.im/id1083446067"
|
||||
ios="https://itunes.apple.com/app/vector.im/id1083446067"
|
||||
web="https://riot.im/app/"
|
||||
%}
|
||||
|
||||
|
|
@ -43,8 +44,8 @@
|
|||
include cardv2.html
|
||||
title="Keybase"
|
||||
image="/assets/img/tools/keybase.png"
|
||||
description='Keybase provides a hosted team chat with end-to-end encryption. It has also been <a href="https://keybase.io/docs-assets/blog/NCC_Group_Keybase_KB2018_Public_Report_2019-02-27_v1.3.pdf">independently audited (PDF)</a>.'
|
||||
labels="warning:<a href=//github.com/keybase/client/issues/6374>Warning</a>:The server side of Keybase runs on proprietary code and is centralized."
|
||||
description='Keybase provides a hosted team chat with E2EE. Its protocol has also been <a href="https://keybase.io/docs-assets/blog/NCC_Group_Keybase_KB2018_Public_Report_2019-02-27_v1.3.pdf">indepedently audited (PDF)</a>. Keybase can help you prove you own social media accounts though the use of cryptographic signing of "<a href="https://en.wikipedia.org/wiki/Keybase#Identity_proofs">identity proofs</a>".'
|
||||
labels="warning:<a href=github.com/keybase/client/issues/6374>Warning</a>:This software relies on a closed-source central server."
|
||||
website="https://keybase.io/"
|
||||
forum="https://forum.privacytools.io/t/discussion-keybase/1224"
|
||||
tor="http://keybase5wmilwokqirssclfnsqrjdsi7jdir5wy7y7iu3tanwmtp6oid.onion/"
|
||||
|
|
@ -53,8 +54,8 @@
|
|||
mac="https://keybase.io/docs/the_app/install_macos"
|
||||
linux="https://keybase.io/docs/the_app/install_linux"
|
||||
freebsd="https://www.freshports.org/security/keybase/"
|
||||
googleplay="https://play.google.com/store/apps/details?id=io.keybase.ossifrage&hl=en_US"
|
||||
ios="https://keybase.io/_/download/keybase-for-ios"
|
||||
firefox="https://addons.mozilla.org/en-US/firefox/addon/keybase-for-firefox/"
|
||||
googleplay="https://play.google.com/store/apps/details?id=io.keybase.ossifrage"
|
||||
ios="https://apps.apple.com/app/keybase-crypto-for-everyone/id1044461770"
|
||||
firefox="https://addons.mozilla.org/firefox/addon/keybase-for-firefox/"
|
||||
chrome="https://chrome.google.com/webstore/detail/keybase-for-reddit/ognfafcpbkogffpmmdglhbjboeojlefj"
|
||||
%}
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 5.8 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 23 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 2.0 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 2.0 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 3.9 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 5.8 KiB |
Reference in New Issue