Re: [dev] sj: explicit tlsc doesn't work

From: Jan Klemkow <j.klemkow_AT_wemelug.de>
Date: Fri, 4 Dec 2015 06:47:26 +0100

On Thu, Dec 03, 2015 at 03:23:16PM -0500, Matthew of Boswell wrote:
> On Tue, 1 Dec 2015 10:37:44 -0500
> Greg Reagle <greg.reagle_AT_umbc.edu> wrote:
>
> > but that doesn't work for me. I have to omit tlsc. It seems to be
> > called automatically. Am I doing something wrong or does the man page
> > need to be corrected?
>
> I think it's a combination. I got it working around the same time you
> did but forgot to post that it worked. I think Jan wants to find a
> cleaner solution, but for now sj calls tlsc.

This solution it the final one, I think. sj is calling tlsc with its
own arguments. So that tlsc starts sj in the same way as before. This
looks like the right way to keep all tools clean and simple.

The aim is, that every tool just handles its own protocol and not parts
of other protocols and programs. One program for one protocol.

> Having sj call tlsc doesn't really bother me... I guess because I can't
> think of a better way to start in xmpp, negotiate tls, then continue in
> encrypted xmpp.
>
> --
> Matt Boswell
Received on Fri Dec 04 2015 - 06:47:26 CET