Andrea wrote > I don't think your argument is valid, according to it you could, absurdly, > always replace the owner password with a random string (even when the user > provided it) and still strictly don't contradict the spec (there is an > owner password, *a random string*, algorithm 3.3 applies).
If that is the way that API is documented, i.e. if its claimed functionality is to ignore some input and use a random string instead, then that is completely ok. It merely might not be the functionality or API you are after. Obviously in the case at hand we are not in such a funny situation. Instead, if you want to use the same user and owner password, supply them identically. Regards, Michael -- View this message in context: http://itext-general.2136553.n4.nabble.com/Encrypt-without-owner-password-and-random-password-generation-tp4659839p4659848.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
