Encrypted Files on the IP Phone
7-6
41-001160-03, Rev 00, Releaes 2.4
IP Phone Administrator Guide
Example 5
Encrypting all cfg files in C:\data with password 1234abcd using the new MAC
encryption and generating a security.tuz file at the same time.(2.2.0 and up)
C:\>
anacrypt -d C:\data -p 1234abcd -m -i
Example 6
Encrypting all cfg files in C:\data with password 1234abcd using the and
generating a security.tuz file at the same time for all firmware versions.(any
version)
C:\>
anacrypt -d C:\data -p 1234abcd -i -v1
Vendor Configuration File Encryption
Some vendors can have specific methods to encrypt files on their configuration
servers. For each phone, the configuration server can generate a random hex string
(encryption key) that is used to encrypt the phone’s MAC-specific configuration
file.
The encryption key is placed in a plain text MAC-specific configuration file that
the server downloads to the phone. After the phone receives the file, it updates the
encryption key.
This method of encryption does not affect the implementation of the Aastra
method of file encryption.
You can set the phone-specific encryption key using the configuration files only.
For more information about configuration file encryption, contact Aastra
Technical Support.
Note:
The
aastra.cfg
file is not encrypted with this feature.
Draft 1
Summary of Contents for 675i Series
Page 4: ...D r a f t 1 ...
Page 26: ...Non Blocking HTTP Connections F 90 XML SIP Notify F 91 Limited Warranty D r a f t 1 ...
Page 30: ...D r a f t 1 ...
Page 70: ...D r a f t 1 ...
Page 90: ...D r a f t 1 ...
Page 745: ...D r a f t 1 ...
Page 1026: ...D r a f t 1 ...
Page 1068: ...D r a f t 1 ...
Page 1072: ...D r a f t 1 ...
Page 1076: ...D r a f t 1 ...
Page 1182: ...Index 12 41 001160 00 Release 2 2 Rev 05 Index D r a f t 1 ...
Page 1183: ...D r a f t 1 ...