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

Create an initial README.md file
#1 by kbeyls was closed Oct 8, 2021
1
Set up github pages, so the book is available online
#8 by kbeyls was closed Oct 4, 2021
1
Make clickable links in PDF output more clearly visible
#27 by kbeyls was closed Oct 7, 2021
1
Also produce a nice-looking HTML version of the book. HTML Issues relating to the HTML output of the book
#28 by kbeyls was closed Oct 4, 2021
2
Shorten chapter 2 title good first issue Good for newcomers
#94 by sam-ellis was closed Jan 4, 2023
Section symbol always present, even without hover, for h4 elements
#147 by JLouisKaplan-Arm was closed Feb 3, 2023
1
Add top-level license file
#4 by kbeyls was closed Sep 20, 2021
1
Write contributors guide
#7 by kbeyls was closed Oct 14, 2021
@kbeyls
1
setup an initial form of CI
#9 by kbeyls was closed Sep 28, 2021
1
Add a copyright and license page to the book
#26 by kbeyls was closed Oct 8, 2021
@kbeyls
1
Hyphenate "low-level" good first issue Good for newcomers
#50 by sam-ellis was closed Oct 15, 2021
1
1
Section 2.8 "JIT compiler vulnerabilities": write section content New content for the book
#171 by kbeyls was closed Apr 4, 2023
@g-kouv
1
Consider incorporation of trojan-source attacks? content New content for the book
#58 by sam-ellis was closed May 6, 2024
2
Docker output for local builds belongs to root
#84 by JLouisKaplan-Arm was closed Feb 25, 2022
2
Consider adding github issue link to TODOs
#156 by kbeyls was closed Feb 22, 2023
@kbeyls
2
Typos
#188 by sam-ellis was closed Mar 7, 2023
2
Should we explicitly list all authors somewhere?
#42 by kbeyls was closed Oct 11, 2021
3
Include brief 'plain english' description of license and copyright of book
#67 by JLouisKaplan-Arm was closed Dec 10, 2021
1
3
Setup https://allcontributors.org/ for the repo.
#2 by kbeyls was closed Sep 29, 2021
5
Concerning timing attacks
#149 by pronesto was closed Feb 15, 2023
1
5
Consider section on underhanded code (detections)
#232 by wanders was closed May 6, 2024
5
Should linear history be enforced?
#10 by kbeyls was closed Sep 16, 2021
6
Make HTML version of book mobile device friendly. HTML Issues relating to the HTML output of the book
#32 by g-kouv was closed Jan 16, 2023
6
Make headings and subheadings directly linkable HTML Issues relating to the HTML output of the book
#64 by JLouisKaplan-Arm was closed Feb 12, 2022
1
6
Write section on securely clearing memory in C/C++ and undefined behaviour. content New content for the book
#183 by kbeyls was closed May 24, 2023
7
ProTip! Follow long discussions with comments:>50.