BrandonJWilhite on Thu, 02 Mar 2017 13:28:23
Is there a way other than the registry edit workaround to prevent this error? Maybe has the problem been fixed (I'm guessing not)?
If the registry edit is still the only way around, what are the security implications of this? The blog post is unclear on how safe/un-safe doing this is.
Workaround I'm talking about:
BrandonJWilhite on Thu, 02 Mar 2017 13:37:09
EDIT: Nope, that was in reference to a different, but related security update.
A little more digging...it seems that the security update that is needing worked around is meant to address a vulnerability in *serving* encrypted web traffic. If the machine I am installing the hybrid connection listener on does not *serve* any web traffic would that mitigate my risk?