Installation guide

10 PC-Duo 12.5 May 2014
Additional Notes
Note on Encryption Fix in 11.6
Connection encryption, which in some circumstances was found to be
intermittent, has been fixed. Below is additional information about the defect, the
circumstances in which the defect may affect performance, and mitigation
options.
Defect Description
By default, connections between Proxy components (for example, Master-to-
Host, Gateway-to-Host, Master-to-Gateway) use encryption (the current version
is set by default to use the AES 256-bit cypher). We have determined that in
certain circumstances, a defect in the encryption code occasionally causes
encryption to be dropped, even though one or both Proxy components are
configured to use encryption.
This defect has been identified in Gateway and Workstation Editions of PC-Duo
versions 10.0 through 11.6.
Defect Scenarios
This defect can affect both peer-to-peer and Gateway-managed connections.
There is no indication to the user when encryption is dropped (for example, the
Lock icon will still show in the status bar of the Master, and Gateway Administrator
will indicate encryption method being used in several places), nor is there any
error message associated with this defect.
However, the defect does not affect the following circumstances:
 Does not affect SSL connections. With SSL protocol, encryption is
explicitly enforced and is unaffected by this defect.
 Does not affect reverse connections. Reverse connections are typically
utilized when Host is outside the domain of the Gateway. Reverse
connections allow Hosts to safely and seamlessly navigate NATs and
firewalls and connect to a Gateway. This is arguably the most vulnerable
connection type (since it can involve sending information over the public
Internet) but it is not affected by this defect, i.e. encryption has been
observed to be always in force.
 The initial connection between Proxy components is not affected by this
defect, so the very first service activity (e.g. remote viewing, recording
playback) will not be affected.
Mitigation Options
Following are mitigation options for this defect:
 No action. For most customers, the intermittent enforcement of
encryption may not be a significant issue, and no action may be
necessary: