-
Notifications
You must be signed in to change notification settings - Fork 53
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Should contributors also be listed in the book?
#3
opened Sep 16, 2021 by
kbeyls
updated Sep 16, 2021
Should we add a Glossary to the book?
content
New content for the book
#6
opened Sep 16, 2021 by
kbeyls
updated Oct 11, 2021
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
updated Oct 11, 2021
Should we add an "assumed knowledge"/"prerequisites" section?
content
New content for the book
#5
opened Sep 16, 2021 by
kbeyls
updated Nov 10, 2021
Consider adding some traffic/visitor analysis to https://llsoftsec.github.io/llsoftsecbook/
#60
opened Nov 19, 2021 by
kbeyls
updated Nov 19, 2021
2
Consider synchronising some or all of README.md with the first page of the book
#62
opened Dec 7, 2021 by
JLouisKaplan-Arm
updated Dec 8, 2021
Should common terms by emphasized/typeset in a consistent way?
#91
opened Feb 18, 2022 by
kbeyls
updated Feb 18, 2022
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
updated Mar 22, 2022
Consider using archive links instead of direct links for references
#101
opened Apr 1, 2022 by
g-kouv
updated Apr 1, 2022
Consider section on supply chain attacks?
content
New content for the book
#45
opened Oct 11, 2021 by
sam-ellis
updated Jan 16, 2023
Consider section on run-time vulnerabilities in compilers?
content
New content for the book
#46
opened Oct 11, 2021 by
sam-ellis
updated Jan 16, 2023
Consider context section on why software security is different for compilers
content
New content for the book
#48
opened Oct 11, 2021 by
lyndon160
updated Jan 16, 2023
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
updated Jan 16, 2023
Consider section on ABI vulnerabilities
content
New content for the book
#88
opened Feb 16, 2022 by
sam-ellis
updated Jan 16, 2023
Consider section on binary image exploits
content
New content for the book
#106
opened Jun 6, 2022 by
sam-ellis
updated Jan 16, 2023
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
updated Jan 16, 2023
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
updated Jan 16, 2023
Chapter about Obfuscation
content
New content for the book
#127
opened Jan 11, 2023 by
Fare9
updated Jan 16, 2023
Convert references in section 5.3.1 into using bibtex
good first issue
Good for newcomers
#159
opened Feb 21, 2023 by
kbeyls
updated Feb 21, 2023
Add a section on threat models
content
New content for the book
#161
opened Feb 21, 2023 by
kbeyls
updated Feb 21, 2023
Section 2.4.2 "Jump-oriented Programming": Use "real" instead of made-up gadgets in example
content
New content for the book
#165
opened Feb 21, 2023 by
kbeyls
updated Feb 21, 2023
Section 2.5.2.3 "Pointer Authentication": add more references to relevant research
content
New content for the book
#166
opened Feb 21, 2023 by
kbeyls
updated Feb 21, 2023
Section 2.5.2.3 "Pointer Authentication": Also describe other uses of FEAT_PAuth in a later section and refer to it
content
New content for the book
#167
opened Feb 21, 2023 by
kbeyls
updated Feb 21, 2023
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.