All sensitive materials are encrypted using a Master Configuration Key (MCK), derived from a
passphrase entered by an administrator. The secrets are then stored in the configuration file
in an encrypted format. This enables copying configurations, including secrets, from one device
to another. The only requirement is that the administrator must generate an identical MCK (by
using the same passphrase) in the target device before executing the copy operation.
Note:
All Gateways have the same default MCK. For security reasons, it is recommended to
configure a new MCK immediately upon Branch Gateway installation.
Related topics:
Configuring the Master Configuration Key
on page 52
Configuring the Master Configuration Key
Procedure
1. Enter
key config-key password-encryption
followed by a phrase of 13 to
64 printable ASCII characters.
2. Copy the running configuration to the start-up configuration using the
copy
running-config startup-config
command.
Result
The new MCK is now in effect.
DoS attacks
The Branch Gateway provides various TCP/IP services and is therefore exposed to a myriad
of TCP/IP based DoS attacks.
“DoS (Denial of Service) attacks” refers to a wide range of malicious attacks that can cause a
denial of one or more services provided by a targeted host.
Related topics:
on page 53
on page 53
on page 54
Commands used to maintain SYN cookies
SYN cookies configuration commands
Accessing the Branch Gateway
52 Administering Avaya G430 Branch Gateway
October 2013
Summary of Contents for G430
Page 1: ...Administering Avaya G430 Branch Gateway Release 6 3 03 603228 Issue 5 October 2013 ...
Page 12: ...12 Administering Avaya G430 Branch Gateway October 2013 ...
Page 246: ...VoIP QoS 246 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Page 556: ...IPSec VPN 556 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...