Client-side encryption: Difference between revisions

Content deleted Content added
Toned down unsupported gushing. It's only as reliable as the client. For example, if the client can be "updated" (potentially into an insecure state), then it's only fake security.
Full stop before ref
Tags: Mobile edit Mobile web edit Advanced mobile edit
Line 1:
'''Client-side encryption''' is the [[cryptographic]] technique of [[encrypting]] data on the sender's side, before it is transmitted to a [[server (computing)|server]] such as a cloud storage service.<ref name=infosectoday>{{cite web |url= http://www.infosectoday.com/Articles/Client-Side_Encryption.htm |title= Why Client-Side Encryption Is the Next Best Idea in Cloud-Based Data Security |date= 2015 |accessdate= February 21, 2016 |author= Tunio Gaffer |website= Information Security Today |publisher= Auerbach Publications}}</ref> Client-side encryption features an encryption key that is not available to the service provider, making it difficult or impossible for service providers to decrypt hosted data. Client-side encryption allows for the creation of applications whose providers cannot access the data its users have stored, thus offering a high level of privacy.<ref name=infosectoday/> Those applications are sometimes marketed under the misleading term "zero-knowledge".<ref>{{Cite web|url=https://news.ycombinator.com/item?id=13303436|title=Spider Oak - Please stop describing your service as "Zero Knowledge" unless and ... {{!}} Hacker News|website=news.ycombinator.com|access-date=2018-07-16}}</ref>.
 
==Details==