summaryrefslogtreecommitdiffstats
path: root/Makefile.am
diff options
context:
space:
mode:
authorJiri Denemark <jdenemar@redhat.com>2011-03-11 13:44:20 +0100
committerJiri Denemark <jdenemar@redhat.com>2011-03-14 12:37:19 +0100
commit0aa2b90fc0a9975221ae8f8e94df61bb788877bc (patch)
tree2c539db485706da855166fb2f5584754657c24c2 /Makefile.am
parentf9b0014ec10e3c031e0cdbd90ae9c2ba5698804e (diff)
downloadlibvirt-python-split-0aa2b90fc0a9975221ae8f8e94df61bb788877bc.zip
libvirt-python-split-0aa2b90fc0a9975221ae8f8e94df61bb788877bc.tar.gz
libvirt-python-split-0aa2b90fc0a9975221ae8f8e94df61bb788877bc.tar.xz
python: Use hardcoded python path in libvirt.pyv0.9.1v0.9.0CVE-2011-1486
This partially reverts (and fixes that part in a different way) commit e4384459c93e3e786aa483c7f077d1d22148f689, which replaced ``/usr/bin/python'' with ``/usr/bin/env python'' in all examples or scripts used during build to generate other files. However, python bindings module is compiled and linked against a specific python discovered or explicitly provided in configure phase. Thus libvirt.py, which is generated and installed into the system, should use the same python binary for which the module has been built. The hunk in Makefile.am replaces $(srcdir) with $(PYTHON), which might seem wrong but it is not. generator.py didn't use any of its command line arguments so passing $(srcdir) to it was redundant.
Diffstat (limited to 'Makefile.am')
-rw-r--r--Makefile.am2
1 files changed, 1 insertions, 1 deletions
diff --git a/Makefile.am b/Makefile.am
index eda2866..432ad70 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -53,7 +53,7 @@ GENERATED= libvirt-export.c \
libvirt.py
generated.stamp: $(srcdir)/$(GENERATE) $(API_DESC)
- $(PYTHON) $(srcdir)/$(GENERATE) $(srcdir)
+ $(PYTHON) $(srcdir)/$(GENERATE) $(PYTHON)
touch $@
$(GENERATED): generated.stamp