1. 22 11月, 2019 1 次提交
  2. 20 11月, 2019 1 次提交
  3. 19 11月, 2019 1 次提交
  4. 14 11月, 2019 1 次提交
  5. 13 11月, 2019 1 次提交
  6. 12 11月, 2019 1 次提交
  7. 09 11月, 2019 2 次提交
  8. 25 10月, 2019 2 次提交
  9. 21 10月, 2019 2 次提交
  10. 16 10月, 2019 1 次提交
  11. 15 10月, 2019 5 次提交
  12. 14 10月, 2019 3 次提交
  13. 01 10月, 2019 1 次提交
    • D
      rpc: fix escaping of shell path for netcat binary · 76d31244
      Daniel P. Berrangé 提交于
      Consider having a nc binary in the path with a space in its name,
      for example '/tmp/fo o/nc'
      
      This results in libvirt running SSH with the following arg value
      
        "'if ''/tmp/fo o/nc'' -q 2>&1 | grep \"requires
          an argument\" >/dev/null 2>&1; then ARG=-q0;
          else ARG=;fi;''/tmp/fo o/nc'' $ARG -U
          /var/run/libvirt/libvirt-sock'"
      
      The use of the single quote escaping was introduced by
      
        commit 6ac6238d
        Author: Guido Günther <agx@sigxcpu.org>
        Date:   Thu Oct 13 21:49:01 2011 +0200
      
          Use virBufferEscapeShell in virNetSocketNewConnectSSH
      
          to escape the netcat command since it's passed to the shell. Adjust
          expected test case output accordingly.
      
      While the intention of this change was good, the result is broken as it
      is still underquoted.
      
      On the SSH server side, SSH itself runs the command via the shell.
      Our command is then invoking the shell again. Thus we see
      
      $ virsh -c qemu+ssh://root@domokun/system?netcat=%2Ftmp%2Ffo%20o%2Fnc list
      error: failed to connect to the hypervisor
      error: End of file while reading data: sh: /tmp/fo: No such file or directory: Input/output error
      
      With the second level of escaping added we can now successfully use a nc
      binary with a space in the path.
      
      The original test case added was misleading as it illustrated using a
      binary path of 'nc -4' which is not a path, it is a command with a
      separate argument, which is getting interpreted as a path.
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      76d31244
  14. 16 9月, 2019 2 次提交
  15. 28 8月, 2019 1 次提交
  16. 14 8月, 2019 1 次提交
  17. 09 8月, 2019 1 次提交
  18. 07 8月, 2019 2 次提交
  19. 27 7月, 2019 1 次提交
  20. 19 7月, 2019 1 次提交
    • D
      remote: increase daemon shutdown timer to 2 minutes · 9d7fcdbf
      Daniel P. Berrangé 提交于
      Shutting down the daemon after 30 seconds of being idle is a little bit
      too aggressive. Especially when using 'virsh' in single-shot mode, as
      opposed to interactive shell mode, it would not be unusual to have
      more than 30 seconds between commands. This will lead to the daemon
      shutting down and starting up between a series of commands.
      
      Increasing the shutdown timer to 2 minutes will make it less likely that
      the daemon will shutdown while the user is in the middle of a series of
      commands.
      Reviewed-by: NJim Fehlig <jfehlig@suse.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      9d7fcdbf
  21. 12 7月, 2019 9 次提交