Non-Hashed Passwords; Self-Signed Certificate Creation - Polycom 1500 Administrator's Manual

RealPresence Collaboration Server (RMX) 1500/1800/2000/4000 Administrator's Guide

Non-hashed Passwords

All non-hashed passwords are stored encrypted as set out in Table 5-54.
Non-hashed Passwords - Encryption
Connection
SNMPv3
Two passwords: Authentication
/ Privacy
Exchange
RV v.35 serial ports – password
for login
H.323 authentication –
password
SIP digest – password
In compliance with UC APL requirements, PKI Self-signed Certificates are supported for the both the
Default Management and IP Network Services.
A mixture of Self-signed and CA-signed Certificates is supported, however a CA-signed certificate will
always override a Self-signed Certificate.

Self-signed Certificate Creation

Self-signed Certificates are created during:
● Initial system start-up before any CA-signed Certificates have been installed.
● IP Network Services creation.
● Network Services updates that result in Host Name changes.
● Daily validity checks of Self-signed Certificates.
● Backup and Restore of the system configuration
Self-signed Certificate field values are automatically inserted when the certificate is created
:
Self-signed Certificate - Creation
Field
Signature Algorithm
Polycom®, Inc.
Storage type
Community permissions which are not
the PW to connect to SNMP are not
Saved Encrypted
Non encrypted – Feature disabled in
Ultra Secure Mode
Reversible – AES_128 with 256 Bytes
Key (2048 Bits)
Reversible – AES_128 with 256 Bytes
Key (2048 Bits)
Reversible – AES_128 with 256 Bytes
Key (2048 Bits)
Value
SHA1
Previous From
Versions Version 8.1
Non encrypted AES 256
Non encrypted AES 256
AES 256 AES 256
AES 256 AES 256
AES 256 AES 256
853