We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Clear pdf metadata producer and create

How do i clear the producer and creator metadata values? Here is my code, the console shows no output for these once removed, however when i use a metadata finder online they still appear.

           // Open document
            Aspose.Pdf.Document pdfDocument = new Aspose.Pdf.Document(pdfFile);
            // Get document information
            DocumentInfo docInfo = pdfDocument.Info;

            //docInfo.Remove("Producer");
            docInfo.Remove("Creater");

            docInfo.Clear();

            docInfo.Producer.Replace("Aspose.PDF for .NET 19.5", "");

            docInfo.CreationDate = DateTime.Now;
            docInfo.ModDate = DateTime.Now;

            Console.WriteLine("Author: {0}", docInfo.Author);
            Console.WriteLine("Creation Date: {0}", docInfo.CreationDate);
            Console.WriteLine("Keywords: {0}", docInfo.Keywords);
            Console.WriteLine("Modify Date: {0}", docInfo.ModDate);
            Console.WriteLine("Subject: {0}", docInfo.Subject);
            Console.WriteLine("Title: {0}", docInfo.Title);
            Console.WriteLine("Producer: {0}", docInfo.Producer);
            Console.WriteLine("Producer: {0}", docInfo.Creator);

@smooney1234

We would like to share with you that you cannot change/remove/update the producer or creator value in PDF file information as Aspose.PDF for XXX would be shown against them. However, in case you need any other information, please feel free to let us know.

This is a real problem for us as it was highlighted as a security concern during penetration testing that we must address.

yeah same for us. it is a security concern, is there any chance this could be introduced or any rational as to why it cannot?

@smooney1234, @damong

As per our company policy, we are afraid that we cannot offer such functionality to change the creator or producer name against PDF properties. The limitation is already mentioned in the API documentation.

It is a piety that the company policy is to compromise the security of people using your libraries.
We will seek other means of producing PDF’s without leaking this information.

@damong

We apologize if it caused any inconvenience. We will surely share more information in case we have some regarding this scenario in future.

This is really bad, we don’t want to expose what libs we are using in our backend.

@Kranton

At the moment, we cannot implement this feature as per company policy. However, if we plan to offer this in future, we will inform you.

I have the same issue…

I don’t understand this “company policy”, can you explain ? This is a show stopper for us…

@Whiletrue

We are looking into this matter and trying to work out some strategies in this regard. We will get back to you on this matter soon. Please spare us some time.