fixes for PDF

Author: nocomplexity

constructs/assert.md

@@ -62,8 +62,7 @@ For AI-generated, Python programs you will see a lot of assert statement warning
 
 For production code, especially when handling external inputs or executing critical logic, always rely on explicit condition checks and robust exception handling.
 
-:::{admonition} Instead of an assert, use standard control flow and exception raising
-:class: hint
+:::{hint} Instead of an assert, use standard control flow and exception raising
 
 * Use if/else checks: Explicitly validate inputs and conditions.
 

constructs/builtins.md

@@ -15,8 +15,8 @@ Should always be reviewed within the full context. By default use of this functi
 
 ## Why check on `eval`
 
-:::{admonition} Security risk
-:class: danger
+:::{danger} Security risk
+
 `eval()` can execute arbitrary Python code. 
 
 If the input is user-controlled or from an untrusted source, this can be exploited.

constructs/constructs_intro.md

@@ -6,7 +6,42 @@ short_title: Dangerous Python Constructs
 
 Certain Python language features pose inherent security risks. The following subsections detail specific dangerous constructs found within the [Python Standard Library(PSL)](#PSL).
 
++++{"no-pdf": true}
 
 :::{toc}
 :context: children
 :::
+
++++
+
+:::{raw:typst}
+*Sections*
+
+Assert Statement
+Input Statement
+Built-in Functions eval, exec and compile
+The os.chmod Function
+The socket.bind() Method
+Directory Creation
+Dynamic Import Statements
+Exception Statements
+TarFile Statement
+Insecure Hashing
+FTP Statement
+Marshal Statement
+Mktemp Statement
+Subprocess Statement
+OS System Calls
+Logging Configuration
+Base64 Statements
+HTTP Server Use
+Multiprocessing Module `Connection.recv()`
+Pickle Function
+Random Statement
+Shelve Module
+sys Module:Tracing and Profiling Hooks
+XML Security
+Zipfile Extraction
+Shutil Statement
+
+:::

constructs/tarfile.md

@@ -8,8 +8,7 @@ Using these methods in Python code can give serious security concerns.
 ## Security concerns
 
 
-:::{admonition} The default rule is:
-:class: danger
+:::{danger} The default rule is:
 Assume all input is malicious.
 :::
 

fundamentals/fundamentals_intro.md

@@ -9,8 +9,33 @@ short_title: Fundamentals
 Developing secure programs in Python requires understanding its strengths and limitations in handling security. Below are some critical insights and best practices to help you build secure Python applications.  
 
 
++++{"no-pdf": true}
+
 The key fundamentals to really understand Python security weaknesses are outlined in the following sections:
 
 :::{toc}
 :context: children
 :::
+
++++
+
+
+:::{raw:typst}
+
+*Sections*
+
+The key fundamentals to really understand Python security weaknesses are outlined in the following sections:
+
+- Python Execution Model
+- Python bytecode security concerns
+- Python Threat Model
+- Python Attack Landscape
+- Python Software Dependencies and Definitions
+- Python Static Application Security Testing (SAST)
+- Using python -S for Enhanced Security
+- Python in Isolated Mode
+- Using AI for Python security
+- Limitations of Vulnerability Scanning in Python Software
+- SAST vs Vulnerability Scanning:A Comparison
+
+:::

guidelines/guidelines_intro.md

@@ -15,7 +15,10 @@ In many mature professions, checklists have become a mandatory safeguard against
 
 ![Checklists](../images/checklists.png)
 
++++{"no-pdf": true}
 
 :::{toc}
 :context: children
 :::
+
++++

guidelines/securecoding.md

@@ -104,8 +104,7 @@ When using External Modules:
  +++
 
 
-:::{admonition} **Disclaimer**  
-:class: note
+:::{note} **Disclaimer**  
 
 These **Python Secure Coding Guidelines** are based on real-world breaches and [CWE](https://cwe.mitre.org/index.html) entries from the *Most Dangerous Software Weaknesses* list.  
 

images/PythonSecurity_bookcover_large.png

@@ -28,8 +28,7 @@ This book is created for modern Python use. This means all examples are minimal
 Security is a process that must be embedded within your development flow at every stage, from design through to production, maintenance, and operations. For those using or developing Python programs, this means that security should, at a minimum, be integrated into the initial design or architecture.
 :::
 
-:::{admonition} TLDR - If you short on time
-:class: important
+:::{important} TLDR - If you short on time
 The bare minimum to do as programmer is:
 * Follow and use the [Python Secure Coding Guidelines](https://nocomplexity.com/documents/codeaudit/securecoding.html).
 
@@ -43,6 +42,16 @@ and:
 
 No single book can cover every aspect of Python security. Here are the **essential** companion resources that many Python developers and security consultants rely on to strengthen their skills and deliver better results.
 
+:::{raw:typst}
+
+- Security Testing for Python
+- Security By Design
+- Open Security Reference Architecture
+
+Check: https://nocomplexity.com/simplify-security/
+:::
+
++++{"no-pdf": true}
 ::::{grid} 1 1 2 3
 
 :::{card} 😃 **Python Security Handbook**  
@@ -91,6 +100,7 @@ Accelerate your Python security architecture work with proven patterns and desig
 :::
 
 ::::
++++
 
 
 ## Audience

introduction.md

@@ -16,6 +16,7 @@ project:
 
 extends:
   - toc.yml
+  #- export.yml #For PDF creation - See https://nocomplexity.gumroad.com/ for the PDF! 
 
 site:
   parts: