Hello, I've startet creating a crypto engine for pdfbox. The aim is to provide a highlevel api for signing and verifying pdf documents.
The engine is called cryptobox and is splited into a 1.8.x and main branch. After the basic functions are ready in the 1.8.x, I will do a pdfbox 2.0.x port and clean up the signature interface. The goal is to do a pdfbox reference implementation for PAdES [1] up to part 4 of the specification or I will go straight to the Europen Union Commision Decision [2]. I hope with the help of the community, we have a chance to reach the goal. At the moment the code is hosted on github [3] but I will move it to the apache repository after the codebase reached a usable level. It is easier for me to prepare the code and play with it on github (less restrictions). From 4 to 29 May 2015 ETSI is making a PAdES PlugTest [4], I'm already a participant and will try to test the cryptobox. So I first try to go through the specification and later port stuff like visual signatures. Maybe we can participant as Apache at such plugtests, so we can gain more publicity. I don't made much planing, but I think this roadmap could be a good start: - Implement pdf signatures and verification for the ISO 32000-1:2008 specification. - Implement the ETSI signature specification PAdES (deadline is the PlugTest) - Basic signature service, maybe webservice or gui application. - Port the visual signature stuff that already exist and maybe start a table based visualisation (without the need to create pictures) - Port it to pdfbox 2.0.x with NonSeqParser - Cleanup the existing pdfbox signature code other parts that need to be done are: - refactor signature interface and coswriter - make pdf signature streamable without the dirty hooks that are needed now. - there where already plans to move the pdf encryption from pdfbox to a new module. Maybe we can move it into the cryptobox. I don't want promise anything, so I try mainly get through the plugtest and show how the feedback is. If you have some ideas how the cryptobox can be improved or maybe how the architecture may look like to provide best usability, then please give me some suggestions. Best regards Thomas [1] http://www.etsi.org/news-events/news/324-news-release-14th-september-2009 [2] http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32011D0130 [3] https://github.com/Rayman2200/cryptobox/tree/1.8 [4] http://xades-portal.etsi.org/pub/index.shtml --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org
