New answers tagged

0

Redhat provides the necessary CVE to package version information. For any provided CVE the package version may (and as I have found in my own experience) may not correspond to the original package version. Example source from developer for package ABC is v0.0.3 which addresses CVE 1.1 where RedHats RPM of ABC is at v0.0.2x for release 6 and at v0.0.3 for ...


1

Providing the SA and version should be good enough since the SSH patch has been implemented. If they have problems with this then they would have to take it up with Redhat version control themselves. After all if you can demonstrate that the attack will not work because it has been patched, version number means nothing. It's already patched regardless of ...


0

What you need to address is the issue, and whether or not the issue is fixed, or if there is a compensating control to address the vulnerability. If there isn't a patch for a vulnerability, you would be out of compliance however if you had rules that illustrated that you blocked all, but allowed only trusted (vetted sources) you now have a compensating ...


0

TL:DR; you'd have to setup a transparent proxy on your VPN server. You can reroute all outgoing traffic to port 443 from your VPN server (which are, probably, your VPN clients) using iptables. After this you could run an intercepting proxy such as mitmproxy which takes care of the SSL bit as well. First off, you redirect all outgoing web traffic to ...



Top 50 recent answers are included