From bytes to a verifiable file
A download has a checksum, a register has a hash chain, a document has a signature. Which property does each establish? This reading path starts with bytes and leads to a concrete file exercise.
Understanding SHA-256: from bytes to a hash
Why a SHA-256 hash has 64 hexadecimal characters, how bytes matter and what a checksum actually establishes. With examples, a browser demo and PDF.
Hashing, encryption and digital signatures: the difference
Checksums, confidentiality and verifiable origin serve different purposes. A decision guide for files, backups and software protocols.
Checking files with PowerShell: SHA-256 and the right bytes
A reproducible PowerShell exercise: create a test file, calculate SHA-256, compare line endings and interpret results correctly. With a PDF edition.
These examples connect to my work on belegwerk and Orivane: keeping data traceable, limiting access and correctly assessing what a technical method can establish.
Compact reading editions
These editions develop selected parts of my existing teaching materials. Each PDF includes the author, version, examples and sources. The web edition is the starting point for links, feedback and further content.
Understanding SHA-256
Bytes, hashes and checksum limits
Checking files with PowerShell
An exercise on SHA-256, line endings and result objects
Questions for practical work
For an AI project, an operational handover or a partnership, a shared worksheet often helps more than another abstract term. Save the templates as text files without signing up and fill them in using your own editor.
Evaluating AI agents — worksheet
Document the task, permissions, test cases and observed results separately.
From prototype to operation — discussion worksheet
Discuss key workflows, support, errors, data and changes before use.
Starting a partnership clearly — discussion worksheet
Clarify shared results, contributions, effort and use for a first project.
Use in teaching and discussion
The materials are freely accessible. For a reading recommendation, a course or your own article, link to the relevant article page: explanation, version and download remain available together there.
A reference can include the author, title, year and URL. If you wish to reproduce or adapt an entire resource for your own publication, please discuss its use with me directly. Third-party sources retain their respective terms of use.
I welcome specific corrections, new test cases and experiences from using the materials. For joint articles or workshops, a topic, an audience and a practical question are a good starting point.