Summary: | app-text/acroread | ||
---|---|---|---|
Product: | Gentoo Security | Reporter: | Daniel Ahlberg (RETIRED) <aliz> |
Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | usata |
Priority: | Highest | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Daniel Ahlberg (RETIRED)
2003-08-17 01:06:55 UTC
Acrobat 5.0.8 was released on 8 Aug, and I committed acrobat-5.0.8.ebuild on 11 Aug. Acrobat 5.0.8 seems to have this problem solved. (But I haven't marked it as stable yet) Are you sure you committed acrobat vs acroread ? If infact you commited acroread it now appears its been marked stable and we could close this bug. Sorry it was my typo. I didn't mean acrobat but acroread. It's okay for me to close this bug. btw, how do we deal with former releases? I think we could remove them and leave 5.08 alone in Portage tree, but if we are to keep them we better to mask them in /usr/portage/package.mask I'd vote for removal of old exploiable versions of packages, but thats your call as the maintainer. I removed them from Portage tree. I suppose we could close this bug. closing |