Even if your program does in fact offer AES encryption, why not offer 256-bit encipherment, which was introduced by Acrobat 9.0? True, some choose not to use it, in order to maximize compatibility with potential end-users, but that's clearly not an issue for general home use, or if one is using your program strictly inside an organization where version capabilities are known in advance. Unless that's just an oversight on your behalf.Ģ.
#Winx hd video converter deluxe 5.9.8 pdf#
128-bit what? Are you implementing the much weaker 128-bit RC4 cipher, or the stronger 128-bit AES which became available starting with PDF version 7.0? I'm assuming it's the older RC4 implementation, otherwise you'd have to mention the issue of compatibility (a PDF app or plugin which is PDF 6.0 compatible would not be able to open a document encrypted with the newer ciphers, for example), which you do not do. You mention 128-bit encryption a number of times. But in your case, this battle is not lost due merely to the narrow focus of your program it's lost due to how poorly it's implemented- and presented:ġ. In the case of PDF encryption, a function offered by a whole array of existing, free PDF readers and general PDF utilities-usually appearing as just one in a whole host of other useful features-you really have an uphill battle. But for me to even take the time to download a program with such a narrow feature set, someone needs to do an exceptional job at explaining why I might want to choose it over competing products. As someone who works frequently with PDF's, I'm usually inclined to try new tools which process these documents, even a one-trick pony such as yours.
0 kommentar(er)
