| |||||||||||||
Unexpected features in Acrobat 7Unexpected features in Acrobat 7Posted Mar 30, 2005 20:11 UTC (Wed) by alan (subscriber, #4018)In reply to: Unexpected features in Acrobat 7 by jbh Parent article: Unexpected features in Acrobat 7
No need to disable javascript completely, just all outgoing traffic to any domain controlled by remoteapproach.
(Log in to post comments)
Unexpected features in Acrobat 7 Posted Mar 30, 2005 20:21 UTC (Wed) by mattdm (guest, #18) [Link] Well, except, any given document that wants to track you could use its own site to do so.
Unexpected features in Acrobat 7 Posted Mar 31, 2005 22:29 UTC (Thu) by proski (subscriber, #104) [Link] Do you have a complete list of domains controlled by remoteapproach?
Unexpected features in Acrobat 7 Posted Apr 1, 2005 17:44 UTC (Fri) by allesfresser (subscriber, #216) [Link] Does anyone know if there's a way to control packet flow based on the attributes of the process trying to transmit the packet (i.e., "don't allow Acrobat Reader to send any network packets anywhere?")
Unexpected features in Acrobat 7 Posted Apr 1, 2005 17:45 UTC (Fri) by corbet (editor, #1) [Link] SELinux can do that sort of thing quite easily. Well, as easily as SELinux does anything, I guess...
Unexpected features in Acrobat 7 Posted Apr 7, 2005 21:07 UTC (Thu) by ekg (guest, #27035) [Link] iptables -A OUTPUT -m owner --cmd-owner acroread -j DROP
Unexpected features in Acrobat 7 Posted Oct 21, 2005 16:02 UTC (Fri) by toxik (guest, #33244) [Link] That tid not quite work, perhaps it works for other or you need some extension - I'm not an expert.
Anyhow, the idea is to send all output from the command "acroread" to the DROP chain, which would cause you timeouts, I'd rather just send it to REJECT (-j REJECT) or if you're wondering, why not use a logged chain of your own? :)
|
|||||||||||||