Depthcharge
What is Depthcharge?
Depthcharge is a toolkit designed to support security research of embedded platforms using the U-Boot bootloader.
It consists of:
- An extensible Python 3 depthcharge module
- Python scripts built atop of the
depthchargemodule API - Depthcharge "Companion" firmware, which is used to perform attacks requiring a malicious peripheral device.
- Some example "helper" payload binaries and build scripts to get you started with U-Boot "standalone" program-esque payloads.
Project Documention
More information can be found in the online documentation for the Depthcharge project.
If you'd like to build this documentation for offline viewing, You can find the Sphinx-based documentation "source" in the doc directory.
Branches
The Depthcharge source repository contains two primary branches:
main- The latest release. This corresponds to what is available on PyPinext- "Bleeding edge" changes scheduled for inclusion in the next release.
At each release, the contents of next are merged to main and tagged accordingly.
Under some circumstances, selected fixes may be merged to main in order publish an interim patch release.
Versioning
Depthcharge uses a Semantic versioning scheme for both the Python API and the Companion Firmware. The version number for published releases will follow that of the Python API version. The CHANGELOG shall document the current version state of both, along with any compatibility information.
Currently, this project uses "unstable" version numbers; API-breaking changes may occur within this minor version series, if deemed to be sufficiently beneficial for the future of the project. Refer to the CHANGELOG for guidance on handling any API changes.
Each published release will have a "codename". This serves no real purpose, other than to amuse the author and add a little fun to preparing releases. (Maybe they'll even be useful to remember!) The codenames are song titles from punk bands, increasing alphabetically with each release.
License
All Depthcharge components are licensed under the BSD 3-Clause License, found in the License.txt file. Project files use the corresponding SPDX Identifier to denote this.
Logo
The Depthcharge logo was created by the incredibly talented Juupiter.
1 maintainer
Metadata
1 maintainer
Release files for depthcharge 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| depthcharge-0.6.0.tar.gz | 163.3 kB | Without provenance | Details for depthcharge-0.6.0.tar.gz |
Release files / depthcharge-0.6.0.tar.gz
| Download URL | depthcharge-0.6.0.tar.gz |
|---|---|
| Size | 163.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3682628020cef92d76c71fe6a068a0c5774c15dfa8b257d124df860619c7c293
|
|
BLAKE2b-256 checksum How to use checksums |
e9d464f6b59c5816db32617cd29a881b5f14784742d827ffaf84617c884864ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.8
|
Security for depthcharge 0.6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
