You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Hiya,
It is pretty annoying (& often irritating) that we can't access the detailed report even when the bugs have been made public (and is fixed).
That said, I would heartily request the relevant information for CVE-2019-19479 so I/we can actually reproduce the bug (accordingly) and see it's significance in the packages shipped by different distributions (I'm primarily concerned with Debian).
The text was updated successfully, but these errors were encountered:
That said, wouldn't it make more sense if the whole report could me made more "open" and available at least after the issue has been made public and is fixed?
What's the point of keeping it hidden anyway?
Hiya,
It is pretty annoying (& often irritating) that we can't access the detailed report even when the bugs have been made public (and is fixed).
That said, I would heartily request the relevant information for CVE-2019-19479 so I/we can actually reproduce the bug (accordingly) and see it's significance in the packages shipped by different distributions (I'm primarily concerned with Debian).
The text was updated successfully, but these errors were encountered: