Question about payload/share protocol

[Albert Vaca]

Looks like you figured it out already, but anyway: For the SSL sockets used
for payload transfers, you can configure them using the device
certificates, without having to do anything kdeconnect-specific
(like sending an identity packet). It's just a plain SSL connection.

Albert

On Thu, Sep 21, 2017 at 4:23 AM, Andy Holmes <andrew.g.r.holmes at gmail.com>
wrote:

> Nevermind, got it.
>
> On Tue, Sep 19, 2017 at 2:10 PM, Andy Holmes
> <andrew.g.r.holmes at gmail.com> wrote:
> > Hi,
> >
> > I'm trying to understand the payload protocol, used for the share
> > plugin and elsewhere, but having a hard time following the code since
> > I don't write C++.
> >
> > I'm using protocol version 7 so I assume a TLS socket is opened to the
> > device host address at the port specified in "payloadTransferInfo",
> > but I can't establish a successful handshake. If I try sending an
> > identity packet (as in LanLinkProvider::connected), the handshake
> > fails immediately, but if I don't the handshake never completes.
> >
> > On the other hand, if I open a connection without SSL/TLS the
> > connection never has data waiting. Could someone give me a rough
> > breakdown of what happens here?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20170921/4e344d15/attachment.html>