|
Currently, there are no known upgrades or patches to correct this issue. It is possible to correct the flaw by implementing the following workaround:
1. Set the firewall gateway for VPN, with the "Respond to unauthenticated topology requests" enabled.
2. Set up a sample secuRemote client, and download the site topology.
3. Turn off "Respond to unauthenticated topology requests".
4. Securely distribute the file userc.C from the sample client to all
secuRemote users.
You will need to send out an updated userc.C any time there is a change to
the encryption domain or keying info.
|