Purpose of security-mechanisms of Acrobat PDFs?












0















I'm wondering what's the use of the, I call them "pseudo", security-mechanisms, offered by Acrobat PDF fileformat?



The only real purpose I see is to use a user-password, i.e. to prevent unauthorized people to open a PDF by encrypting it with a password; and the signing of PDFs within a company as a means of trusting that a PDF was validated / committed by a certain user within a companys network.



But apart from that, I highly wonder why Acrobat put mechanisms in place like the ability to set an owner-password or the restriction to copy / print or edit a PDF-file. As far as I know these are simply "flags" and it highly depends on the viewer-software whether it will stick to those flags or not. Because obviously, when you set a flag like edit/print-restriction, if you are allowed the file on the computer you can easily extract the PDF-pages (even if it's only doing a screenshot as a last resort) and build a new PDF from it.



So I don't get the deal of setting those flags in-place if there's always some service / software which will just not interpret those flags and thus make it possible to remove those flags.



Won't this lead to a user to feel secure due to misconceptions?










share|improve this question



























    0















    I'm wondering what's the use of the, I call them "pseudo", security-mechanisms, offered by Acrobat PDF fileformat?



    The only real purpose I see is to use a user-password, i.e. to prevent unauthorized people to open a PDF by encrypting it with a password; and the signing of PDFs within a company as a means of trusting that a PDF was validated / committed by a certain user within a companys network.



    But apart from that, I highly wonder why Acrobat put mechanisms in place like the ability to set an owner-password or the restriction to copy / print or edit a PDF-file. As far as I know these are simply "flags" and it highly depends on the viewer-software whether it will stick to those flags or not. Because obviously, when you set a flag like edit/print-restriction, if you are allowed the file on the computer you can easily extract the PDF-pages (even if it's only doing a screenshot as a last resort) and build a new PDF from it.



    So I don't get the deal of setting those flags in-place if there's always some service / software which will just not interpret those flags and thus make it possible to remove those flags.



    Won't this lead to a user to feel secure due to misconceptions?










    share|improve this question

























      0












      0








      0








      I'm wondering what's the use of the, I call them "pseudo", security-mechanisms, offered by Acrobat PDF fileformat?



      The only real purpose I see is to use a user-password, i.e. to prevent unauthorized people to open a PDF by encrypting it with a password; and the signing of PDFs within a company as a means of trusting that a PDF was validated / committed by a certain user within a companys network.



      But apart from that, I highly wonder why Acrobat put mechanisms in place like the ability to set an owner-password or the restriction to copy / print or edit a PDF-file. As far as I know these are simply "flags" and it highly depends on the viewer-software whether it will stick to those flags or not. Because obviously, when you set a flag like edit/print-restriction, if you are allowed the file on the computer you can easily extract the PDF-pages (even if it's only doing a screenshot as a last resort) and build a new PDF from it.



      So I don't get the deal of setting those flags in-place if there's always some service / software which will just not interpret those flags and thus make it possible to remove those flags.



      Won't this lead to a user to feel secure due to misconceptions?










      share|improve this question














      I'm wondering what's the use of the, I call them "pseudo", security-mechanisms, offered by Acrobat PDF fileformat?



      The only real purpose I see is to use a user-password, i.e. to prevent unauthorized people to open a PDF by encrypting it with a password; and the signing of PDFs within a company as a means of trusting that a PDF was validated / committed by a certain user within a companys network.



      But apart from that, I highly wonder why Acrobat put mechanisms in place like the ability to set an owner-password or the restriction to copy / print or edit a PDF-file. As far as I know these are simply "flags" and it highly depends on the viewer-software whether it will stick to those flags or not. Because obviously, when you set a flag like edit/print-restriction, if you are allowed the file on the computer you can easily extract the PDF-pages (even if it's only doing a screenshot as a last resort) and build a new PDF from it.



      So I don't get the deal of setting those flags in-place if there's always some service / software which will just not interpret those flags and thus make it possible to remove those flags.



      Won't this lead to a user to feel secure due to misconceptions?







      security pdf printing adobe-acrobat






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 9 at 9:25









      timtim

      2471213




      2471213






















          1 Answer
          1






          active

          oldest

          votes


















          1














          I think the security mechanism in PDF files are more related to the document process life in a structured company and for prevent modification of the file. Off course is easy to bypass the protection, some file you can use any print to PDF software and most of the flag are gone, but the generated PDF is not signed.



          So, I imaging, in a company who receive a document signed by a trusted authority could trust the document, for example if a technician receive a procedure describe how to operate safely in a critical environment and the company use the security feature of PDF file who read the document signed can trust it; is wrote and sign by, let me say, "John Doe" who take the responsibility of the operation described in the document.



          This is my think and probably only a part the reason for PDF security mechanism






          share|improve this answer
























          • That was what I thought as well: It's a good standard for people working/collaborating in a big company to see the signature etc. But it's bad for everybody who distributes PDF files via mail or puts them online on a webpage, hoping that no one except the owner will be able to modify or print those files. So it leads to a wrong understanding of security in this case and I hope it's a big danger for people which can barely use a computer - and trust me, there are many like this (in fact I know a lot). So it gives you a wrong impression.

            – tim
            Jan 9 at 15:41











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1392206%2fpurpose-of-security-mechanisms-of-acrobat-pdfs%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          I think the security mechanism in PDF files are more related to the document process life in a structured company and for prevent modification of the file. Off course is easy to bypass the protection, some file you can use any print to PDF software and most of the flag are gone, but the generated PDF is not signed.



          So, I imaging, in a company who receive a document signed by a trusted authority could trust the document, for example if a technician receive a procedure describe how to operate safely in a critical environment and the company use the security feature of PDF file who read the document signed can trust it; is wrote and sign by, let me say, "John Doe" who take the responsibility of the operation described in the document.



          This is my think and probably only a part the reason for PDF security mechanism






          share|improve this answer
























          • That was what I thought as well: It's a good standard for people working/collaborating in a big company to see the signature etc. But it's bad for everybody who distributes PDF files via mail or puts them online on a webpage, hoping that no one except the owner will be able to modify or print those files. So it leads to a wrong understanding of security in this case and I hope it's a big danger for people which can barely use a computer - and trust me, there are many like this (in fact I know a lot). So it gives you a wrong impression.

            – tim
            Jan 9 at 15:41
















          1














          I think the security mechanism in PDF files are more related to the document process life in a structured company and for prevent modification of the file. Off course is easy to bypass the protection, some file you can use any print to PDF software and most of the flag are gone, but the generated PDF is not signed.



          So, I imaging, in a company who receive a document signed by a trusted authority could trust the document, for example if a technician receive a procedure describe how to operate safely in a critical environment and the company use the security feature of PDF file who read the document signed can trust it; is wrote and sign by, let me say, "John Doe" who take the responsibility of the operation described in the document.



          This is my think and probably only a part the reason for PDF security mechanism






          share|improve this answer
























          • That was what I thought as well: It's a good standard for people working/collaborating in a big company to see the signature etc. But it's bad for everybody who distributes PDF files via mail or puts them online on a webpage, hoping that no one except the owner will be able to modify or print those files. So it leads to a wrong understanding of security in this case and I hope it's a big danger for people which can barely use a computer - and trust me, there are many like this (in fact I know a lot). So it gives you a wrong impression.

            – tim
            Jan 9 at 15:41














          1












          1








          1







          I think the security mechanism in PDF files are more related to the document process life in a structured company and for prevent modification of the file. Off course is easy to bypass the protection, some file you can use any print to PDF software and most of the flag are gone, but the generated PDF is not signed.



          So, I imaging, in a company who receive a document signed by a trusted authority could trust the document, for example if a technician receive a procedure describe how to operate safely in a critical environment and the company use the security feature of PDF file who read the document signed can trust it; is wrote and sign by, let me say, "John Doe" who take the responsibility of the operation described in the document.



          This is my think and probably only a part the reason for PDF security mechanism






          share|improve this answer













          I think the security mechanism in PDF files are more related to the document process life in a structured company and for prevent modification of the file. Off course is easy to bypass the protection, some file you can use any print to PDF software and most of the flag are gone, but the generated PDF is not signed.



          So, I imaging, in a company who receive a document signed by a trusted authority could trust the document, for example if a technician receive a procedure describe how to operate safely in a critical environment and the company use the security feature of PDF file who read the document signed can trust it; is wrote and sign by, let me say, "John Doe" who take the responsibility of the operation described in the document.



          This is my think and probably only a part the reason for PDF security mechanism







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 9 at 9:42









          AtomiX84AtomiX84

          4779




          4779













          • That was what I thought as well: It's a good standard for people working/collaborating in a big company to see the signature etc. But it's bad for everybody who distributes PDF files via mail or puts them online on a webpage, hoping that no one except the owner will be able to modify or print those files. So it leads to a wrong understanding of security in this case and I hope it's a big danger for people which can barely use a computer - and trust me, there are many like this (in fact I know a lot). So it gives you a wrong impression.

            – tim
            Jan 9 at 15:41



















          • That was what I thought as well: It's a good standard for people working/collaborating in a big company to see the signature etc. But it's bad for everybody who distributes PDF files via mail or puts them online on a webpage, hoping that no one except the owner will be able to modify or print those files. So it leads to a wrong understanding of security in this case and I hope it's a big danger for people which can barely use a computer - and trust me, there are many like this (in fact I know a lot). So it gives you a wrong impression.

            – tim
            Jan 9 at 15:41

















          That was what I thought as well: It's a good standard for people working/collaborating in a big company to see the signature etc. But it's bad for everybody who distributes PDF files via mail or puts them online on a webpage, hoping that no one except the owner will be able to modify or print those files. So it leads to a wrong understanding of security in this case and I hope it's a big danger for people which can barely use a computer - and trust me, there are many like this (in fact I know a lot). So it gives you a wrong impression.

          – tim
          Jan 9 at 15:41





          That was what I thought as well: It's a good standard for people working/collaborating in a big company to see the signature etc. But it's bad for everybody who distributes PDF files via mail or puts them online on a webpage, hoping that no one except the owner will be able to modify or print those files. So it leads to a wrong understanding of security in this case and I hope it's a big danger for people which can barely use a computer - and trust me, there are many like this (in fact I know a lot). So it gives you a wrong impression.

          – tim
          Jan 9 at 15:41


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1392206%2fpurpose-of-security-mechanisms-of-acrobat-pdfs%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

          Alcedinidae

          RAC Tourist Trophy