Andrea, Andrea wrote > I found what seemed a little discrepancy with the spec and I asked why, > that's it. > I spent time re-reading the spec, comparing it with your implementation > and writing a detailed email because I thought it was useful for me to > understand it but might also be good for iText.
Of course input on situations in which iText might not act as a conforming reader or writer (or conforming PDF processor as the lingo will develop to) is important. But in my eyes you misunderstand one aspect: the PDF specification foremost does not specify APIs or GUIs of PDF processors: > ISO 32000-1 does not prescribe any specific technical design, user > interface or implementation details of conforming writers (section 2.3 Conforming writers) Instead its requirements > focus on the creation of conforming files. (ibidem) The upcoming PDF-2 formulates this even more clearly. Thus, the specification in the context at hand: > Algorithm 3: Computing the encryption dictionary’s O (owner password) > value > a)Pad or truncate the owner password string as described in step (a) of > "Algorithm 2: Computing an encryption key". If there is no owner password, > use the user password instead. does *not* rule how to design an application programming or graphical user interface but instead rules how the very code in such a library or application "computing the encryption dictionary’s O (owner password) value" shall default. I.e. the "owner password" may be provided by the API caller and merely forwarded through the API, or it may be provided by the API itself; only in the absence of any predetermination of that password, the spec says what to do. When interpreting ISO 32000 one always has to keep in mind that this specification of the file format PDF is derived from a series of PDF references (not normative in nature) which were written to help programmers understand how Adobe Acrobat and Reader handle PDF files and allow their own code to be as compatible as possible. So there are numerous sections in the specification still formulated with the Acrobat or Reader in mind without this Acrobat or Reader behavior being normative. Regards, Michael -- View this message in context: http://itext-general.2136553.n4.nabble.com/Encrypt-without-owner-password-and-random-password-generation-tp4659839p4659847.html Sent from the iText - General mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions iText(R) is a registered trademark of 1T3XT BVBA. Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/ Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php
