
PROBLEM: (BE_G04155) (PATCH ID: OSF520-682)
********
This patch corrects a problem using MD5 authentication with Version 2 RIP


PROBLEM: (TKT383174, DE_G05224, TKT416062, TKT398755,
          TKT367516) (PATCH ID: OSF520-978)
********
This patch resolves a problem where the cluster interconnect route is
inappropriately advertised.


PROBLEM: (95082) (PATCH ID: OSF520-1052)
********
If a static and/or loopback host route is added via
routing socket, 'gated' deletes this route upon
route aging time-out.  In cluster alias environment,
this will cause all TCP/UDP packets destined to
the cluster alias address being mis-handled.


PROBLEM: (95812) (PATCH ID: OSF520-1063)
********
This patch corrects a problem with gated not recognizing a valid option
'aliases-nexthop' in geted.config.  Gated now correctly recognizes the option
and preferes the nexthop address based on the preference specified by the
option.


PROBLEM: (95884, TKT441149) (PATCH ID: OSF520-1143)
********
This fix corrects a problem where, under cirtain circumstances, a route
added through the /sbin/route command will not be honored by GateD and
will be removed.  This happens when a node has a multinet interface
(interface with 2 addresses configured in different subnets) and a route
being added is in the second subnet (i.e subnet that appears second in
the output of /usr/sbin/ifconfig).


PROBLEM: (88449, 88453) (PATCH ID: OSF520-1168)
********
A potential security vulnerability has been discovered, where under
certain circumstances, system integrity may be compromised. This may
occur when Gated deamon or Gated Control utility (gdc) incorrectly
access temporary files.



