Subject: Re: [9front] vncv patch
Date: Mon, 15 Aug 2022 17:15:19 -0400 [thread overview]
Message-ID: <18D3F3D315DF53FA7BA125A18CBCB354@eigenstate.org> (raw)
Quoth Emil Tomczyk <email@example.com>:
> I wrote a small patch for vncv. This patch allows to specify port on the
> remote vnc server.
this already works out of the box with dial strings,
using the same syntax as any other program doing a
> Although TLS connection wasn't working for me.
if it's broken, let's fix it before changing that.
my vnc servers aren't set up with tls, though, so
I don't have a setup to test. (Because VNC auth
is a joke, my VNC doesn't listen on the public
internet, but instead I tunnel in using sshnet)
prev parent reply other threads:[~2022-08-15 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3496E2C20C950B6CFA9424F09804A810@9front.inri.net>
2022-08-15 20:24 ` Emil Tomczyk
2022-08-15 21:15 ` ori [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).