From: "Anthony J. Bentley" <anthonyjbentley@gmail.com>
To: tech@mdocml.bsd.lv
Subject: Re: remove private information from user documents
Date: Sun, 27 Feb 2011 17:30:21 -0700 [thread overview]
Message-ID: <4d6aeca1.42922a0a.4b08.ffffba88@mx.google.com> (raw)
In-Reply-To: <20110227191439.GE12815@iris.usta.de>
Hi Ingo,
> Theo noticed that mandoc(1) includes information about itself
> into PostScript and PDF documents it creates.
>
> I don't like that. Basically, what software i'm running, and which
> version, is private information about myself. I don't expect such
> information to end up in documents i'm creating.
Perhaps you should patch your mail client as well, as it tells me
you're using Mutt/1.5.21 ;)
Personally I don't see it as a security problem, but neither do I
see any reason not to take it out. I admit, I do occasionally run
pdfinfo(1) on documents just to see how the author created it.
(Perhaps I need a hobby.)
--
Anthony J. Bentley
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-02-28 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 19:14 Ingo Schwarze
2011-02-27 19:35 ` Joerg Sonnenberger
2011-02-27 22:40 ` Ingo Schwarze
2011-03-06 23:59 ` Kristaps Dzonsons
2011-02-28 0:30 ` Anthony J. Bentley [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4d6aeca1.42922a0a.4b08.ffffba88@mx.google.com \
--to=anthonyjbentley@gmail.com \
--cc=tech@mdocml.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).