First, this is a chicken/egg problem: standardisation comitee tend to standard what is widely used, witness gcc extension: many of them were incorporated into C99 and if gcc developpers hadn't push for them we would probably have a less useful C language now.
Then, who really cares about information leak??? Buffer overflow is a much much bigger problem, this is a very bad excuse.
Please stop making stupid excuse against inclusion such as 'programmers must manage perfectly their strings' from somebodytookmyname, in the real world programmers makes mistakes, security mistakes are very hard to spot as normal use case don't see any bad behaviour, providing an API which is safe and simple to use is very useful so glibc should include it, Ulrich Drepper is just being stupid..
Hopefuly, the next C standardisation will include such kind of function, but what a waste of time..
First, this is a chicken/egg
First, this is a chicken/egg problem: standardisation comitee tend to standard what is widely used, witness gcc extension: many of them were incorporated into C99 and if gcc developpers hadn't push for them we would probably have a less useful C language now.
Then, who really cares about information leak??? Buffer overflow is a much much bigger problem, this is a very bad excuse.
Please stop making stupid excuse against inclusion such as 'programmers must manage perfectly their strings' from somebodytookmyname, in the real world programmers makes mistakes, security mistakes are very hard to spot as normal use case don't see any bad behaviour, providing an API which is safe and simple to use is very useful so glibc should include it, Ulrich Drepper is just being stupid..
Hopefuly, the next C standardisation will include such kind of function, but what a waste of time..