Skip to content

Issues: llsoftsec/llsoftsecbook

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
55 Open 27 Closed
55 Open 27 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
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Compiler preserving constant-time property
#213 opened Oct 18, 2023 by swarnpriya
3 👍 2
Consider section on supply chain attacks? content New content for the book
#45 opened Oct 11, 2021 by sam-ellis
@sam-ellis
2 👍 1
Verify everything relevant in related 2021 ACM ToDAES article is present in the book content New content for the book
#78 opened Jan 6, 2022 by kbeyls
👍 1
Consider using archive links instead of direct links for references
#101 opened Apr 1, 2022 by g-kouv
👍 1
Should we add a Glossary to the book? content New content for the book
#6 opened Sep 16, 2021 by kbeyls
1
Check that the book covers everything relevant mentioned in a number of other surveys content New content for the book
#16 opened Sep 24, 2021 by kbeyls
1
Start Timing Attacks section with a definition, use cryptography as an example good first issue Good for newcomers
#44 opened Oct 11, 2021 by sam-ellis
3
Consider section on run-time vulnerabilities in compilers? content New content for the book
#46 opened Oct 11, 2021 by sam-ellis
2
Consider context section on why software security is different for compilers content New content for the book
#48 opened Oct 11, 2021 by lyndon160
4
Consider adding some traffic/visitor analysis to https://llsoftsec.github.io/llsoftsecbook/
#60 opened Nov 19, 2021 by kbeyls
2
Consider synchronising some or all of README.md with the first page of the book
#62 opened Dec 7, 2021 by JLouisKaplan-Arm
2
Design a logo for the project
#74 opened Dec 20, 2021 by kbeyls
Consider section on ABI vulnerabilities content New content for the book
#88 opened Feb 16, 2022 by sam-ellis
1
Should contributors also be listed in the book?
#3 opened Sep 16, 2021 by kbeyls
Should common terms by emphasized/typeset in a consistent way?
#91 opened Feb 18, 2022 by kbeyls
Consider section on binary image exploits content New content for the book
#106 opened Jun 6, 2022 by sam-ellis
1
Write a section/appendix with more information on exploitation content New content for the book good first issue Good for newcomers
#125 opened Jan 3, 2023 by g-kouv
Write section on undefined behaviour and the intersection of optimisation and security content New content for the book
#126 opened Jan 4, 2023 by g-kouv
Chapter about Obfuscation content New content for the book
#127 opened Jan 11, 2023 by Fare9
5
Make HTML output look and feel better HTML Issues relating to the HTML output of the book
#130 opened Jan 16, 2023 by kbeyls
17
Build fails with on latex/pdf output with '! You can't use `macro parameter character #' in horizontal mode.'
#246 opened May 15, 2024 by kbeyls
Convert references in section 5.3.1 into using bibtex good first issue Good for newcomers
#159 opened Feb 21, 2023 by kbeyls
Add a section on threat models content New content for the book
#161 opened Feb 21, 2023 by kbeyls
Describe in more detail why range limitation matters in section 2.2 Exploitation Primitives. content New content for the book
#162 opened Feb 21, 2023 by kbeyls
Should we have a better \index macro?
#90 opened Feb 18, 2022 by kbeyls
ProTip! What’s not been updated in a month: updated:<2025-01-04.