Comment 12 for bug 1458052

We've decided this is a "security hardening" measure rather than a security issue, and thus won't apply for a CVE and won't attempt an embargoed coordination with other vendors: any process that has sufficient privileges to read this file and thus the password has every opportunity to perform dozens of other privileged operations that would expose or reset this password.

Ben said he'd follow through with the SRU process; this makes sense to us.

Thanks