Re:size_t-to-int vulnerability in Linux’s filesystem layer
by stjohnswarts on Tuesday July 20, 2021 @05:04PM
(#27899310)
Good find thanks for sharing. And everyone at work gripes about me carrying the size around with a lot of my variables in the form of a struct. It's strictly a reminder to always be checking the size since I'm juggling with shotguns.
[ Parent
| on HN ]
Re:size_t-to-int vulnerability in Linux’s filesystem layer
by thayne on Tuesday July 20, 2021 @11:20PM
(#27901988)
The fact that c doesn't have a native concept of an array with length and strings usually use a null byte to determine the end is, IMO c's biggest failing, and it's worst legacy on the wider software world.
Re:size_t-to-int vulnerability in Linux’s filesystem layer
by nextaccountic on Wednesday July 21, 2021 @12:47PM
(#27908673)
This and having any pointer implicitly be nullable
Re:size_t-to-int vulnerability in Linux’s filesystem layer
by GoblinSlayer on Wednesday July 21, 2021 @05:47AM
(#27904196)
Do they even C? It's official ideology: a good programmer compensates shortcomings of the language.
Re:size_t-to-int vulnerability in Linux’s filesystem layer
by stjohnswarts on Wednesday July 21, 2021 @01:06PM
(#27908968)
They seem to be all about the conciseness :) . We have gigabytes of memory, a size parameter isn't going to make a difference haha. The allow me my little idiosyncrasies though so I can't complain.