Skip to content

Commit

Permalink
unfix not a typo
Browse files Browse the repository at this point in the history
"S" is, indeed a consonant, but since it is pronounced "ess", it is appropriate to write "an SSL certificate"
  • Loading branch information
adammichaelwood committed Sep 29, 2017
1 parent 71d158c commit 4cfd4eb
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion encrypted-forms.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Encrypted Forms

Overview
====================
Encrypted forms provide a mechanism to keep your data private even when using **http:** for communications (e.g., when you do not have a **SSL certificate** or **https:** is not available). Encrypted forms may also enable Google App Engine deployments (and deployments using other web database services, e.g., AWS) to comply with data privacy laws, eliminating the necessity for setting up your own servers to meet those requirements.
Encrypted forms provide a mechanism to keep your data private even when using **http:** for communications (e.g., when you do not have an **SSL certificate** or **https:** is not available). Encrypted forms may also enable Google App Engine deployments (and deployments using other web database services, e.g., AWS) to comply with data privacy laws, eliminating the necessity for setting up your own servers to meet those requirements.

Encrypted forms apply asymmetric public key encryption at the time the form is finalized within ODK Collect. This encrypted form can then be submitted up to ODK Aggregate and downloaded to ODK Briefcase. ODK Briefcase, when supplied with the asymmetric private key (which ODK Briefcase never stores), can then decrypt and export the form data as a CSV file for your use.

Expand Down

0 comments on commit 4cfd4eb

Please sign in to comment.