Specifications

2-265
Cisco SCE 2000 and SCE 1000 CLI Command Reference
OL-26797-03
Chapter 2 CLI Command Reference
sce-url-database import
The database import file may either contain cleartext or be encrypted. If the file is encrypted, the
matching encryption key must be configured by the database owner.
If the file is encrypted, it must be prefixed with a cleartext header. The encrypted file header format must
be exactly as follows:
Encrypted file version: 0x01
Block cipher index: 0x01
Mode of operation index: 0x02
Padder index: 0x02
IV length: 0x10
IV: <16 unformatted bytes which form the 128 bits IV of the encrypted data >
Following the header, the following data should appear in AES 128, CFB mode, encrypted format:
A random number (in the range [16…31]) of random bytes, followed by the word "Signed", and then
again 32 random bytes.
Each following line represents a single URL.
Protected URL Database Import File Format
[Flavor <tab>] URL
Where:
• Flavor: Flavor-id. The flavor ID must either be included for every line in the file or none of the lines.
The flavor must be separated from the URL by a <tab>.
• URL: (* | [*] [Host-Suffix] | [*] [Host-Suffix] / [URL-Prefix [*]] [URL suffix] [? Params-prefix])
See Table 2-5 for examples of how to define the URL.
Results
• The sce-url-database is first cleared.
• The entries from the file are written to the database.
• Duplicate keys in the file are overwritten with no warning.
• In case of a failure, writing continues to the next entry.
The total number of failures and a listing of the failed file line numbers are reported when the import
is finished.
Authorization: admin
Examples The following example shows how to import the protected URL database from an encrypted file. Since
the flavor-ID is included in the command, this indicates that it is not present in the import file.
SCE>enable 10
Password:<cisco>
SCE#>configure
SCE(config)#interface linecard 0
SCE(config if)#
sce-url-database import encrypted-file blacklist-file flavor-id 50
SCE(config if)#