Digital signature on code
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- cryptography, security
Research direction
The issue does not name any files, tests, or entry points. Start by reviewing the existing G-code format and the standard packaging formats and support libraries mentioned, then define the signing and verification scope, format, compatibility requirements, and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Description
Something sorely needed in the CNC world is security. GCode isn't just used for 3D printing, it is used in CNC equipment moving tons of material at high speed. We have actual real world instances of state actors corrupting code to destroy machinery.
Making space for a digital signature wrapper around the Gcode would provide the option of signing it. Basically you just have a preamble saying it is going to be signed and the digest value is X and then comes the data and then the computed signature goes at the end.
While 3D printers don't move massive amounts of material in quite the same way as a CNC lathe, signatures could be very useful for making copyright claims. In a production environment, they can be used to make sure that printers are building the correct part rather than a modified one.
There are standard packaging formats and support libraries that can be used.
- Dominant language
- G-code
- Stars
- 73
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from prusa3d/libbgcode
-
Extending bgcodeOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Broken on big-endian architecturesPossibly taken @onitake claimed this 334 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
PyPI releaseMay be free again @tomasbedrich claimed this 1035 days ago, and no pull request is open. Open
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
All issues in prusa3d/libbgcode
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
cms: `OtherRevocationInfoFormat.other_format` should be an OBJECT IDENTIFIERPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
RustCrypto/formats#2543 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
flashbots/panetiere#46 · 1 comment ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
btclib-org/btclib-ecc#595 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
btclib-org/btclib#3143 ·
Maintainers usually reply within 1 day