9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] tlssrv
Date: Mon, 17 Jun 2002 12:08:31 +0100	[thread overview]
Message-ID: <857fc7b9048629e29563854dcea6e3e7@9fs.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 135 bytes --]

To my mind, tlssrv equals stunnel server mode.

Thus, a tlsclient program equivalent to stunnel -c would
seem to be the next step.

[-- Attachment #2: Type: message/rfc822, Size: 2546 bytes --]

From: Christopher Nielsen <cnielsen@pobox.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] tlssrv
Date: Mon, 17 Jun 2002 09:14:27 GMT
Message-ID: <16c222b6.0206141730.352cb2c2@posting.google.com>

On a related note, tlssrv seems to be aimed at wrapping
the server side in tls.

In my quest to secure all of my traffic via encrypted
connections, I'd like to wrap my vnc connections from my
Plan 9 terminal to my FreeBSD server in tls/ssl. There
doesn't appear to be anything currently available to do
so, unless I'm missing something about tlssrv.

It'd be easy enough to teach vncv to speak tls/ssl, but
it might be better to solve the problem with a sort of
tls/ssl wrapper like stunnel (http://www.stunnel.org/).

Options I see:

o teach vncv to use tls/ssl
o teach tlssrv to behave like stunnel
o write a new tool to do what tlssrv does but on the
  client side

I'm thinking that teaching tlssrv to operate this way
would be the way to go, but I'd like some feedback on
what others think about this before I write the code.

Thoughts?

--
Christopher Nielsen - Metal-wielding pyro techie
"Those who are willing to trade freedom for security deserve
 neither freedom nor security." --Benjamin Franklin

             reply	other threads:[~2002-06-17 11:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17 11:08 nigel [this message]
2002-06-17 18:59 ` Christopher Nielsen
  -- strict thread matches above, loose matches on Subject: below --
2002-06-17 19:47 Russ Cox
2002-06-17 13:47 Russ Cox
2002-06-17 19:02 ` Christopher Nielsen
2002-06-14 13:45 nigel
2002-06-17  9:14 ` Christopher Nielsen
2002-06-14 13:34 nigel

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=857fc7b9048629e29563854dcea6e3e7@9fs.org \
    --to=nigel@9fs.org \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).