2011-05-16 07:46:54 +00:00
|
|
|
/*
|
|
|
|
|
tincctl.h -- header for tincctl.c.
|
|
|
|
|
Copyright (C) 2011 Guus Sliepen <guus@tinc-vpn.org>
|
|
|
|
|
|
|
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
|
|
|
it under the terms of the GNU General Public License as published by
|
|
|
|
|
the Free Software Foundation; either version 2 of the License, or
|
|
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
|
|
This program is distributed in the hope that it will be useful,
|
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
GNU General Public License for more details.
|
|
|
|
|
|
|
|
|
|
You should have received a copy of the GNU General Public License along
|
|
|
|
|
with this program; if not, write to the Free Software Foundation, Inc.,
|
|
|
|
|
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef __TINC_TINCCTL_H__
|
|
|
|
|
#define __TINC_TINCCTL_H__
|
|
|
|
|
|
Add an invitation protocol.
Using the tinc command, an administrator of an existing VPN can generate
invitations for new nodes. The invitation is a small URL that can easily
be copy&pasted into email or live chat. Another person can have tinc
automatically setup the necessary configuration files and exchange keys
with the server, by only using the invitation URL.
The invitation protocol uses temporary ECDSA keys. The invitation URL
consists of the hostname and port of the server, a hash of the server's
temporary ECDSA key and a cookie. When the client wants to accept an
invitation, it also creates a temporary ECDSA key, connects to the server
and says it wants to accept an invitation. Both sides exchange their
temporary keys. The client verifies that the server's key matches the hash
in the invitation URL. After setting up an SPTPS connection using the
temporary keys, the client gives the cookie to the server. If the cookie
is valid, the server sends the client an invitation file containing the
client's new name and a copy of the server's host config file. If everything
is ok, the client will generate a long-term ECDSA key and send it to the
server, which will add it to a new host config file for the client.
The invitation protocol currently allows multiple host config files to be
send from the server to the client. However, the client filters out
most configuration variables for its own host configuration file. In
particular, it only accepts Name, Mode, Broadcast, ConnectTo, Subnet and
AutoConnect. Also, at the moment no tinc-up script is generated.
When an invitation has succesfully been accepted, the client needs to start
the tinc daemon manually.
2013-05-29 16:31:10 +00:00
|
|
|
extern bool tty;
|
|
|
|
|
extern char line[4096];
|
|
|
|
|
extern int fd;
|
|
|
|
|
extern char buffer[4096];
|
|
|
|
|
extern size_t blen;
|
|
|
|
|
extern bool confbasegiven;
|
|
|
|
|
extern char *tinc_conf;
|
|
|
|
|
extern char *hosts_dir;
|
|
|
|
|
|
|
|
|
|
#define VAR_SERVER 1 /* Should be in tinc.conf */
|
|
|
|
|
#define VAR_HOST 2 /* Can be in host config file */
|
|
|
|
|
#define VAR_MULTIPLE 4 /* Multiple statements allowed */
|
|
|
|
|
#define VAR_OBSOLETE 8 /* Should not be used anymore */
|
|
|
|
|
#define VAR_SAFE 16 /* Variable is safe when accepting invitations */
|
|
|
|
|
|
|
|
|
|
typedef struct {
|
|
|
|
|
const char *name;
|
|
|
|
|
int type;
|
|
|
|
|
} var_t;
|
|
|
|
|
|
|
|
|
|
extern const var_t variables[];
|
|
|
|
|
|
|
|
|
|
extern int rstrip(char *value);
|
|
|
|
|
extern char *get_my_name(bool verbose);
|
|
|
|
|
extern bool connect_tincd(bool verbose);
|
2011-05-16 07:46:54 +00:00
|
|
|
extern bool sendline(int fd, char *format, ...);
|
|
|
|
|
extern bool recvline(int fd, char *line, size_t len);
|
|
|
|
|
|
|
|
|
|
#endif
|
|
|
|
|
|