This process is called "responsible disclosure".
That can lead to "a feeling of false security."
The patches mitigating CVE-2013-1667 are all public.
The patches are public; but whether they actually address the perceived problem -- nor even if the perceived problem is actually a problem -- cannot be determined without knowing what the problem is.
The only code which is not public is the code which demonstrates a key-discovery attack on perls old hash function,
Easily reproduced with a 20 line script. It is running now:
You do not know what you are talking about
Actually, I do. As you will find out.
In reply to Re^10: 5.18.0 is available NOW!
by BrowserUk
in thread 5.18.0 is available NOW!
by Tux
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |