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

hex-key, ascii-key, quiet, After each compilation

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 41 highlights

Creating Provisioning Scripts Encrypting a File with the SPC 2 Two algorithms are available for this type of encryption: • RC4 (--rc4) • AES (--aes) In addition, the key can be specified either explicitly as a hexadecimal digit sequence (--hex-key) or by hashing a secret phrase (--ascii-key). With the --hexkey option, the key can be up to 256 bits in length. With the --ascii-key option the generated key is 128 bits. The following examples illustrate explicit key-based encryption. spc --rc4 --ascii-key apple4sale spa962.txt spa962.cfg spc --aes --ascii-key lucky777 spa962.txt spa962.cfg spc --aes --ascii-key "my secret phrase" spa962.txt spa962.cfg spc --aes --hex-key 8d23fe7...a5c29 spa962.txt spa962.cfg Any combination of scrambling, targeting, and explicit-key encrypting can be applied to a CFG file, as shown by the following example: spc --target 000e08aaa010 --aes --ascii-key VerySecret a.txt a.cfg After each compilation, SPC prints a final status message. Syntax error messages are also printed if a compilation is not successful. The status and error messages printed by SPC are suppressed with the --quiet command line option. Messages can be redirected to a file with the --log file_name option. In the latter case, the SPC command itself is also printed in the log file, preceded by a timestamp. spc --quiet . . . spc --log prov.log . . . SPC can also be used to generate sample configuration source files (for both plain text and XML formats), corresponding to the accompanying firmware release. The commands for producing sample files are as follows: # sample plain.txt to be used as source file for eventual spc compilation: spc --sample-profile plain.txt # sample config.xml to be fed directly to a device running 2.0.6 or above: spc --sample-xml config.xml Cisco Small Business IP Telephony Devices Provisioning Guide 39

  • 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
Creating Provisioning Scripts
Encrypting a File with the SPC
Cisco Small Business IP Telephony Devices Provisioning Guide
39
2
Two algorithms are available for this type of encryption:
•
RC4 (
--rc4
)
•
AES (
--aes
)
In addition, the key can be specified either explicitly as a hexadecimal digit
sequence (
--hex-key
) or by hashing a secret phrase (
--ascii-key
). With the
--hex-
key
option, the key can be up to 256 bits in length. With the
--ascii-key
option the
generated key is 128 bits.
The following examples illustrate explicit key-based encryption.
spc –-rc4 –-ascii-key apple4sale spa962.txt spa962.cfg
spc –-aes –-ascii-key lucky777 spa962.txt spa962.cfg
spc –-aes –-ascii-key “my secret phrase” spa962.txt spa962.cfg
spc –-aes –-hex-key 8d23fe7...a5c29 spa962.txt spa962.cfg
Any combination of scrambling, targeting, and explicit-key encrypting can be
applied to a CFG file, as shown by the following example:
spc –-target 000e08aaa010 –-aes –-ascii-key VerySecret a.txt a.cfg
After each compilation, SPC prints a final status message. Syntax error messages
are also printed if a compilation is not successful.
The status and error messages printed by SPC are suppressed with the
--quiet
command line option. Messages can be redirected to a file with the
--log
file_name
option. In the latter case, the SPC command itself is also printed in the
log file, preceded by a timestamp.
spc –-quiet . . .
spc –-log prov.log . . .
SPC can also be used to generate sample configuration source files (for both plain
text and XML formats), corresponding to the accompanying firmware release. The
commands for producing sample files are as follows:
# sample plain.txt to be used as source file for eventual spc compilation:
spc –-sample-profile plain.txt
# sample config.xml to be fed directly to a device running 2.0.6 or above:
spc --sample-xml config.xml