devicecustomization

this object provides a method to encrypt storage and is released in bos version 9 0 146 devicecustomization idl interface devicecustomization { promise\<void> encryptstorage(string device, storageencryptionoptions params); }; interface storageencryptionoptions { attribute string method; attribute string passphrase; attribute boolean format; }; object creation let devicecustomizationclass = require("@brightsign/devicecustomization"); let devicecustomization = new devicecustomizationclass(); devicecustomization encryptstorage() promise\<void> encryptstorage(string device, storageencryptionoptions params) encrypts the contents of a storage device using an encryption key stored in the private section of the player registry this prevents other devices from reading the names or contents of files on the storage device (though file metadata will still be readable) the storage device can still be mounted on other devices, which can list, delete, and copy files (even though they cannot read them) the device parameter specifies which storage drive to encrypt (for example, /storage/sd , /storage/usb1 or /storage/ssd ), and the process is configured with the passed storageencryptionoptions parameters storageencryptionoptions attributes method string string the encryption method, which can be one of the following "none" encryption is disabled and any encryption keys for the storage device are deleted from the registry "passphrase" the storage device is encrypted using an un obfuscated passphrase "obfuscated passphrase" the storage device is encrypted using an obfuscated passphrase contact support\@brightsign biz mailto\ support\@brightsign biz to learn more about generating a key for obfuscation and storing it on the player "brightsign key" the storage device is encrypted using an encryption key that is common to all brightsign players, but is not shared with outside parties "generate key" the storage device is encrypted using an encryption key that is generated on demand using a secure random generator the private registry of the player contains the only copy of the key; if the value in the registry is erased or becomes corrupted, there will be no way to recover data from that storage device the private registry does not distinguish between different physical volumes of the same drive for example, if you encrypt two sd cards, the key for the first sd card will be overwritten when the second sd card is encrypted; in the case of a randomly generated key, the data from the first sd card will be irretrievable passphrase string string the passphrase for encrypting the storage device this parameter must be included if the method is specified as "passphrase" or "obfuscated passphrase" format boolean boolean setting this to true will cause the specified storage device to be reformatted–all existing files will be deleted (but are not guaranteed to be securely erased) before the device is encrypted; however, if the device cannot be reformatted, the operation will fail if set to false , the storage device will be mounted as if it has been previously encrypted using the supplied key if the storage device hasn't been previously encrypted, it will be encrypted while leaving any preexisting files unencrypted if the storage device has been encrypted using a different key, the operation will fail if the format parameter is not specified, the storage device will be mounted as if it has been previously encrypted using the supplied key if the storage device hasn't been previously encrypted, the operation will fail