Linksys SPA921 Cisco Small Business IP Telephony Devices Provisioning Guide - Page 80

Profile Encryption

Get Linksys SPA921 - Cisco - IP Phone PDF manuals and user guides
UPC - 745883570799
View all Linksys SPA921 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 80 highlights

Provisioning Tutorial Profile Formats 3 Upon resync, the new file is downloaded by the IP Telephony Device and used to update its parameters. The file size of such a small profile is not reduced by gzip. Compression is only useful with larger profiles. For integration into customized back-end provisioning server solutions, the open source zlib compression library can be used in place of the standalone gzip utility to perform the profile compression. However, the IP Telephony Device expects the file to contain a valid gzip header. Profile Encryption A compressed or uncompressed profile can be encrypted. This is useful when the confidentiality of the profile information is of particular concern, such as when using TFTP or HTTP for communication between the IP Telephony Device and the provisioning server. The IP Telephony Device supports symmetric key encryption using the 256-bit AES algorithm. This encryption can be performed using the open source OpenSSL package. Exercise STEP 1 Install OpenSSL on a local PC. This may require recompilation to enable the AES code. STEP 2 Starting from the XML profile in basic.txt, generate an encrypted file with the following command: openssl enc -aes-256-cbc -k MyOwnSecret -in basic.txt -out basic.cfg The compressed basic.txt.gz file could be used instead because the XML profile can be both compressed and encrypted. STEP 3 Store the encrypted file basic.cfg in the TFTP server virtual root directory. STEP 4 Modify the Profile_Rule on the test device to resync to the encrypted file in place of the original XML file. The encryption key is made known to the IP Telephony Device with the following URL option: [--key MyOwnSecret ] tftp://192.168.1.200/basic.cfg Cisco Small Business IP Telephony Devices Provisioning Guide 78

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
Provisioning Tutorial
Profile Formats
Cisco Small Business IP Telephony Devices Provisioning Guide
78
3
Upon resync, the new file is downloaded by the IP Telephony Device and used to
update its parameters.
The file size of such a small profile is not reduced by gzip. Compression is only
useful with larger profiles.
For integration into customized back-end provisioning server solutions, the open
source zlib compression library can be used in place of the standalone gzip utility
to perform the profile compression. However, the IP Telephony Device expects the
file to contain a valid gzip header.
Profile Encryption
A compressed or uncompressed profile can be encrypted. This is useful when the
confidentiality of the profile information is of particular concern, such as when
using TFTP or HTTP for communication between the IP Telephony Device and the
provisioning server.
The IP Telephony Device supports symmetric key encryption using the 256-bit
AES algorithm. This encryption can be performed using the open source
OpenSSL package.
Exercise
STEP 1
Install OpenSSL on a local PC.
This may require recompilation to enable the AES code.
STEP 2
Starting from the XML profile in basic.txt, generate an encrypted file with the
following command:
openssl enc –aes-256-cbc –k MyOwnSecret –in basic.txt –out basic.cfg
The compressed basic.txt.gz file could be used instead because the XML profile
can be both compressed and encrypted.
STEP 3
Store the encrypted file basic.cfg in the TFTP server virtual root directory.
STEP 4
Modify the Profile_Rule on the test device to resync to the encrypted file in place
of the original XML file. The encryption key is made known to the IP Telephony
Device with the following URL option:
[--key MyOwnSecret ] tftp://192.168.1.200/basic.cfg