Facebook has announced it is letting users add encryption keys to their profiles and opt in to have notification emails sent in an encrypted format.
The news comes as some US surveillance powers expire and tensions rise between the US government and the tech community over the use of strong encryption.
Strong encryption refers to data coded in such a way that it cannot
be understood by anyone who does not have the correct key to decrypt it.
It can help internet users keep their sensitive communications safe
online — but some people believe it poses a potential security risk, as
it cannot be decrypted by authorities even with a search warrant.
Following revelations of mass government surveillance by exiled
whistleblower Edward Snowden over the last few years, big tech companies
have increasingly incorporated strong encryption into their products.
This hardened stance is frustrating law enforcement, who fear they
will lose access to vital evidence. When Apple announced it would
implement strong encryption on its iOS mobile operating system, for
example, one senior US police officer claimed the iPhone "will become the phone of choice for the pedophile." But Apple argues that it is imperative that it protects users' privacy, with CEO Tim Cook saying the company has
"never worked with any government agency from any country to create a
backdoor in any of our products or services... And we never will."
Facebook has previously operated an "onion site" that lets users
access the social network via Tor, a network only accessible by a
special web browser that obscures users' identities. Now, the site's security team announced today in a note, users will be able to add their "public keys" to their profiles to encourage others to contact them using encryption.
Public keys are how people communicate with most popular encryption
products. Every user has a public and a private key — the public is
shared freely, while the private is kept secret. Anyone can encrypt a
message using someone else's public key, which can then only be
decrypted by the owner of that public key — using their private key.
No comments:
Post a Comment