Encrypting A File With The Spc - Cisco SPA921 - - IP Phone Provisioning Manual

Creating Provisioning Scripts

Encrypting a File with the SPC

Encrypting a File with the SPC
Cisco Small Business IP Telephony Devices Provisioning Guide
The SPC can generate different types of configuration files, using different types
of encryption.
• Generic, non-targeted CFG file, without an explicit key
• Targeted (--target option), also encrypts the CFG file without an explicit
key, but uses the MAC address of the target IP Telephony Device, and only
that device can decode it
• Explicit key-based encryption of the CFG file.
A generic, non-targeted CFG file is accepted as valid by any IP Telephony Device
that resyncs to it. The following command generates a basic CFG file:
spc spa962.txt spa962.cfg
This example compiles the plain-text spa962.txt file into the binary spa962.cfg file
understood by the SPA962. The --scramble option performs encryption that does
not require the explicit transmission of a key to the target device. It requires one
randomizing argument. For example,
spc --scramble SomeSecretPhrase spa962.txt spa962.cfg
The resulting encrypted spa962.cfg is accepted as valid by any IP Telephony
Device that resyncs to it.
The --target option also encrypts the CFG file without the need to explicitly
transmit a key, but does so in such a way that only the target IP Telephony Device
can decode it. Targeted CFG files provide a basic level of security. This command
uses the MAC address of the target device as an argument. Refer to the following
example:
spc --target 000e08aabbcc spa962.txt spa962.cfg
This command uses the MAC address 000e08aabbcc, and only the IP Telephony
Device with that MAC address is able to decrypt and process the generated
spa962.cfg profile. If any other IP Telephony Device attempts to resync to this file,
the device will reject the file as unreadable.
The third option performs an explicit key-based encryption of the CFG file. This
option requires that the key used to encrypt the file be preprovisioned in the target
device, so that it can be decoded.
2
38