[Pkg-scicomp-devel] Bug#441478: [ptb at inv.it.uc3m.es: Bug#441478: libglpk0: security flaw buffer overflow in glplib05.c xvprintf]

[Andrew Makhorin]

> Actually, there is a way to circumvent the problem. It is quite ugly
> and I am not sure you would like to implement it. Here is it: make
> the functions xprintf and xprint1 both static, and move them,
> together with xvprintf, into a header file (.h) which will be
> included by all other files calling xprintf or xprint1. The only
> side effect is that the resulting shared library will increase in
> size.

Rafael,

I do not understand the problem. There are many internal glpk routines
prefixed by '_glp_', which, in principle, can be called from the user
program. However, there is a common convention not to call such routines
from outside.