CVE-2019-3700

yast2-security didn't use secure defaults to protect passwords. This became a problem on 2019-10-07 when configuration files that set secure settings were moved to a different location. As of the 20191022 snapshot the insecure default settings were used until yast2-security switched to stronger...

CVE-2019-3700

The CVE-2019-3700 entry relates to yast2-security not using secure defaults for passwords. Technical details across connected records show insecure defaults used prior to version 4.2.6, with password hashes potentially protected poorly due to DES encryption. The fix stated is that yast2-security ...