![Euresys Picolo.net HD1 Скачать руководство пользователя страница 59](http://html1.mh-extra.com/html/euresys/picolo-net-hd1/picolo-net-hd1_getting-started_2436142059.webp)
59
4.3. AES Storage Control Interface
By default, Picolo.net HD1 boots with AES storage disabled. Any new media clip is then stored as
plain MP4 file and AES-protected present on the USB media will read as an ciphered data if one
tries to get them. When AES storage is enabled, new media clips are encrypted with AES and past
AES-protected files are decrypted on the fly when one tries to download/preview them.
NOTE
AES-protected content is always encrypted on the USB media,
whatever the AES storage status. Files are only decrypted on-the-fly, leaving
no decrypted copy on the media or on the device itself. Similarly, new media
clips are only stored on the USB media after being encrypted and leave no
temporary plain copies behind.
Get AES Storage Status
Reports the current state of the media storage.
The
GetAESStorageStatusRequest
is an empty message.
The
GetAESStorageStatusResponse
holds:
●
exactly one
Directory
string, which is the name of the folder that can be protected by AES
(and used to store media clips) within the
VIDEO
directory of the USB media;
exactly one encryption status string that can be either None (encryption disabled) or AES128
(encryption enabled)
Trying to read the AES storage status when there is no USB media attached, no filesystem or that
the existing filesystem has been unmounted to allow device being ejected will result in a
ter:Action
SOAP fault
Unlock AES Storage
Enable AES encryption on the device.
The
UnlockAESStorageRequest
contains one
Directory
indicating which sub-folder of
VIDEO should be unlocked and a PassPhrase.
The
UnlockAESStorageResponse
is an empty message, indicating that we successfully applied
AES encryption with the given passphrase.
Only directory names reported by
GetAESStorageStatusResponse
are safe to use as
argument of
UnlockAESStorageRequest
The pass phrase should be base-64 encoded, using the conventions of
xs:base64Binary
, and
will be used in its base64 form on the eCryptfs back-end tool.
There will be no check on whether the given passphrase match any previously used passphrase
on this device. A typo in the passphrase will result in new contents to be encrypted with the
"wrong" passphrase while decryption of previously encrypted content will be skipped.
Picolo.net
Getting Started