1. 01 3月, 2017 1 次提交
  2. 23 2月, 2017 2 次提交
  3. 22 2月, 2017 1 次提交
  4. 20 2月, 2017 1 次提交
  5. 16 2月, 2017 1 次提交
  6. 14 2月, 2017 2 次提交
  7. 08 2月, 2017 1 次提交
    • D
      ui: fix reporting of VNC auth in query-vnc-servers · 2a7e6857
      Daniel P. Berrange 提交于
      Currently the VNC authentication info is emitted at the
      top level of the query-vnc-servers data. This is wrong
      because the authentication scheme differs between plain
      and websockets when TLS is enabled. We should instead
      report auth against the individual servers. e.g.
      
      (QEMU) query-vnc-servers
      {
          "return": [
              {
                  "clients": [],
                  "id": "default",
                  "auth": "vencrypt",
                  "vencrypt": "x509-vnc",
                  "server": [
                      {
                          "host": "127.0.0.1"
                          "service": "5901",
                          "websocket": false,
                          "family": "ipv4",
                          "auth": "vencrypt",
                          "vencrypt": "x509-vnc"
                      },
                      {
                          "host": "127.0.0.1",
                          "service": "5902",
                          "websocket": true,
                          "family": "ipv4",
                          "auth": "vnc"
                      }
                  ]
              }
          ]
      }
      
      This also future proofs the QMP schema so that we can
      cope with multiple VNC server instances, listening on
      different interfaces or ports, with different auth
      setup.
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
      Message-id: 20170203120649.15637-3-berrange@redhat.com
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      2a7e6857
  8. 31 1月, 2017 1 次提交
  9. 27 1月, 2017 1 次提交
  10. 23 1月, 2017 1 次提交
  11. 16 1月, 2017 28 次提交