core-agent-linux/debian/qubes-core-agent-qrexec.install

etc/pam.d/qrexec
etc/qubes/rpc-config/README
lib/systemd/system/qubes-qrexec-agent.service
usr/bin/qrexec-client-vm
usr/bin/qrexec-fork-server
usr/lib/qubes/qrexec-agent
usr/lib/qubes/qrexec-client-vm
usr/lib/qubes/qrexec_client_vm
usr/lib/qubes/qubes-rpc-multiplexer
usr/share/man/man1/qrexec-client-vm.1.gz
qrexec: use PAM directly instead of calling su to setup the session Instead of calling 'su' to switch the user, use own implementation of this. Thanks to PAM it's pretty simple. The main reason is to have control over process waiting for session termination (to call pam_close_sesion/pam_end). Especially we don't want it to keep std* fds open, which would prevent qrexec-agent from receiving EOF when one of them will be closed. Also, this will preserve QREXEC_AGENT_PID environment variable. Fixes QubesOS/qubes-issues#2851 2014-10-31 01:07:49 +01:00			`etc/pam.d/qrexec`
document /etc/qubes/rpc-config QubesOS/qubes-issues#2974 2017-08-05 21:28:19 +02:00			`etc/qubes/rpc-config/README`
rpm,deb: split qrexec-agent into separate subpackage While it doesn't make sense to install qubes-core-agent without qrexec, it may make sense to do the otherway around - install just qrexec-agent without all the qrexec services and configuration. For example on some pre-installed system. QubesOS/qubes-issues#2771 2017-06-08 15:33:26 +02:00			`lib/systemd/system/qubes-qrexec-agent.service`
			`usr/bin/qrexec-client-vm`
			`usr/bin/qrexec-fork-server`
			`usr/lib/qubes/qrexec-agent`
			`usr/lib/qubes/qrexec-client-vm`
			`usr/lib/qubes/qrexec_client_vm`
			`usr/lib/qubes/qubes-rpc-multiplexer`
Add qrexec-client-vm man page This clarifies and also defines some corner cases like exit code reporting. QubesOS/qubes-issues#2861 2017-06-20 23:34:43 +02:00			`usr/share/man/man1/qrexec-client-vm.1.gz`