Re: [Libcdio-devel] Vulnerable use of strcpy in iso9660_fs.c

2024-05-13 Thread Rocky Bernstein
Just wanted to post a follow-up on this. Mansour Gashasbi has reminded me about this. He is willing to come up with a set of patches for the issues he has come across. So expect a request for comments on this when it come through. (I am back from a wonderful time at BlackHat Asia 2024 - talk text

[Libcdio-devel] Request for Comments: converting libcdio-paranoia C style - which "standard" to use?

2024-05-13 Thread Rocky Bernstein
Recently, I put out a libcdio-paranoia release https://github.com/rocky/libcdio-paranoia/releases/tag/release-10.2%2B2.0.2 to fix a bug that Whipper folks mentioned 6 years ago. For those who have looked at the code, it largely follows the C style used by the original cdparanoia code. This is a s

Re: [Libcdio-devel] Request for Comments: converting libcdio-paranoia C style - which "standard" to use?

2024-05-13 Thread karl
Rocky Bernstein: ... > For example: > > for(;endA > if(buffA[endA]!=buffB[endB])break; Perfectly readable though a little cramped. [ about clang-format etc. ] > First, any thoughts or comments on this? Any thoughts on which of the many > C "standard" styles to use? (The great thing about