diff options
author | Sol Jerome <sol.jerome@gmail.com> | 2011-08-11 21:03:59 -0500 |
---|---|---|
committer | Sol Jerome <sol.jerome@gmail.com> | 2011-08-11 21:05:40 -0500 |
commit | 5fe3867a3b75aff04eeb7ba8c910ee6939c1680f (patch) | |
tree | c51844648207860428307bdc4b9dcc7e9bce3e1e /src/lib/Server/Reports/reports/templates/displays/summary.html | |
parent | 9ae39f3eff76015a45b30750cacc354d992c66b4 (diff) | |
download | bcfg2-5fe3867a3b75aff04eeb7ba8c910ee6939c1680f.tar.gz bcfg2-5fe3867a3b75aff04eeb7ba8c910ee6939c1680f.tar.bz2 bcfg2-5fe3867a3b75aff04eeb7ba8c910ee6939c1680f.zip |
Metadata: Better handling of floating cert-authenticated clients (Ticket #1030)
From the ticket:
A floating, cert-authenticated client can be not recognized properly by
hostname if it resolves to an arbitrary name in reverse DNS.
Background: Metadata.resolve_client, called from @exposed Core's
methods, falls back to reverse DNS lookup for client's name, because the
name is not preserved thanks to bailing off early from
Metadata.AuthenticateConnection.
(This issue can be related to #936.)
This patch enables caching of client names for cert-based floating
clients.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
Diffstat (limited to 'src/lib/Server/Reports/reports/templates/displays/summary.html')
0 files changed, 0 insertions, 0 deletions