Sign Document - Feature Request.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I am trying to use a Certificate to Sign a PDF document. I have managed to generate a P12 file and sign the PDF attaching the certificate into the PDF.
When looking at the Certificate is says the certificate has no parent which is correct.
Would it be possible for Keybase to generate a document signing p12 or pem based on the data it holds as it already understands the personal key and has proof of ownership?
The perfect secure solution would be to generate a certificate in memory then sign and attach the certificate to the PDF not returning the certificate. The certificate would only be available for users who have a proven identity.
The sign API will sign a document but it is not visible to the user when viewing it which does not meet my requirements.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No files, tests, or entry points are named. Start by locating the existing document-signing API and its certificate-handling code, then review how Keybase identity proof could connect to PDF signing. Done would mean an agreed design and supported path for producing a verifiable signed PDF without returning the private certificate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100