char: don't silently skip tn3270 protocol init when TLS is enabled

Even if common tn3270 implementations do not support TLS, it is trivial to
have them proxied over a proxy like stunnel which adds TLS at the sockets
layer. We should thus not silently skip tn3270 protocol initialization
when TLS is enabled.

Reviewed-by: Eric Blake <[email protected]>
Acked-by: Cornelia Huck <[email protected]>
Signed-off-by: Daniel P. Berrange <[email protected]>

diff --git a/chardev/char-socket.c b/chardev/char-socket.c
index a220803c012383c52b7c3f1ed3bad9b7b7ae9d92..1a371b91ac3d5d279806fc0ed000ec3e1f3ff229 100644 (file)
--- a/chardev/char-socket.c
+++ b/chardev/char-socket.c
@@ -663,8 +663,7 @@ static void tcp_chr_tls_handshake(QIOTask *task,
     if (qio_task_propagate_error(task, NULL)) {
         tcp_chr_disconnect(chr);
     } else {
-        /* tn3270 does not support TLS yet */
-        if (s->do_telnetopt && !s->is_tn3270) {
+        if (s->do_telnetopt) {
             tcp_chr_telnet_init(chr);
         } else {
             tcp_chr_connect(chr);