Skip to content

Issues: ossf/wg-best-practices-os-developers

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
20 Open 148 Closed
20 Open 148 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Consider -Wstringop-overflow, -Wno-stringop-overread, and -Wno-stringop-truncation for C and C++ Compiler Hardening Guide Enhancement Product: Compiler Hardening Guide
#882 opened May 7, 2025 by thomasnyman
Consider -fzero-init-padding-bits=all for C and C++ Compiler Hardening Guide Enhancement good first issue Good for newcomers Product: Compiler Hardening Guide
#857 opened Apr 17, 2025 by thomasnyman
2
Add links from Compiler Options Hardening guide to Concise guides Product: Compiler Hardening Guide
#851 opened Apr 8, 2025 by david-a-wheeler Loading…
4
The -Wconversion warning in the Compiler Options Hardening Guide should come with a caveat for brown-field projects good first issue Good for newcomers Product: Compiler Hardening Guide
#819 opened Mar 20, 2025 by thomasnyman
Consider -Wdangling-gsland -Wreturn-stack-address for C and C++ Compiler Hardening Guide Enhancement Product: Compiler Hardening Guide
#684 opened Oct 31, 2024 by thomasnyman
Optimization option recommendations should have caveats Product: Compiler Hardening Guide
#660 opened Oct 14, 2024 by thesamesam
13
_FORTIFY_SOURCE recommendation is a timebomb Product: Compiler Hardening Guide
#659 opened Oct 14, 2024 by thesamesam
8
_FORTIFY_SOURCE guidance confuses people, should suggest undefining with more care (as order matters) Product: Compiler Hardening Guide
#658 opened Oct 14, 2024 by thesamesam
5
Consider -Wl,-z,separate-code for C and C++ Compiler Hardening Guide Enhancement Product: Compiler Hardening Guide
#588 opened Aug 22, 2024 by thomasnyman
1
Create guidance on using buffer overflow attributes in C backlog Enhancement Product: Compiler Hardening Guide
#551 opened Jun 27, 2024 by david-a-wheeler
1
Consider Annobin -grecord-gcc-switches for C and C++ Compiler Hardening Guide Enhancement Product: Compiler Hardening Guide
#509 opened May 30, 2024 by thomasnyman
Review "C style" ideas from mcinglis Product: Compiler Hardening Guide
#498 opened May 20, 2024 by david-a-wheeler
3
Consider documenting additional sanitizers Product: Compiler Hardening Guide
#336 opened Dec 6, 2023 by AaronBallman
1
Evaluate -fsanitize-minimal-runtime for possible hardening Enhancement Product: Compiler Hardening Guide
#326 opened Dec 1, 2023 by david-a-wheeler
1
Review other documents for more C/C++ compiler option ideas Product: Compiler Hardening Guide
#285 opened Nov 9, 2023 by david-a-wheeler
Add -D_LIBCPP_ENABLE_HARDENED_MODE=1 Enhancement Product: Compiler Hardening Guide
#284 opened Nov 8, 2023 by david-a-wheeler
@var-const
12
Compiler attributes for improved security Product: Compiler Hardening Guide
#201 opened Jul 11, 2023 by siddhesh
7
Microsoft C/C++ compiler and linker options are not covered by the hardening guide Product: Compiler Hardening Guide
#150 opened May 2, 2023 by balteravishay
2
Compiler Options: GCC 13.1 analyzer options ok to close? Product: Compiler Hardening Guide
#147 opened Apr 26, 2023 by david-a-wheeler
13
Review "Best and Worst" compiler option flags for our C and C++ guidelines Product: Compiler Hardening Guide
#134 opened Mar 17, 2023 by david-a-wheeler
4
ProTip! Adding no:label will show everything without a label.