Apr 14

When you need to distribute documents in PDF format, you’ll probably want to protect them. If you are working on Mac OS X (or Windows) and you have Adobe Acrobat, that can be done quite easily.

But if you’re running Linux on your desktop —or even if you’re using Windows or a Mac and don’t want to use proprietary programs—, there are free tools that will let you protect your files by adding encryption, passwords and restrictions.

One of those tools is pdftk (the pdf toolkit). On Debian and Ubuntu, pdftk is already present in the official repositories, so all you have to do to install it is:

apt-get install pdftk

In the product’s website you’ll also find binary packages for FreeBSD, Mac OS X and Windows.

Here are some examples that show you how to use the program:

  • Encrypt a PDF using 128-Bit Strength (the default) and withhold all permissions:

    pdftk mydoc.pdf output mydoc.128.pdf owner_pw foopass

  • Same as above, except that a password is required to open the PDF:

    pdftk mydoc.pdf output mydoc.128.pdf owner_pw foo user_pw baz

  • Same as above, except that printing is allowed (after the PDF has been opened):

    pdftk mydoc.pdf output mydoc.128.pdf owner_pw foo user_pw baz allow printing

Besides the security functions, pdftk has many more features that you might find useful too, including the ability to merge, split and rotate PDF documents, or applying watermarks.

GNU / LinuxFreeBSDMac OS XWindows


Defined tags for this entry: , , ,

Posted by Marcus Friedman

442 hits
Last modified on 2009-04-15 22:27
Bookmark How to protect your PDF files with open source tools  at del.icio.us Digg How to protect your PDF files with open source tools Bloglines How to protect your PDF files with open source tools Technorati How to protect your PDF files with open source tools Bookmark How to protect your PDF files with open source tools  at reddit.com Stumble It!

0 Trackbacks

  1. No Trackbacks

0 Comments

Display comments as(Linear | Threaded)
  1. No comments

Add Comment

If this is the first time that you're posting a comment to this blog, please take a look at the guidelines for posting comments.


Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.
Textile-formatting allowed
BBCode format allowed
E-Mail addresses will not be displayed and will only be used for E-Mail notifications

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA


Submitted comments will be subject to moderation before being displayed.