Just to add on that, you could create drop-in replacements for selected
packages. You could create MariaDB-10.X-intel-2016b.eb (for instance), update
the easyconfig file every time there is a new release in the 10.X series, and
reinstall it on top of the old one, so bug fixes and security updates could be
applied transparently* to the users and to other packages. That’s normally
something you don’t want to do for reproducibility reasons, but it makes sense
in certain cases.
Damian
*Static libraries might still be an issue though.
On 04/05/17 10:39, "easybuild-requ...@lists.ugent.be on behalf of Jens
Timmerman" <easybuild-requ...@lists.ugent.be on behalf of
jens.timmer...@ugent.be> wrote:
I do realize there exist a few bad scenarios, e.g. software that opens
up sockets to listen to incomming connections such as MariaDB and
mongoDB. If these packages have security issues (or are badly
configured) your users risk loss of confidentiality on their data or
even arbitrary code executing as their user (not root, not a sudo user).
Or a software package that has issues and opens up a users files to the
world.
This would require you to either educate your users not to use the bad
software in an unsafe way, or manually remove it and install a patched
version and tell them to use that version. If you are a non admin user
using EasyBuild to install your own software on a system, you will need
to follow up on this as there is currently nobody paid to do this
centrally for all EB easyconfigs.
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
