Difference between revisions of "Data encryption/ja"

From LimeSurvey Manual

(Created page with "==設定== LimeSurveyには、データ暗号化設定を設定できる場所が3つあります。 * 質問属性 * Data_encryp...")
(Created page with "===質問属性=== 質問属性「暗号化」は、対応する回答データの暗号化を有効にするために使用します。この属性の既定値は'''オフ'''...")
Line 41: Line 41:
===Question attributes===
Question attribute "Encrypted" is used to enable data encryption for corresponding responses. This attribute is '''turned off''' by default. Once survey is activated, it is not possible to change this attribute.

Revision as of 03:26, 10 August 2019

Other languages:
English • ‎Nederlands • ‎日本語


データ暗号化は、LimeSurvey 4で提供される新機能です。これは、アンケート管理者が世界のさまざまな地域で採用されている新しいデータ保護規制(GDPRなど)に適切に対応できるように作成されました。



  暗号化キーを作成したら、必ずバックアップを作成してください。 キーを紛失すると、データを回復できなくなるため、データが使用できなくなります。LimeSurvey CEを使用する場合、公開キーと秘密キーは/application/config/security.phpにあります。



  • the type of data you collect
  • where your survey is based on
  • national or federal legislation
  • ...








Question attributes.png

Participant attributes

Three core attributes (firstname, lastname, and email) are always shown in the survey participants table, the encryption being turned on by default.

Each new participant attribute will have encryption turned off by default.

Encryption can be turned on or off at any moment.

Manage attribute fields.png

Central participant database attribute management

Three core attributes (firstname, lastname and email) are always shown in the central participant database, the encryption being turned on by default.

Each new participant attribute will have encryption turned off by default.

Encryption can be turned on or off at any moment.

Cpdb attribute management.png


Sodium library is used to provide data encryption and decryption functionality for LimeSurvey.

Sodium is a modern, easy-to-use software library for encryption, decryption, signatures, password hashing and more. It is a portable, cross-compilable, installable, packageable fork of NaCl, with a compatible API, and an extended API to improve usability even further. Its goal is to provide all of the core operations needed to build higher-level cryptographic tools.

Sodium is cross-platforms and cross-languages. It runs on a variety of compilers and operating systems, including Windows (with MinGW or Visual Studio, x86 and x86_64), iOS and Android. Javascript and WebAssembly versions are also available and are fully supported. Bindings for all common programming languages are available and well-supported.

Version 7.2.0 and newer of the PHP programming language includes the Sodium extension (referred to as ext/sodium) as a core cryptography library. Version 2 of the PHP extension in PECL is compatible with ext/sodium in PHP 7.2.

LimeSurvey uses the Sodium Compat library to bridge with different PHP versions. This library tentatively supports PHP 5.2.4 - 7.x (latest), but officially it only supports non-EOL'd versions of PHP.

Data encryption/decryption methods used in LimeSurvey are based on public-key signatures. Public and secret keys can be found in /application/config/security.php file. Keys are automatically generated on first usage of encryption feature.

  Warning : Once data encryption is turned on, data in corresponding database columns would become unreadable without decrypting them first. You should always have a backup of your encryption keys in case they get deleted. Also, once encryption keys are set, you should never change them because it would make all existing data unusable.

Partial string search won't be possible for database columns with encrypted data, only exact match search.


Possible errors when using data encryption:

  • library doesn't exists: PHP Sodium library have to be installed to be able to use data encryption feature. Here is a guide on how to install library: Sodium installation. If you don't want to use data encryption, you have to disable encryption in attribute settings.
  • wrong decryption key: decryption key has changed since data was last saved, so data can't be decrypted. The only way to decrypt data is to retrieve the original key from backup and replace the current decryption key with the original key.