search for: _secure

...have other assurances that the target buffer has sufficient space. The performance difference can be significant, since usually memcpy will be turned into a compiler builtin that the compiler recognizes and optimizes specially, whereas with the suggested approach, a regular call into a "llvm::*_secure" wrapper which then calls into the OS-provided general-purpose "secure" version will happen. I think that it would be useful if you used the output of your static analyzer to provide a list of the places where C-style string manipulation is being done, so that these places can be mi...

...veloper should know about. The general interest book will be something fiction or nonfiction that is interesting to the folks who hang around here :-). To get things rolling, here are our books for January: Users: _Ethernet: The Definitive Guide_, from O'Reilly. ISBN 1565926609 Developers: _Secure Programming Cookbook for C and C++_, also from ORA. ISBN 0596003943** General Interest: _Cuckoo's Egg_, by Cliff Stoll. ISBN 0743411463 So, head out to your favorite bookstore and join #asterisk-bookclub! See ya on IRC, Nick (IRC hermie)

...have other assurances that the target buffer has sufficient space. The performance difference can be significant, since usually memcpy will be turned into a compiler builtin that the compiler recognizes and optimizes specially, whereas with the suggested approach, a regular call into a "llvm::*_secure" wrapper which then calls into the OS-provided general-purpose "secure" version will happen. I think that it would be useful if you used the output of your static analyzer to provide a list of the places where C-style string manipulation is being done, so that these places can be mi...

...le their implementation will be platform specific (like the Mutex class in Support module). In cases where the platform does not support the functionality natively, we are writing an implementation of these functions. For example, in the case of memcpy the secure function will look like llvm::memcpy_secure. Some secure functions require additional data that needs to be passed (like buffer sizes). That information has to be added in all places of invocation. In some cases, this requires an extra size_t argument to be passed through. Hence, this change would not just be a one to one function refacto...

...ion will be platform specific (like > the Mutex class in Support module). In cases where the platform does not > support the functionality natively, we are writing an implementation of > these functions. For example, in the case of memcpy the secure function > will look like llvm::memcpy_secure. > > Some secure functions require additional data that needs to be passed > (like buffer sizes). That information has to be added in all places of > invocation. In some cases, this requires an extra size_t argument to be > passed through. Hence, this change would not just be a one t...