add localsend-protocol-v3

[ghost]

Hello everyone.

I made a pull request about this issue: login authentication ways for localsend

Possibly in version 3, it would be possible to have login extensions on the localsend protocol.

img:

I would like to contribute to this pull-request and I hope you all accept it.

[Tienisto]

Thanks for your contribution.

Generally, this can be added as v2.1 because it has no breaking changes for devices that understand v2.

Regarding public/private key:
There is an interesting issue localsend/localsend#357 that mentions two-side-ssl. In this case, devices can remember the SSL certificate and that's it. So we don't actually need to complicate the protocol and just use built-in two-way-SSL.

[ghost]

Hi Tienisto.

Generally, this can be added as v2.1 because it has no breaking changes for devices that understand v2.

• Maybe this protocol version would be "3" - because there are several concepts or ideas that are outside the scope of the first or second version of the protocol.
• I think it's better to name it version 2.1. Because initially, the version 2 is used to compose some stuff.

Regarding public/private key:
There is an interesting issue localsend/localsend#357 that mentions two-side-ssl. In this case, devices can remember the SSL certificate and that's it.

So, If there is no public and private key, would it be possible with two-way-SSL to solve this problem above?

So we don't actually need to complicate the protocol and just use built-in two-way-SSL.

So, Is it possible to authenticate only with two-way-SSL one or more devices, and one or more files?

note: Another interesting use case for the public and private key would be interesting is when you need to send some shared link. Please, see this - too: share links Feature request

If you have time to answer my questions, I would be happy for your brief contact.