Encrypting configuration files, Encrypting, Configuration files – Polycom SIP 2.2.2 User Manual

Page 227

Advertising
background image

Miscellaneous Administrative Tasks

C - 3

Thawte Server CA

Thawte Universal CA Root

UPS Document Exchange by DST

ValiCert Class 1 VA

ValiCert Class 2 VA

ValiCert Class 3 VA

VeriSign Class 4 Primary CA

Verisign Class 1 Public Primary Certification Authority

Verisign Class 1 Public Primary Certification Authority - G2

Verisign Class 1 Public Primary Certification Authority - G3

Verisign Class 2 Public Primary Certification Authority

Verisign Class 2 Public Primary Certification Authority - G2

Verisign Class 2 Public Primary Certification Authority - G3

Verisign Class 3 Public Primary Certification Authority

Verisign Class 3 Public Primary Certification Authority - G2

Verisign Class 3 Public Primary Certification Authority - G3

Verisign Class 4 Public Primary Certification Authority - G2

Verisign Class 4 Public Primary Certification Authority - G3

Verisign/RSA Commercial CA

Verisign/RSA Secure Server CA

Encrypting Configuration Files

The phone can recognize encrypted files, which it downloads from the boot

server and it can encrypt files before uploading them to the boot server. There

must be an encryption key on the phone to perform these operations.

Configuration files (excluding the master configuration file), contact

directories, and configuration override files can be encrypted.
A separate SDK, with a readme file, is provided to facilitate key generation and

configuration file encryption and decrypt on a UNIX or Linux server. The

utility is distributed as source code that runs under the UNIX operating

system. For more information, contact Polycom Technical Support.

Advertising