Beuh
commented
10 years ago Hey,
I second this one, and want to add something. I such a feature is added, I think the best would be to have a CLI option to turn it on (default OFF). The security breach could then be much less of a problem, since the user would turn the feature ON on purpose if needed.
Hi all,
I've just started using pdfpc instead of xpdf to give beamer presentations but have run into a problem. In beamer I can insert a \href{run: script.sh}{link text} command and xpdf will run the script, starting up the script and, in my case starting a Processing app that I use to illustrate points in my talk in an interactive fashion. I also use \href{run: movie.avi}{link text} which starts up a movie in movie player.
I much prefer the play in a box approach of pdfpc for the movies but it doesn't seem to know what to do if I call a script. Looking at the code (I'm not much of a hacker, but I understand code), it seems that the movie.vala code uses the poppler library ActionLaunch (?) call to start a movie but fails if Glib doesn't recognise it as a movie file that can be loaded.
Is there anyway to have arbitrary binaries loaded as part of this handler, perhaps only if a command line option is passed if security is a concern. Since the role of pdfpc is to play mostly self generated pdf files for presentations, this would seem to me a reasonable tradeoff of security vs the convenience of being able to call demo programs from within a presentation.
John Walker