<unaffected range="ge">1.0.2g-r2</unaffected> <vulnerable range="lt">1.0.2g-r2</vulnerable> This is not correct, versions 1.0.2g and 1.0.2g-r1 are not affected, too. This now annoys everyone who did a quick fix with a (local) overlay. I now run a local overlay that has ssl2 entirely disabled. Reproducible: Always
Both ebuilds for -r0 and -r1 expose technical defects. Suggesting users to use those is not a good option.