On Tuesday 05 Apr 2005 19:37, jdow wrote: > > So you simply block all ports for AcroRead. That's as easy as only > blocking port 80. > > > The cute problem is when you want to read a pdf file in your browser. > It is probably better to save the pdf file and only allow AcroRead to > access local files.
I do tend to view the pdf in a browser first, then save it if it looks useful. > So watch, the Acrobat people will include a little > app that AcroRead talks to and that little app accesses the net. It has > a different name so it can still communicate. You get into an arms race > quite literally. > > It may be that the way to handle this is in the court of public opinion. > Spray this information around to all your friends. If they stop using > AcroRead and use other tools instead maybe Adobe will get the message. > (For that matter - why use AcroRead on Linux, anyway?) > In theory, I don't mind a bit if an author wants to know about his work being read. The problem, of course, is in how it can be abused. As to why us AcroRead - things may have improved lately, but I first installed AcroRead because it handled scaleable printing better - printing 2-up, or A4 onto A5 paper. Certainly at that time I couldn't do it in any other package. Anne -- Registered Linux User No.293302 (http://counter.li.org/) Have you visited http://twiki.mdklinuxfaq.org yet? Mandrake at all levels
pgpWP90zcUWC4.pgp
Description: PGP signature
