Timeline for OpenSSL version causes PCI Compliance failure
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 29, 2017 at 3:44 | history | tweeted | twitter.com/StackSecurity/status/858164996110524416 | ||
| Mar 9, 2017 at 17:14 | comment | added | Craig Jacobs | I hear what you're saying. I actually really like AMI becasue they patch it almost continuously and it generally seems to be up to date. I'm getting irritated with the PCI people because Amazon states that they have backported those CVEs to their distro, and the PCI people seem to only want to look at the reported version AFAIK RHEL and CentOS do the same, so I suspect I'd have the same issue there - OpenSSL is 1.0.1e. I'm not quite ready to give up on AMI yet, but I may have to. | |
| Mar 9, 2017 at 11:46 | comment | added | Gewure | Note: I've once installed AMI just to find out that it was probably the worst-case choice available. If its an option, stick to distributions which have an actual community, not just a company, behind them. Ubuntu Server or some Debian are usually the best choice, else the RedHat Distris (CentOS, Fedora..). | |
| Mar 9, 2017 at 3:35 | vote | accept | Craig Jacobs | ||
| Mar 9, 2017 at 3:05 | answer | added | Trey Blalock | timeline score: 3 | |
| Mar 9, 2017 at 1:55 | history | asked | Craig Jacobs | CC BY-SA 3.0 |