[proposed fix] tinc has a security hole

[Guus Sliepen]

On Tue, 29 Aug 2000, Guus Sliepen wrote:

> HELLO? overhead. Just start directly sending a public key.
> 
>   2                               send PUBLIC_KEY
>   3 send PUBLIC KEY

Uhm actually, we don't need to send those public keys at all, because we
will store each others public key locally. Let's use that for
authentication and the meta protocol. Using the meta protocol, a shared
secret key for the symmetric blowfish algorithm can be exchanged. So:

Client				Server
--------------------------------------------------------------
Connects to server
				Accepts connection, but waits
send tinc name
				Looks up tinc name, if it exist
				get the public key.
				Send own tinc name, encrypted
				with public key.
decrypt, look up public                       .
key of the server.                            .
        .                                     .
        .                                     .
        V                                     V
Rest of the authentication can now be done totally encrypted.

-------------------------------------------
Met vriendelijke groet / with kind regards,
  Guus Sliepen <guus at sliepen.warande.net>
-------------------------------------------
See also: http://tinc.nl.linux.org/
          http://www.kernelbench.org/
-------------------------------------------

---
TINC development list, tinc-devel at nl.linux.org
Archive: http://mail.nl.linux.org/tinc-devel/