Encrypting And Decrypting Configuration Files - Yealink CP969 Administrator's Manual

AES keys must be 16 characters and the supported characters contain: 0-9, A-Z, a-z and the
following special characters are also supported: # $ % * + , - . : = ? @ [ ] ^ _ { } ~.
Click Confirm to accept the change.
3.
To configure AES keys via phone user interface:
Tap Settings->Advanced (default password: admin) ->Set AES Key.
1.
Enter the values in the Common AES and MAC-Oriented AES fields.
2.
AES keys must be 16 characters and the supported characters contain: 0-9, A-Z, a-z and the
following special characters are also supported: # $ % * + , - . : = ? @ [ ] ^ _ { } ~.
Tap to accept the change.
3.

Encrypting and Decrypting Configuration Files

Encrypted configuration files can be downloaded from the provisioning server to protect against
unauthorized access and tampering of sensitive information (e.g., login passwords, registration
information).
Yealink supplies a configuration encryption tool for encrypting configuration files. The
encryption tool encrypts plaintext configuration files (e.g., account.cfg, <y0000000000xx>.cfg,
<MAC>.cfg) (one by one or in batch) using 16-character symmetric keys (the same or different
keys for configuration files) and generates encrypted configuration files with the same file name
as before.
You can also configure the <MAC>-local.cfg files to be automatically encrypted using
Note
16-character symmetric keys when uploading to the server (by setting the value of the parameter
"static.auto_provision.encryption.config" to 1).
This tool also encrypts the plaintext 16-character symmetric keys using a fixed key, which is the
same as the one built in the IP phone, and generates new files named as <xx_Security>.enc (xx
indicates the name of the configuration file, for example, y000000000058_Security.enc for
Configuring Security Features
717