[Freedombox-discuss] Java vulnerabilities
pere at hungry.com
Wed Jun 17 05:52:53 UTC 2015
> A rather scary article:
I find the article mostly stupid, I must admit. It keep repeating that
the problem is caused by the use of open source components, while in
reality the situation is worse when using proprietary components, at
least based on my experience in both free and proprietary software
development. Using old software components is a risk, and in the free
software world it is easier to get access to the new components.
> Does the current Fbox implementation use Java? Should we eliminate it
> as a matter of necessary security policy? If not, how can we deal with
> these issues?
As far as I know, nothing in the current Freedombox uses Java. But that
is really beside the point.
Perl and Python is a specially high risk, I believe you have
misunderstood something. If you do not claim this, I fail to understand
what you mean. The free software implementations of Perl and Python are
of very high quality compared to proprietary software according to
so it is not possible to make a sensible general statement about its
More information about the Freedombox-discuss