Aller au contenu

« Silence (application) » : différence entre les versions

Ajouter des liens
Un article de Wikipédia, l'encyclopédie libre.
Navigation interactive dans l’historique
← Modification précédenteModification suivante →
Contenu supprimé Contenu ajouté
VisuelWikicode
Asr (discuter | contributions)
2 336 modifications
Aucun résumé des modifications
Asr (discuter | contributions)
2 336 modifications
Balises : Nowiki dans un article Éditeur visuel
Ligne 30 : Ligne 30 :


====Open Whisper Systems (2013–2015)====
====Open Whisper Systems (2013–2015)====
Open Whisper Systems' website was launched in January 2013.<ref name="welcome" /> Open Whisper Systems started working to bring TextSecure to [[iOS]] in March 2013.<ref name="threatpost1" /><ref name="sure" />
<s>Open Whisper Systems' website was launched in January 2013.<ref name="welcome" /> Open Whisper Systems started working to bring TextSecure to [[iOS]] in March 2013.<ref name="threatpost1" /><ref name="sure" /></s>


In February 2014, Open Whisper Systems updated their protocol to version 2, adding group chat and push messaging capabilities.<ref name="threatpost1" /><ref name="the-new-textsecure" /> Toward the end of July 2014, Open Whisper Systems announced plans to unify its RedPhone and TextSecure applications as [[Signal (software)|Signal]].<ref name="signal" /> This announcement coincided with the initial release of Signal as a RedPhone counterpart for iOS. The developers said that their next steps would be to provide TextSecure instant messaging capabilities for iOS, unify the RedPhone and TextSecure applications on Android, and launch a web client.<ref name="threatpost2" /> Signal was the first iOS app to enable easy, strongly encrypted voice calls for free.<ref name="wired3" /><ref name="techcrunch2" />
<s>In February 2014, Open Whisper Systems updated their protocol to version 2, adding group chat and push messaging capabilities.<ref name="threatpost1" /><ref name="the-new-textsecure" /> Toward the end of July 2014, Open Whisper Systems announced plans to unify its RedPhone and TextSecure applications as [[Signal (software)|Signal]].<ref name="signal" /> This announcement coincided with the initial release of Signal as a RedPhone counterpart for iOS. The developers said that their next steps would be to provide TextSecure instant messaging capabilities for iOS, unify the RedPhone and TextSecure applications on Android, and launch a web client.<ref name="threatpost2" /> Signal was the first iOS app to enable easy, strongly encrypted voice calls for free.<ref name="wired3" /><ref name="techcrunch2" /></s>


In March 2015, Open Whisper Systems released Signal 2.0 with support for TextSecure private messaging on iOS.<ref name="theintercept1" /><ref name="arstechnica1" /> Later that month, Open Whisper Systems ended support for sending and receiving encrypted SMS/MMS messages on Android. As of version 2.7.0, TextSecure only supports sending and receiving encrypted messages via the data channel. Reasons for this included:<ref name="goodbye-encrypted-sms" />
<s>In March 2015, Open Whisper Systems released Signal 2.0 with support for TextSecure private messaging on iOS.<ref name="theintercept1" /><ref name="arstechnica1" /> Later that month, Open Whisper Systems ended support for sending and receiving encrypted SMS/MMS messages on Android. As of version 2.7.0, TextSecure only supports sending and receiving encrypted messages via the data channel. Reasons for this included:<ref name="goodbye-encrypted-sms" /></s>
*Complications with the SMS encryption procedure: Users needed to manually initiate a "key exchange", which required a full round trip before any messages could be exchanged. In addition to this, users could not always be sure whether the receiver could receive encrypted SMS/MMS messages or not.
*<s>Complications with the SMS encryption procedure: Users needed to manually initiate a "key exchange", which required a full round trip before any messages could be exchanged. In addition to this, users could not always be sure whether the receiver could receive encrypted SMS/MMS messages or not.</s>
*Compatibility issues with iOS: Not possible to send or receive encrypted SMS/MMS messages on iOS due to the lack of [[Application programming interface|APIs]].
*<s>Compatibility issues with iOS: Not possible to send or receive encrypted SMS/MMS messages on iOS due to the lack of [[Application programming interface|APIs]].</s>
*The large amounts of [[metadata]] that inevitably arise and are uncontrollable when using SMS/MMS for the transportation of messages.
*<s>The large amounts of [[metadata]] that inevitably arise and are uncontrollable when using SMS/MMS for the transportation of messages.</s>
*Focus on software development: Maintaining SMS/MMS encryption and dealing with edge cases took up valuable resources and inhibited the development of the software.
*<s>Focus on software development: Maintaining SMS/MMS encryption and dealing with edge cases took up valuable resources and inhibited the development of the software.</s>


=== Fork vers SMSSecure ===
=== Fork vers SMSSecure ===
Ligne 51 : Ligne 51 :
Il permet également d'envoyer des messages non chiffrés (SMS et MMS) vers des utilisateurs de téléphone ne disposant pas de TextSecure, SMSSecure ou n'étant pas sous WhisperPush sous Cryogenmod.
Il permet également d'envoyer des messages non chiffrés (SMS et MMS) vers des utilisateurs de téléphone ne disposant pas de TextSecure, SMSSecure ou n'étant pas sous WhisperPush sous Cryogenmod.
===Gestion des SMS/MMS classiques===
===Gestion des SMS/MMS classiques===
Messages sent with SMSSecure may be encrypted as soon as the user sends a private session request. This feature differs from the regular use of TextSecure protocol V2 in TextSecure, WhisperPush and Signal, which centralizes the users in [[Federation (information technology)|federated]] directory servers, and therefore is able to automatically start ciphered sessions via Google Cloud Messaging or WhisperPush, without requesting it from the user.<ref name="linuxfr1" />
<s>Messages sent with SMSSecure may be encrypted as soon as the user sends a private session request. This feature differs from the regular use of TextSecure protocol V2 in TextSecure, WhisperPush and Signal, which centralizes the users in [[Federation (information technology)|federated]] directory servers, and therefore is able to automatically start ciphered sessions via Google Cloud Messaging or WhisperPush, without requesting it from the user.<ref name="linuxfr1" /></s>


===Encryption of SMS===
===<s>Encryption of SMS</s>===
When the private session started in SMSSecure, any sent messages are automatically end-to-end encrypted, which means that they can only be read by the intended recipients. The [[Key (cryptography)|keys]] that are used to encrypt the user's messages are stored on the device alone, and they are protected by an additional layer of encryption if the user has a passphrase enabled. In the user interface, encrypted messages are denoted by a lock icon.
<s>When the private session started in SMSSecure, any sent messages are automatically end-to-end encrypted, which means that they can only be read by the intended recipients. The [[Key (cryptography)|keys]] that are used to encrypt the user's messages are stored on the device alone, and they are protected by an additional layer of encryption if the user has a passphrase enabled. In the user interface, encrypted messages are denoted by a lock icon.</s>


===Key verification===
===<s>Key verification</s>===
SMSSecure has a built-in function for verifying that the user is communicating with the right person and that no [[man-in-the-middle attack]] has occurred. This verification can be done by comparing key fingerprints out-of-band. Users can also scan each other's personal [[QR code]]s.
<s>SMSSecure has a built-in function for verifying that the user is communicating with the right person and that no [[man-in-the-middle attack]] has occurred. This verification can be done by comparing key fingerprints out-of-band. Users can also scan each other's personal [[QR code]]s.</s>


===Non-dependency on GCM===
===<s>Non-dependency on GCM</s>===
TextSecure implements instant messaging via [[Google Cloud Messaging]] or Cyanogen's WhisperPush.<ref name=whisper1 />{{self published inline|date=July 2015}} According to the SMSSecure team, their goal is to build an app which could be totally independant from Google Services,<ref name="readme1" /> which is not be TextSecure because of this GCM dependancy.<ref name="korben1" />
<s>TextSecure implements instant messaging via [[Google Cloud Messaging]] or Cyanogen's WhisperPush.<ref name="whisper1" />{{self published inline|date=July 2015}} According to the SMSSecure team, their goal is to build an app which could be totally independant from Google Services,<ref name="readme1" /> which is not be TextSecure because of this GCM dependancy.<ref name="korben1" /></s>


===Encryption without data channel===
===<s>Encryption without data channel</s>===
The application doesn't needs to own a data channel to cipher/decipher messages. According to the slovakian website "cypersec.sk", with the abandon of SMS/MMS use by [[TextSecure]], it is now the only one from their tests to propose this feature.
<s>The application doesn't needs to own a data channel to cipher/decipher messages. According to the slovakian website "cypersec.sk", with the abandon of SMS/MMS use by [[TextSecure]], it is now the only one from their tests to propose this feature.
<ref name="cybersec.sk">http://www.cybersec.sk/navody-a-programy/navody/ako-si-ochranit-komunikaciu-predovsetkym-na-androide/
<ref name="cybersec.sk">http://www.cybersec.sk/navody-a-programy/navody/ako-si-ochranit-komunikaciu-predovsetkym-na-androide/
(via Google translate)
(via Google translate)
''SMSsecure
''SMSsecure''


The only exception among the selected applications, which replaces the built-in Messenger Android. After you install it, use the SMS if only this application, including received messages. The authors have chosen this solution, especially for greater security - SMS messages are also encrypted locally in the phone memory. Note, however, that after uninstalling lose all SMS messages that have been received by it.
The only exception among the selected applications, which replaces the built-in Messenger Android. After you install it, use the SMS if only this application, including received messages. The authors have chosen this solution, especially for greater security - SMS messages are also encrypted locally in the phone memory. Note, however, that after uninstalling lose all SMS messages that have been received by it.
⚫
The indisputable advantage of the application and its unique is that it does not require a data connection. If the application uses only one party sends unencrypted traditional SMS. If you have applications installed both, sender and recipient, it is possible to exchange messages in encrypted mode. Enough to exchange encryption keys (one-touch). This is a very intuitive application that the operator should not cause more trouble even inexperienced users.''<nowiki/>''</ref></s>

⚫
The indisputable advantage of the application and its unique is that it does not require a data connection. If the application uses only one party sends unencrypted traditional SMS. If you have applications installed both, sender and recipient, it is possible to exchange messages in encrypted mode. Enough to exchange encryption keys (one-touch). This is a very intuitive application that the operator should not cause more trouble even inexperienced users.''</ref>


==Stagefright==
==Stagefright==
On July 27, 2015, a bug called [[Stagefright (bug)|Stagefright]] was publicly announced,<ref name="zdnet1">http://www.zdnet.fr/actualites/stagefright-un-simple-mms-pour-controler-95-des-smartphones-android-39822978.htm</ref> which lead users to audit their MMS/SMS applications. Accoring to ''Yemen-Press.com'', SMSSecure's default settings can be modified so that it is not vulnerable to this [[attack vector]].<ref name="yemenpress">https://yemen-press.com/news52022.html</ref>
Le 27 juillet 2015, la firme Zimperium a révélé avoir repérér une faille<nowiki><ref>http://blog.zimperium.com/experts-found-a-unicorn-in-the-heart-of-android/</ref></nowiki><s><ref name="zdnet1">http://www.zdnet.fr/actualites/stagefright-un-simple-mms-pour-controler-95-des-smartphones-android-39822978.htm</ref></s> dans la librairie <nowiki>[[Stagefright]]</nowiki> utilisée par nombre d'applications android pour afficher les contenus non textuels, dont les applications de MMS par défaut. TextSecure ne faisant pas de pré-processing d'images n'est pas vulnérable au 0-clic, mais peut l'être au 1-clic<nowiki><ref>{{cite web|url=https://lists.riseup.net/www/arc/whispersystems/2015-07/msg00084.html|titre=Stagefright vilnerability}}</nowiki>

<nowiki>''</nowiki>TextSecure plays audio/video by handing it to the system's default media player. If there's a stagefright vulnerability, it's possible that the system's default media player is vulnerable. From TextSecure, that interaction should only happen by physically tapping on an audio/video attachment, then tapping through a warning dialog about insecure playback. At that point, it's out of our hands.<nowiki>''</ref></nowiki>. D'après ''Yemen Press.com''<s><ref name="yemenpress">https://yemen-press.com/news52022.html</ref></s>, les paramètres de SMSSecure peuvent être modifiés pour ne pas que l'application soit sensible à ce bug.


==Licensing==
==License==
The complete [[source code]] of SMSSecure is available on [[GitHub]] under a [[free software license]]. This enables interested parties to examine the code and help the developers verify that everything is behaving as expected. It also allows advanced users to compile their own copy of the application and compare it with the version that is distributed by SMSSecure.
<s>The complete [[source code]] of SMSSecure is available on [[GitHub]] under a [[free software license]]. This enables interested parties to examine the code and help the developers verify that everything is behaving as expected. It also allows advanced users to compile their own copy of the application and compare it with the version that is distributed by SMSSecure.</s>


==Accueil de la presse==
==Reception==


In April 2015, SMSSecure was included in a list of "The best 9 apps for Android" by the Dutch website ''Android Planet''.<ref name="androidplanet2">http://www.androidplanet.nl/apps/de-9-beste-android-apps-in-google-play-van-week-15-2015/</ref>
En avril 2015, SMSSecure a été inclu dans une liste des "Les 9 meilleurs applis pour Android" du site web néerlandais ''Android Planet''.<ref name="androidplanet2">http://www.androidplanet.nl/apps/de-9-beste-android-apps-in-google-play-van-week-15-2015/</ref>


==Distribution==
==Diffusion==
SMSSecure is available through Google Play, F-Droid and Amazon Apps.
<s>SMSSecure is available through Google Play, F-Droid and Amazon Apps.</s>


== See also ==
== Voir aussi ==
{{Portal| Freedom of speech | Free software | Cryptography | Telecommunications}}
{{Portal| Freedom of speech | Free software | Cryptography | Telecommunications}}
* [[Comparison of instant messaging clients]]
* [[Comparison of instant messaging clients]]

Version du 31 juillet 2015 à 11:44

Cet article est une ébauche.

Vous pouvez partager vos connaissances en l’améliorant (comment ?).

Consultez la liste des tâches à accomplir en page de discussion.

Silence
[[Fichier:Fichier:SMSsecure logo.svg |frameless |upright=0.55 |alt=Description de l'image Fichier:SMSsecure logo.svg. ]]
[[Fichier: |frameless |upright=1 |alt=Description de l'image . ]]
Informations
Première version
Dernière version Modèle:LSR
Dépôt git.silence.dev/Silence/Silence-AndroidVoir et modifier les données sur Wikidata
Assurance qualité Intégration continueVoir et modifier les données sur Wikidata
État du projet Actif
Écrit en JavaVoir et modifier les données sur Wikidata
Système d'exploitation AndroidVoir et modifier les données sur Wikidata
Environnement Android
Type Chiffrement de SMS/MMS messaging
Licence Licence publique générale GNU version 3Voir et modifier les données sur Wikidata
Site web smssecure.org

modifier - modifier le code - voir Wikidata (aide)

SMSSecure est un fork de TextSecure, deux logiciels libres et open-source de chiffrement de messagerie. Ces applications permettent la transmission sécurisée des messages SMS et MMS à d'autres utilisateurs de SMSSecure, TextSecure, ou Signal. Les utilisateurs peuvent vérifier indépendamment de l'identité de leurs correspondants en comparant les empreintes digitales (fingerprint) des clés de chiffrement, ou en scannant les codes QR de personne à personne. L'application Android peut fonctionner en remplacement de l'application de messagerie native d'Android. La base de données de messages locale peut être chiffré avec un mot de passe.

SMSSecure met en œuvre le protocole de chiffrement de TextSecure, mais sans messagerie « push »,[1] et ne peut donc pas être utilisé pour la messagerie instantanée en tant que telle vers les utilisateurs TextSecure, WhisperPush, ou Signal. SMSSecure est développé par l'équipe de SMSSecure.

Historique

TextSecure

Whisper Systems et Twitter (2010–2011)

TextSecure a démarré comme une application permettant d'envoyer et recevoir des SMS chiffrés.[2] Sa version beta a été publiée en mai 2010, par Whisper Systems,[3] une startup co-fondée par le chercheur en sécurité Moxie Marlinspike, et le roboticien Stuart Anderson.[4][5]. Cette application et les autres applications de Whisper Systems sont à l'époque sous license propriétaire.

En novembre 2011, Twitter a acquis Whisper Systems. Les termes financiers du contrat n'ont pas été diffusés, mais l'acquisition a été faite principalement pour que M. Marlinspike puisse aider la startup a améliorer la sécurité[6][7][8]

Le logiciel a dès lors été publié sous license libre et open-source, sous les termes de la GPLv3 en décembre 2011.[4][9][10][11] . Marlinspike a quitté Twitter pour créer Open Whisper Systems[12] comme projet Open Source collaboratif, permettant le developement de TextSecure.[13]

Open Whisper Systems (2013–2015)

Open Whisper Systems' website was launched in January 2013.[13] Open Whisper Systems started working to bring TextSecure to iOS in March 2013.[14][15]

In February 2014, Open Whisper Systems updated their protocol to version 2, adding group chat and push messaging capabilities.[14][16] Toward the end of July 2014, Open Whisper Systems announced plans to unify its RedPhone and TextSecure applications as Signal.[17] This announcement coincided with the initial release of Signal as a RedPhone counterpart for iOS. The developers said that their next steps would be to provide TextSecure instant messaging capabilities for iOS, unify the RedPhone and TextSecure applications on Android, and launch a web client.[18] Signal was the first iOS app to enable easy, strongly encrypted voice calls for free.[12][19]

In March 2015, Open Whisper Systems released Signal 2.0 with support for TextSecure private messaging on iOS.[20][21] Later that month, Open Whisper Systems ended support for sending and receiving encrypted SMS/MMS messages on Android. As of version 2.7.0, TextSecure only supports sending and receiving encrypted messages via the data channel. Reasons for this included:[2]

  • Complications with the SMS encryption procedure: Users needed to manually initiate a "key exchange", which required a full round trip before any messages could be exchanged. In addition to this, users could not always be sure whether the receiver could receive encrypted SMS/MMS messages or not.
  • Compatibility issues with iOS: Not possible to send or receive encrypted SMS/MMS messages on iOS due to the lack of APIs.
  • The large amounts of metadata that inevitably arise and are uncontrollable when using SMS/MMS for the transportation of messages.
  • Focus on software development: Maintaining SMS/MMS encryption and dealing with edge cases took up valuable resources and inhibited the development of the software.

Fork vers SMSSecure

L'abandon du chiffrement des SMS/MMS par Open Whisper Systems' [22], ainsi que la dépendance forte envers les technologies Google Google Cloud Messaging et Google Market ; l'indisponibilité de l'application sur les plateformes F-Droid et Amazon[23] a conduit plusieurs développeurs à créer un fork.[1][24][25]

Fonctionnalités

Screenshots de l'application depuis un smartphone

SMSSecure permet à ses utilisateurs d'envoyer des messages textes chiffrés vers d'autres utilisateurs de SMSSecure, sur smartphone sous android ou Cryogenmod, ou de Signals sur iPhone sous IOS. Il permet également d'envoyer des messages non chiffrés (SMS et MMS) vers des utilisateurs de téléphone ne disposant pas de TextSecure, SMSSecure ou n'étant pas sous WhisperPush sous Cryogenmod.

Gestion des SMS/MMS classiques

Messages sent with SMSSecure may be encrypted as soon as the user sends a private session request. This feature differs from the regular use of TextSecure protocol V2 in TextSecure, WhisperPush and Signal, which centralizes the users in federated directory servers, and therefore is able to automatically start ciphered sessions via Google Cloud Messaging or WhisperPush, without requesting it from the user.[26]

Encryption of SMS

When the private session started in SMSSecure, any sent messages are automatically end-to-end encrypted, which means that they can only be read by the intended recipients. The keys that are used to encrypt the user's messages are stored on the device alone, and they are protected by an additional layer of encryption if the user has a passphrase enabled. In the user interface, encrypted messages are denoted by a lock icon.

Key verification

SMSSecure has a built-in function for verifying that the user is communicating with the right person and that no man-in-the-middle attack has occurred. This verification can be done by comparing key fingerprints out-of-band. Users can also scan each other's personal QR codes.

Non-dependency on GCM

TextSecure implements instant messaging via Google Cloud Messaging or Cyanogen's WhisperPush.[27]Modèle:Self published inline According to the SMSSecure team, their goal is to build an app which could be totally independant from Google Services,[28] which is not be TextSecure because of this GCM dependancy.[29]

Encryption without data channel

The application doesn't needs to own a data channel to cipher/decipher messages. According to the slovakian website "cypersec.sk", with the abandon of SMS/MMS use by TextSecure, it is now the only one from their tests to propose this feature. [30]

Stagefright

Le 27 juillet 2015, la firme Zimperium a révélé avoir repérér une faille<ref>http://blog.zimperium.com/experts-found-a-unicorn-in-the-heart-of-android/</ref>[31] dans la librairie [[Stagefright]] utilisée par nombre d'applications android pour afficher les contenus non textuels, dont les applications de MMS par défaut. TextSecure ne faisant pas de pré-processing d'images n'est pas vulnérable au 0-clic, mais peut l'être au 1-clic<ref>{{cite web|url=https://lists.riseup.net/www/arc/whispersystems/2015-07/msg00084.html|titre=Stagefright vilnerability}}

''TextSecure plays audio/video by handing it to the system's default media player. If there's a stagefright vulnerability, it's possible that the system's default media player is vulnerable. From TextSecure, that interaction should only happen by physically tapping on an audio/video attachment, then tapping through a warning dialog about insecure playback. At that point, it's out of our hands.''</ref>. D'après Yemen Press.com[32], les paramètres de SMSSecure peuvent être modifiés pour ne pas que l'application soit sensible à ce bug.

License

The complete source code of SMSSecure is available on GitHub under a free software license. This enables interested parties to examine the code and help the developers verify that everything is behaving as expected. It also allows advanced users to compile their own copy of the application and compare it with the version that is distributed by SMSSecure.

Accueil de la presse

En avril 2015, SMSSecure a été inclu dans une liste des "Les 9 meilleurs applis pour Android" du site web néerlandais Android Planet.[33]

Diffusion

SMSSecure is available through Google Play, F-Droid and Amazon Apps.

Voir aussi

Modèle:Portal


References

  1. ↑ a et b (de) « TextSecure-Fork bringt SMS-Verschlüsselung zurück », sur Heise, (consulté le )
  2. ↑ a et b Open Whisper Systems, « Saying goodbye to encrypted SMS/MMS », (consulté le )
  3. ↑ « Announcing the public beta » [archive du ], Whisper Systems, (consulté le )
  4. ↑ a et b (en) Caleb Garling, « Twitter Open Sources Its Android Moxie | Wired Enterprise », Wired,‎ (lire en ligne)
  5. ↑ « Company Overview of Whisper Systems Inc. », Bloomberg Businessweek (consulté le )
  6. ↑ Tom Cheredar, « Twitter acquires Android security startup Whisper Systems », VentureBeat, (consulté le )
  7. ↑ The acquisition was done "primarily so that Mr. Marlinspike could help the then-startup improve its security
  8. ↑ (en) Danny Yadron, « Moxie Marlinspike: The Coder Who Encrypted Your Texts », The Wall Street Journal,‎ (lire en ligne)
  9. ↑ Chris Aniszczyk, « The Whispers Are True » [archive du ], sur The Twitter Developer Blog, Twitter, (consulté le )
  10. ↑ « TextSecure is now Open Source! » [archive du ], Whisper Systems, (consulté le )
  11. ↑ (en) Pete Pachal, « Twitter Takes TextSecure, Texting App for Dissidents, Open Source », Mashable,‎ (lire en ligne)
  12. ↑ a et b Andy Greenberg, « Your iPhone Can Finally Make Free, Encrypted Calls », Wired, (consulté le )
  13. ↑ a et b (en) « A New Home », Open Whisper Systems,‎ (lire en ligne)
  14. ↑ a et b Brian Donohue, « TextSecure Sheds SMS in Latest Version », Threatpost, (consulté le )
  15. ↑ Christine Corbett, « Sure! », Open Whisper Systems, (consulté le )
  16. ↑ Moxie Marlinspike, « The New TextSecure: Privacy Beyond SMS », Open Whisper Systems, (consulté le )
  17. ↑ « Free, Worldwide, Encrypted Phone Calls for iPhone », Open Whisper Systems,
  18. ↑ Michael Mimoso, « New Signal App Brings Encrypted Calling to iPhone », Threatpost,
  19. ↑ Jon Evans, « Talk Private To Me: Free, Worldwide, Encrypted Voice Calls With Signal For iPhone », TechCrunch, AOL,
  20. ↑ (en) Micah Lee, « You Should Really Consider Installing Signal, an Encrypted Messaging App for iPhone », The Intercept,‎ (lire en ligne)
  21. ↑ (en) Megan Geuss, « Now you can easily send (free!) encrypted messages between Android, iOS », Ars Technica,‎ (lire en ligne)
  22. ↑ http://www.techwalls.com/textsecure-no-longer-encrypts-sms/
  23. ↑ http://derstandard.at/2000013841576/SMSSecure-TextSecure-Abspaltung-belebt-SMS-Verschluesselung-wieder
  24. ↑ https://www.security.nl/posting/422674/Versleuteld+sms%27en+met+Android-app+SMSSecure
  25. ↑ http://open-freax.fr/smssecure-retour-sms-chiffres/
  26. ↑ LinuxFr : SMSSecure - Les sms et mms chiffrés sur Android, ce n'est pas fini
  27. ↑ The client logic is contained in a CyanogenMod system app called WhisperPush, which the system hands outgoing SMS messages to for optional delivery. https://whispersystems.org/blog/cyanogen-integration/
  28. ↑ SMSSecure focuses on SMS and MMS. This fork aims to: Keep SMS/MMS encryption ; Drop Google services dependencies (push messages are not available in SMSSecure). SMSSecure/README.md
  29. ↑ SMSSecure est libre (sous licence GPL), ne dépend d'aucun serveur tiers, ne repose pas sur les API et services de Google et utilise un chiffrement de 256 bits. Korben : crypter sms et mms
  30. ↑ http://www.cybersec.sk/navody-a-programy/navody/ako-si-ochranit-komunikaciu-predovsetkym-na-androide/ (via Google translate) SMSsecure The only exception among the selected applications, which replaces the built-in Messenger Android. After you install it, use the SMS if only this application, including received messages. The authors have chosen this solution, especially for greater security - SMS messages are also encrypted locally in the phone memory. Note, however, that after uninstalling lose all SMS messages that have been received by it. The indisputable advantage of the application and its unique is that it does not require a data connection. If the application uses only one party sends unencrypted traditional SMS. If you have applications installed both, sender and recipient, it is possible to exchange messages in encrypted mode. Enough to exchange encryption keys (one-touch). This is a very intuitive application that the operator should not cause more trouble even inexperienced users.
  31. ↑ http://www.zdnet.fr/actualites/stagefright-un-simple-mms-pour-controler-95-des-smartphones-android-39822978.htm
  32. ↑ https://yemen-press.com/news52022.html
  33. ↑ http://www.androidplanet.nl/apps/de-9-beste-android-apps-in-google-play-van-week-15-2015/

Erreur de référence : La balise <ref> nommée « whispersys3 » définie dans <references> n’est pas utilisée dans le texte précédent.

Modèle:Logiciel de cryptographie

Categorie:Logiciel de cryptographie Categorie:Android Categorie:Logiciel libre Categorie:Java

Ce document provient de « https://fr.wikipedia.org/w/index.php?title=Silence_(application)&oldid=117340390 ».