diff options
Diffstat (limited to 'results/classifier/105/socket/1064631')
| -rw-r--r-- | results/classifier/105/socket/1064631 | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/results/classifier/105/socket/1064631 b/results/classifier/105/socket/1064631 new file mode 100644 index 000000000..e61331317 --- /dev/null +++ b/results/classifier/105/socket/1064631 @@ -0,0 +1,31 @@ +socket: 0.956 +network: 0.947 +device: 0.795 +graphic: 0.635 +instruction: 0.502 +semantic: 0.458 +other: 0.404 +vnc: 0.389 +mistranslation: 0.315 +boot: 0.301 +KVM: 0.268 +assembly: 0.130 + +Feature request: tls for chardev socket (telnet,tcp,udp) + +Hello, + +it would be nice if chardev socket (telnet,tcp,udp) could have tls support as vnc does. + +This way we could have encrypted access to virtual character devices over network, +for example in setup: conserver -> socat+tls <-> qemu+chardev+tls. + +The best would be both direction - server even client, so even the client should +trust remote server (trustfile, fingeprint...?). + +Thank you. + +This support was introduced in QEMU 2.6 last year. Some info here: + +https://www.berrange.com/posts/2016/08/16/improving-qemu-security-part-6-tls-support-for-character-devices/ + |