# abraham DBC files for Lincoln MKZ and Ford Fusion
This is a crowdsourced repository to decode Ford Fusion’s and Lincoln MKZ can bus, we will share data dumps for the different models here and creae issues for each of the id codes.
Issues will have the following format <model acronym><year>x<can id>. For example, for a ford fusion 2017 and id 0x320: FF2017x320, we will share links to data dumps that contain that code and use the ticket description to explain it fully. Once it is explained and added to the .dbc file we can close the ticket.
# How do I help?
Read this before you start: http://www.ioactive.com/pdfs/IOActive_Adventures_in_Automotive_Networks_and_Control_Units.pdf
Help close tickets by creating lines in the DBC that can correctly parse each id.
Add your own data dumps as pull requests and reference interesting bits in the pull requests.
1 maintainer
Metadata
1 maintainer
Release files for abraham 0.1
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 |
|---|---|---|---|---|
| abraham-0.1.tar.gz | 1.7 kB | Without provenance | Details for abraham-0.1.tar.gz |
Release files / abraham-0.1.tar.gz
| Download URL | abraham-0.1.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71e13cee25d95594f0da18f46947a7cccaf3031437355ec1e0ce9bc15bd673a3
|
|
BLAKE2b-256 checksum How to use checksums |
35081f6cef31a5472471595e0cff2c3278200ec07507d5ed32b79a1eb832698a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for abraham 0.1
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.
