2002-03-23 20:47:21 +03:00
|
|
|
/*
|
|
|
|
* Network proxy abstraction in PuTTY
|
|
|
|
*
|
|
|
|
* A proxy layer, if necessary, wedges itself between the network
|
|
|
|
* code and the higher level backend.
|
|
|
|
*/
|
|
|
|
|
2002-09-21 20:52:21 +04:00
|
|
|
#include <assert.h>
|
2002-10-23 18:24:40 +04:00
|
|
|
#include <ctype.h>
|
|
|
|
#include <string.h>
|
2002-09-21 20:52:21 +04:00
|
|
|
|
2002-03-23 20:47:21 +03:00
|
|
|
#define DEFINE_PLUG_METHOD_MACROS
|
|
|
|
#include "putty.h"
|
|
|
|
#include "network.h"
|
|
|
|
#include "proxy.h"
|
|
|
|
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
#define do_proxy_dns(conf) \
|
|
|
|
(conf_get_int(conf, CONF_proxy_dns) == FORCE_ON || \
|
|
|
|
(conf_get_int(conf, CONF_proxy_dns) == AUTO && \
|
|
|
|
conf_get_int(conf, CONF_proxy_type) != PROXY_SOCKS4))
|
2002-12-18 19:23:11 +03:00
|
|
|
|
2002-03-23 20:47:21 +03:00
|
|
|
/*
|
|
|
|
* Call this when proxy negotiation is complete, so that this
|
|
|
|
* socket can begin working normally.
|
|
|
|
*/
|
2018-05-27 11:29:33 +03:00
|
|
|
void proxy_activate (ProxySocket *p)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
|
|
|
void *data;
|
|
|
|
int len;
|
2002-10-22 13:40:38 +04:00
|
|
|
long output_before, output_after;
|
|
|
|
|
2002-03-23 20:47:21 +03:00
|
|
|
p->state = PROXY_STATE_ACTIVE;
|
|
|
|
|
2002-10-22 13:40:38 +04:00
|
|
|
/* we want to ignore new receive events until we have sent
|
|
|
|
* all of our buffered receive data.
|
|
|
|
*/
|
2002-03-23 20:47:21 +03:00
|
|
|
sk_set_frozen(p->sub_socket, 1);
|
|
|
|
|
2002-10-22 13:40:38 +04:00
|
|
|
/* how many bytes of output have we buffered? */
|
|
|
|
output_before = bufchain_size(&p->pending_oob_output_data) +
|
|
|
|
bufchain_size(&p->pending_output_data);
|
|
|
|
/* and keep track of how many bytes do not get sent. */
|
|
|
|
output_after = 0;
|
|
|
|
|
2002-03-28 00:09:16 +03:00
|
|
|
/* send buffered OOB writes */
|
2002-03-23 20:47:21 +03:00
|
|
|
while (bufchain_size(&p->pending_oob_output_data) > 0) {
|
|
|
|
bufchain_prefix(&p->pending_oob_output_data, &data, &len);
|
2002-10-22 13:40:38 +04:00
|
|
|
output_after += sk_write_oob(p->sub_socket, data, len);
|
2002-03-23 20:47:21 +03:00
|
|
|
bufchain_consume(&p->pending_oob_output_data, len);
|
|
|
|
}
|
|
|
|
|
2002-03-28 00:09:16 +03:00
|
|
|
/* send buffered normal writes */
|
2002-03-23 20:47:21 +03:00
|
|
|
while (bufchain_size(&p->pending_output_data) > 0) {
|
|
|
|
bufchain_prefix(&p->pending_output_data, &data, &len);
|
2002-10-22 13:40:38 +04:00
|
|
|
output_after += sk_write(p->sub_socket, data, len);
|
2002-03-23 20:47:21 +03:00
|
|
|
bufchain_consume(&p->pending_output_data, len);
|
|
|
|
}
|
2002-10-22 13:40:38 +04:00
|
|
|
|
|
|
|
/* if we managed to send any data, let the higher levels know. */
|
|
|
|
if (output_after < output_before)
|
|
|
|
plug_sent(p->plug, output_after);
|
2002-03-23 20:47:21 +03:00
|
|
|
|
2002-03-28 00:09:16 +03:00
|
|
|
/* if we were asked to flush the output during
|
|
|
|
* the proxy negotiation process, do so now.
|
|
|
|
*/
|
2002-03-23 20:47:21 +03:00
|
|
|
if (p->pending_flush) sk_flush(p->sub_socket);
|
|
|
|
|
2011-09-13 15:44:03 +04:00
|
|
|
/* if we have a pending EOF to send, send it */
|
|
|
|
if (p->pending_eof) sk_write_eof(p->sub_socket);
|
|
|
|
|
2002-10-22 13:40:38 +04:00
|
|
|
/* if the backend wanted the socket unfrozen, try to unfreeze.
|
|
|
|
* our set_frozen handler will flush buffered receive data before
|
|
|
|
* unfreezing the actual underlying socket.
|
|
|
|
*/
|
|
|
|
if (!p->freeze)
|
2018-05-27 11:29:33 +03:00
|
|
|
sk_set_frozen(&p->sockvt, 0);
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* basic proxy socket functions */
|
|
|
|
|
|
|
|
static Plug sk_proxy_plug (Socket s, Plug p)
|
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(s, ProxySocket, sockvt);
|
2002-03-23 20:47:21 +03:00
|
|
|
Plug ret = ps->plug;
|
|
|
|
if (p)
|
|
|
|
ps->plug = p;
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void sk_proxy_close (Socket s)
|
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(s, ProxySocket, sockvt);
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
sk_close(ps->sub_socket);
|
2003-08-07 20:04:33 +04:00
|
|
|
sk_addr_free(ps->remote_addr);
|
2002-03-23 20:47:21 +03:00
|
|
|
sfree(ps);
|
|
|
|
}
|
|
|
|
|
2018-05-26 10:31:34 +03:00
|
|
|
static int sk_proxy_write (Socket s, const void *data, int len)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(s, ProxySocket, sockvt);
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
if (ps->state != PROXY_STATE_ACTIVE) {
|
|
|
|
bufchain_add(&ps->pending_output_data, data, len);
|
|
|
|
return bufchain_size(&ps->pending_output_data);
|
|
|
|
}
|
|
|
|
return sk_write(ps->sub_socket, data, len);
|
|
|
|
}
|
|
|
|
|
2018-05-26 10:31:34 +03:00
|
|
|
static int sk_proxy_write_oob (Socket s, const void *data, int len)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(s, ProxySocket, sockvt);
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
if (ps->state != PROXY_STATE_ACTIVE) {
|
|
|
|
bufchain_clear(&ps->pending_output_data);
|
|
|
|
bufchain_clear(&ps->pending_oob_output_data);
|
|
|
|
bufchain_add(&ps->pending_oob_output_data, data, len);
|
|
|
|
return len;
|
|
|
|
}
|
|
|
|
return sk_write_oob(ps->sub_socket, data, len);
|
|
|
|
}
|
|
|
|
|
2011-09-13 15:44:03 +04:00
|
|
|
static void sk_proxy_write_eof (Socket s)
|
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(s, ProxySocket, sockvt);
|
2011-09-13 15:44:03 +04:00
|
|
|
|
|
|
|
if (ps->state != PROXY_STATE_ACTIVE) {
|
|
|
|
ps->pending_eof = 1;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
sk_write_eof(ps->sub_socket);
|
|
|
|
}
|
|
|
|
|
2002-03-23 20:47:21 +03:00
|
|
|
static void sk_proxy_flush (Socket s)
|
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(s, ProxySocket, sockvt);
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
if (ps->state != PROXY_STATE_ACTIVE) {
|
|
|
|
ps->pending_flush = 1;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
sk_flush(ps->sub_socket);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void sk_proxy_set_frozen (Socket s, int is_frozen)
|
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(s, ProxySocket, sockvt);
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
if (ps->state != PROXY_STATE_ACTIVE) {
|
|
|
|
ps->freeze = is_frozen;
|
|
|
|
return;
|
|
|
|
}
|
2002-10-22 13:40:38 +04:00
|
|
|
|
|
|
|
/* handle any remaining buffered recv data first */
|
|
|
|
if (bufchain_size(&ps->pending_input_data) > 0) {
|
|
|
|
ps->freeze = is_frozen;
|
|
|
|
|
|
|
|
/* loop while we still have buffered data, and while we are
|
|
|
|
* unfrozen. the plug_receive call in the loop could result
|
|
|
|
* in a call back into this function refreezing the socket,
|
|
|
|
* so we have to check each time.
|
|
|
|
*/
|
|
|
|
while (!ps->freeze && bufchain_size(&ps->pending_input_data) > 0) {
|
2002-10-30 20:57:31 +03:00
|
|
|
void *data;
|
2004-01-20 22:30:41 +03:00
|
|
|
char databuf[512];
|
2002-10-22 13:40:38 +04:00
|
|
|
int len;
|
|
|
|
bufchain_prefix(&ps->pending_input_data, &data, &len);
|
2004-01-20 22:30:41 +03:00
|
|
|
if (len > lenof(databuf))
|
|
|
|
len = lenof(databuf);
|
|
|
|
memcpy(databuf, data, len);
|
2002-10-22 13:40:38 +04:00
|
|
|
bufchain_consume(&ps->pending_input_data, len);
|
2004-01-20 22:30:41 +03:00
|
|
|
plug_receive(ps->plug, 0, databuf, len);
|
2002-10-22 13:40:38 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
/* if we're still frozen, we'll have to wait for another
|
|
|
|
* call from the backend to finish unbuffering the data.
|
|
|
|
*/
|
|
|
|
if (ps->freeze) return;
|
|
|
|
}
|
|
|
|
|
2002-03-23 20:47:21 +03:00
|
|
|
sk_set_frozen(ps->sub_socket, is_frozen);
|
|
|
|
}
|
|
|
|
|
2003-05-04 18:18:18 +04:00
|
|
|
static const char * sk_proxy_socket_error (Socket s)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(s, ProxySocket, sockvt);
|
2002-03-23 20:47:21 +03:00
|
|
|
if (ps->error != NULL || ps->sub_socket == NULL) {
|
|
|
|
return ps->error;
|
|
|
|
}
|
|
|
|
return sk_socket_error(ps->sub_socket);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* basic proxy plug functions */
|
|
|
|
|
2005-01-16 17:29:34 +03:00
|
|
|
static void plug_proxy_log(Plug plug, int type, SockAddr addr, int port,
|
|
|
|
const char *error_msg, int error_code)
|
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(plug, ProxySocket, plugvt);
|
2005-01-16 17:29:34 +03:00
|
|
|
|
|
|
|
plug_log(ps->plug, type, addr, port, error_msg, error_code);
|
|
|
|
}
|
|
|
|
|
2016-06-03 01:03:24 +03:00
|
|
|
static void plug_proxy_closing (Plug p, const char *error_msg,
|
|
|
|
int error_code, int calling_back)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(p, ProxySocket, plugvt);
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
if (ps->state != PROXY_STATE_ACTIVE) {
|
|
|
|
ps->closing_error_msg = error_msg;
|
|
|
|
ps->closing_error_code = error_code;
|
|
|
|
ps->closing_calling_back = calling_back;
|
2016-06-03 01:03:24 +03:00
|
|
|
ps->negotiate(ps, PROXY_CHANGE_CLOSING);
|
|
|
|
} else {
|
|
|
|
plug_closing(ps->plug, error_msg, error_code, calling_back);
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2016-06-03 01:03:24 +03:00
|
|
|
static void plug_proxy_receive (Plug p, int urgent, char *data, int len)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(p, ProxySocket, plugvt);
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
if (ps->state != PROXY_STATE_ACTIVE) {
|
|
|
|
/* we will lose the urgentness of this data, but since most,
|
|
|
|
* if not all, of this data will be consumed by the negotiation
|
|
|
|
* process, hopefully it won't affect the protocol above us
|
|
|
|
*/
|
|
|
|
bufchain_add(&ps->pending_input_data, data, len);
|
|
|
|
ps->receive_urgent = urgent;
|
|
|
|
ps->receive_data = data;
|
|
|
|
ps->receive_len = len;
|
2016-06-03 01:03:24 +03:00
|
|
|
ps->negotiate(ps, PROXY_CHANGE_RECEIVE);
|
|
|
|
} else {
|
|
|
|
plug_receive(ps->plug, urgent, data, len);
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void plug_proxy_sent (Plug p, int bufsize)
|
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(p, ProxySocket, plugvt);
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
if (ps->state != PROXY_STATE_ACTIVE) {
|
|
|
|
ps->sent_bufsize = bufsize;
|
|
|
|
ps->negotiate(ps, PROXY_CHANGE_SENT);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
plug_sent(ps->plug, bufsize);
|
|
|
|
}
|
|
|
|
|
2013-11-17 18:03:55 +04:00
|
|
|
static int plug_proxy_accepting(Plug p,
|
|
|
|
accept_fn_t constructor, accept_ctx_t ctx)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ps = FROMFIELD(p, ProxySocket, plugvt);
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
if (ps->state != PROXY_STATE_ACTIVE) {
|
2013-11-17 18:03:55 +04:00
|
|
|
ps->accepting_constructor = constructor;
|
|
|
|
ps->accepting_ctx = ctx;
|
2002-03-23 20:47:21 +03:00
|
|
|
return ps->negotiate(ps, PROXY_CHANGE_ACCEPTING);
|
|
|
|
}
|
2013-11-17 18:03:55 +04:00
|
|
|
return plug_accepting(ps->plug, constructor, ctx);
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
|
2002-12-18 19:23:11 +03:00
|
|
|
/*
|
|
|
|
* This function can accept a NULL pointer as `addr', in which case
|
|
|
|
* it will only check the host name.
|
|
|
|
*/
|
2013-11-17 18:05:41 +04:00
|
|
|
int proxy_for_destination (SockAddr addr, const char *hostname,
|
|
|
|
int port, Conf *conf)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
|
|
|
int s = 0, e = 0;
|
|
|
|
char hostip[64];
|
|
|
|
int hostip_len, hostname_len;
|
2003-01-12 18:26:10 +03:00
|
|
|
const char *exclude_list;
|
2002-03-23 20:47:21 +03:00
|
|
|
|
2012-10-17 00:15:51 +04:00
|
|
|
/*
|
|
|
|
* Special local connections such as Unix-domain sockets
|
|
|
|
* unconditionally cannot be proxied, even in proxy-localhost
|
|
|
|
* mode. There just isn't any way to ask any known proxy type for
|
|
|
|
* them.
|
|
|
|
*/
|
|
|
|
if (addr && sk_address_is_special_local(addr))
|
|
|
|
return 0; /* do not proxy */
|
|
|
|
|
2002-12-18 15:18:54 +03:00
|
|
|
/*
|
|
|
|
* Check the host name and IP against the hard-coded
|
|
|
|
* representations of `localhost'.
|
|
|
|
*/
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
if (!conf_get_int(conf, CONF_even_proxy_localhost) &&
|
2002-12-18 19:23:11 +03:00
|
|
|
(sk_hostname_is_local(hostname) ||
|
|
|
|
(addr && sk_address_is_local(addr))))
|
2002-12-18 15:18:54 +03:00
|
|
|
return 0; /* do not proxy */
|
|
|
|
|
2002-03-23 20:47:21 +03:00
|
|
|
/* we want a string representation of the IP address for comparisons */
|
2002-12-18 19:23:11 +03:00
|
|
|
if (addr) {
|
|
|
|
sk_getaddr(addr, hostip, 64);
|
|
|
|
hostip_len = strlen(hostip);
|
2003-04-23 17:48:09 +04:00
|
|
|
} else
|
|
|
|
hostip_len = 0; /* placate gcc; shouldn't be required */
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
hostname_len = strlen(hostname);
|
|
|
|
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
exclude_list = conf_get_str(conf, CONF_proxy_exclude_list);
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
/* now parse the exclude list, and see if either our IP
|
|
|
|
* or hostname matches anything in it.
|
|
|
|
*/
|
|
|
|
|
|
|
|
while (exclude_list[s]) {
|
|
|
|
while (exclude_list[s] &&
|
2003-03-11 12:30:31 +03:00
|
|
|
(isspace((unsigned char)exclude_list[s]) ||
|
2002-03-23 20:47:21 +03:00
|
|
|
exclude_list[s] == ',')) s++;
|
|
|
|
|
|
|
|
if (!exclude_list[s]) break;
|
|
|
|
|
|
|
|
e = s;
|
|
|
|
|
|
|
|
while (exclude_list[e] &&
|
2003-03-11 12:30:31 +03:00
|
|
|
(isalnum((unsigned char)exclude_list[e]) ||
|
2002-03-23 20:47:21 +03:00
|
|
|
exclude_list[e] == '-' ||
|
|
|
|
exclude_list[e] == '.' ||
|
|
|
|
exclude_list[e] == '*')) e++;
|
|
|
|
|
|
|
|
if (exclude_list[s] == '*') {
|
|
|
|
/* wildcard at beginning of entry */
|
|
|
|
|
2002-12-18 19:23:11 +03:00
|
|
|
if ((addr && strnicmp(hostip + hostip_len - (e - s - 1),
|
|
|
|
exclude_list + s + 1, e - s - 1) == 0) ||
|
2002-03-23 20:47:21 +03:00
|
|
|
strnicmp(hostname + hostname_len - (e - s - 1),
|
|
|
|
exclude_list + s + 1, e - s - 1) == 0)
|
|
|
|
return 0; /* IP/hostname range excluded. do not use proxy. */
|
|
|
|
|
|
|
|
} else if (exclude_list[e-1] == '*') {
|
|
|
|
/* wildcard at end of entry */
|
|
|
|
|
2002-12-18 19:23:11 +03:00
|
|
|
if ((addr && strnicmp(hostip, exclude_list + s, e - s - 1) == 0) ||
|
2002-03-23 20:47:21 +03:00
|
|
|
strnicmp(hostname, exclude_list + s, e - s - 1) == 0)
|
|
|
|
return 0; /* IP/hostname range excluded. do not use proxy. */
|
|
|
|
|
|
|
|
} else {
|
|
|
|
/* no wildcard at either end, so let's try an absolute
|
|
|
|
* match (ie. a specific IP)
|
|
|
|
*/
|
|
|
|
|
2003-05-24 14:57:53 +04:00
|
|
|
if (addr && strnicmp(hostip, exclude_list + s, e - s) == 0)
|
2002-03-23 20:47:21 +03:00
|
|
|
return 0; /* IP/hostname excluded. do not use proxy. */
|
2003-05-24 14:57:53 +04:00
|
|
|
if (strnicmp(hostname, exclude_list + s, e - s) == 0)
|
2002-03-23 20:47:21 +03:00
|
|
|
return 0; /* IP/hostname excluded. do not use proxy. */
|
|
|
|
}
|
|
|
|
|
|
|
|
s = e;
|
2003-01-02 13:07:17 +03:00
|
|
|
|
|
|
|
/* Make sure we really have reached the next comma or end-of-string */
|
|
|
|
while (exclude_list[s] &&
|
2003-03-11 12:30:31 +03:00
|
|
|
!isspace((unsigned char)exclude_list[s]) &&
|
2003-01-02 13:07:17 +03:00
|
|
|
exclude_list[s] != ',') s++;
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* no matches in the exclude list, so use the proxy */
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2015-11-22 15:15:52 +03:00
|
|
|
static char *dns_log_msg(const char *host, int addressfamily,
|
|
|
|
const char *reason)
|
|
|
|
{
|
|
|
|
return dupprintf("Looking up host \"%s\"%s for %s", host,
|
|
|
|
(addressfamily == ADDRTYPE_IPV4 ? " (IPv4)" :
|
|
|
|
addressfamily == ADDRTYPE_IPV6 ? " (IPv6)" :
|
|
|
|
""), reason);
|
|
|
|
}
|
|
|
|
|
2015-05-15 13:15:42 +03:00
|
|
|
SockAddr name_lookup(const char *host, int port, char **canonicalname,
|
2015-11-22 12:58:14 +03:00
|
|
|
Conf *conf, int addressfamily, void *frontend,
|
|
|
|
const char *reason)
|
2002-12-18 19:23:11 +03:00
|
|
|
{
|
2015-11-22 12:58:14 +03:00
|
|
|
char *logmsg;
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
if (conf_get_int(conf, CONF_proxy_type) != PROXY_NONE &&
|
|
|
|
do_proxy_dns(conf) &&
|
|
|
|
proxy_for_destination(NULL, host, port, conf)) {
|
2015-11-22 12:58:14 +03:00
|
|
|
|
|
|
|
if (frontend) {
|
|
|
|
logmsg = dupprintf("Leaving host lookup to proxy of \"%s\""
|
|
|
|
" (for %s)", host, reason);
|
|
|
|
logevent(frontend, logmsg);
|
|
|
|
sfree(logmsg);
|
|
|
|
}
|
|
|
|
|
2002-12-18 19:23:11 +03:00
|
|
|
*canonicalname = dupstr(host);
|
|
|
|
return sk_nonamelookup(host);
|
2015-11-22 12:58:14 +03:00
|
|
|
} else {
|
|
|
|
if (frontend) {
|
2015-11-22 15:15:52 +03:00
|
|
|
logmsg = dns_log_msg(host, addressfamily, reason);
|
2015-11-22 12:58:14 +03:00
|
|
|
logevent(frontend, logmsg);
|
|
|
|
sfree(logmsg);
|
|
|
|
}
|
|
|
|
|
|
|
|
return sk_namelookup(host, canonicalname, addressfamily);
|
2002-12-18 19:23:11 +03:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-05-27 11:29:33 +03:00
|
|
|
static const struct Socket_vtable ProxySocket_sockvt = {
|
|
|
|
sk_proxy_plug,
|
|
|
|
sk_proxy_close,
|
|
|
|
sk_proxy_write,
|
|
|
|
sk_proxy_write_oob,
|
|
|
|
sk_proxy_write_eof,
|
|
|
|
sk_proxy_flush,
|
|
|
|
sk_proxy_set_frozen,
|
|
|
|
sk_proxy_socket_error,
|
|
|
|
NULL, /* peer_info */
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct Plug_vtable ProxySocket_plugvt = {
|
|
|
|
plug_proxy_log,
|
|
|
|
plug_proxy_closing,
|
|
|
|
plug_proxy_receive,
|
|
|
|
plug_proxy_sent,
|
|
|
|
plug_proxy_accepting
|
|
|
|
};
|
|
|
|
|
2015-05-15 13:15:42 +03:00
|
|
|
Socket new_connection(SockAddr addr, const char *hostname,
|
2002-03-23 20:47:21 +03:00
|
|
|
int port, int privport,
|
2004-06-20 21:07:38 +04:00
|
|
|
int oobinline, int nodelay, int keepalive,
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
Plug plug, Conf *conf)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
if (conf_get_int(conf, CONF_proxy_type) != PROXY_NONE &&
|
|
|
|
proxy_for_destination(addr, hostname, port, conf))
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
2018-05-27 11:29:33 +03:00
|
|
|
ProxySocket *ret;
|
2002-03-23 20:47:21 +03:00
|
|
|
SockAddr proxy_addr;
|
2003-05-04 18:18:18 +04:00
|
|
|
char *proxy_canonical_name;
|
2015-11-22 15:15:52 +03:00
|
|
|
const char *proxy_type;
|
2003-05-06 23:52:31 +04:00
|
|
|
Socket sret;
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
int type;
|
2003-05-06 23:52:31 +04:00
|
|
|
|
2003-05-10 15:50:18 +04:00
|
|
|
if ((sret = platform_new_connection(addr, hostname, port, privport,
|
2004-06-20 21:07:38 +04:00
|
|
|
oobinline, nodelay, keepalive,
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
plug, conf)) !=
|
2003-05-10 15:50:18 +04:00
|
|
|
NULL)
|
2003-05-06 23:52:31 +04:00
|
|
|
return sret;
|
2002-03-23 20:47:21 +03:00
|
|
|
|
2018-05-27 11:29:33 +03:00
|
|
|
ret = snew(ProxySocket);
|
|
|
|
ret->sockvt = &ProxySocket_sockvt;
|
|
|
|
ret->plugvt = &ProxySocket_plugvt;
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
ret->conf = conf_copy(conf);
|
2002-03-23 20:47:21 +03:00
|
|
|
ret->plug = plug;
|
2003-08-07 20:04:33 +04:00
|
|
|
ret->remote_addr = addr; /* will need to be freed on close */
|
2002-03-23 20:47:21 +03:00
|
|
|
ret->remote_port = port;
|
|
|
|
|
2002-10-11 16:29:27 +04:00
|
|
|
ret->error = NULL;
|
|
|
|
ret->pending_flush = 0;
|
2011-09-13 15:44:03 +04:00
|
|
|
ret->pending_eof = 0;
|
2002-10-11 16:29:27 +04:00
|
|
|
ret->freeze = 0;
|
|
|
|
|
2002-03-23 20:47:21 +03:00
|
|
|
bufchain_init(&ret->pending_input_data);
|
|
|
|
bufchain_init(&ret->pending_output_data);
|
|
|
|
bufchain_init(&ret->pending_oob_output_data);
|
|
|
|
|
|
|
|
ret->sub_socket = NULL;
|
|
|
|
ret->state = PROXY_STATE_NEW;
|
2002-10-22 13:40:38 +04:00
|
|
|
ret->negotiate = NULL;
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
|
|
|
|
type = conf_get_int(conf, CONF_proxy_type);
|
|
|
|
if (type == PROXY_HTTP) {
|
2002-03-23 20:47:21 +03:00
|
|
|
ret->negotiate = proxy_http_negotiate;
|
2015-11-22 15:15:52 +03:00
|
|
|
proxy_type = "HTTP";
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
} else if (type == PROXY_SOCKS4) {
|
2003-05-07 16:07:23 +04:00
|
|
|
ret->negotiate = proxy_socks4_negotiate;
|
2015-11-22 15:15:52 +03:00
|
|
|
proxy_type = "SOCKS 4";
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
} else if (type == PROXY_SOCKS5) {
|
2003-05-07 16:07:23 +04:00
|
|
|
ret->negotiate = proxy_socks5_negotiate;
|
2015-11-22 15:15:52 +03:00
|
|
|
proxy_type = "SOCKS 5";
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
} else if (type == PROXY_TELNET) {
|
2002-03-23 20:47:21 +03:00
|
|
|
ret->negotiate = proxy_telnet_negotiate;
|
2015-11-22 15:15:52 +03:00
|
|
|
proxy_type = "Telnet";
|
2002-03-23 20:47:21 +03:00
|
|
|
} else {
|
2002-09-21 20:52:21 +04:00
|
|
|
ret->error = "Proxy error: Unknown proxy method";
|
2018-05-27 11:29:33 +03:00
|
|
|
return &ret->sockvt;
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
|
2015-11-22 15:15:52 +03:00
|
|
|
{
|
|
|
|
char *logmsg = dupprintf("Will use %s proxy at %s:%d to connect"
|
|
|
|
" to %s:%d", proxy_type,
|
|
|
|
conf_get_str(conf, CONF_proxy_host),
|
|
|
|
conf_get_int(conf, CONF_proxy_port),
|
|
|
|
hostname, port);
|
|
|
|
plug_log(plug, 2, NULL, 0, logmsg, 0);
|
|
|
|
sfree(logmsg);
|
|
|
|
}
|
|
|
|
|
|
|
|
{
|
|
|
|
char *logmsg = dns_log_msg(conf_get_str(conf, CONF_proxy_host),
|
|
|
|
conf_get_int(conf, CONF_addressfamily),
|
|
|
|
"proxy");
|
|
|
|
plug_log(plug, 2, NULL, 0, logmsg, 0);
|
|
|
|
sfree(logmsg);
|
|
|
|
}
|
|
|
|
|
2002-03-23 20:47:21 +03:00
|
|
|
/* look-up proxy */
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
proxy_addr = sk_namelookup(conf_get_str(conf, CONF_proxy_host),
|
|
|
|
&proxy_canonical_name,
|
|
|
|
conf_get_int(conf, CONF_addressfamily));
|
2003-05-04 18:18:18 +04:00
|
|
|
if (sk_addr_error(proxy_addr) != NULL) {
|
2002-12-18 15:32:18 +03:00
|
|
|
ret->error = "Proxy error: Unable to resolve proxy host name";
|
2013-07-22 23:55:55 +04:00
|
|
|
sk_addr_free(proxy_addr);
|
2018-05-27 11:29:33 +03:00
|
|
|
return &ret->sockvt;
|
2002-12-18 15:32:18 +03:00
|
|
|
}
|
2002-03-23 20:47:21 +03:00
|
|
|
sfree(proxy_canonical_name);
|
|
|
|
|
2015-11-22 15:15:52 +03:00
|
|
|
{
|
|
|
|
char addrbuf[256], *logmsg;
|
2017-02-04 17:36:12 +03:00
|
|
|
sk_getaddr(proxy_addr, addrbuf, lenof(addrbuf));
|
2015-11-22 15:15:52 +03:00
|
|
|
logmsg = dupprintf("Connecting to %s proxy at %s port %d",
|
|
|
|
proxy_type, addrbuf,
|
|
|
|
conf_get_int(conf, CONF_proxy_port));
|
|
|
|
plug_log(plug, 2, NULL, 0, logmsg, 0);
|
|
|
|
sfree(logmsg);
|
|
|
|
}
|
|
|
|
|
2002-03-23 20:47:21 +03:00
|
|
|
/* create the actual socket we will be using,
|
|
|
|
* connected to our proxy server and port.
|
|
|
|
*/
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
ret->sub_socket = sk_new(proxy_addr,
|
|
|
|
conf_get_int(conf, CONF_proxy_port),
|
2002-03-23 20:47:21 +03:00
|
|
|
privport, oobinline,
|
2018-05-27 11:29:33 +03:00
|
|
|
nodelay, keepalive, &ret->plugvt);
|
2002-03-23 20:47:21 +03:00
|
|
|
if (sk_socket_error(ret->sub_socket) != NULL)
|
2018-05-27 11:29:33 +03:00
|
|
|
return &ret->sockvt;
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
/* start the proxy negotiation process... */
|
|
|
|
sk_set_frozen(ret->sub_socket, 0);
|
|
|
|
ret->negotiate(ret, PROXY_CHANGE_NEW);
|
|
|
|
|
2018-05-27 11:29:33 +03:00
|
|
|
return &ret->sockvt;
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* no proxy, so just return the direct socket */
|
2004-06-20 21:07:38 +04:00
|
|
|
return sk_new(addr, port, privport, oobinline, nodelay, keepalive, plug);
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
|
2015-05-15 13:15:42 +03:00
|
|
|
Socket new_listener(const char *srcaddr, int port, Plug plug,
|
|
|
|
int local_host_only, Conf *conf, int addressfamily)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
|
|
|
/* TODO: SOCKS (and potentially others) support inbound
|
|
|
|
* TODO: connections via the proxy. support them.
|
|
|
|
*/
|
|
|
|
|
2004-12-30 19:45:11 +03:00
|
|
|
return sk_newlistener(srcaddr, port, plug, local_host_only, addressfamily);
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* ----------------------------------------------------------------------
|
|
|
|
* HTTP CONNECT proxy type.
|
|
|
|
*/
|
|
|
|
|
|
|
|
static int get_line_end (char * data, int len)
|
|
|
|
{
|
|
|
|
int off = 0;
|
|
|
|
|
|
|
|
while (off < len)
|
|
|
|
{
|
|
|
|
if (data[off] == '\n') {
|
|
|
|
/* we have a newline */
|
|
|
|
off++;
|
|
|
|
|
|
|
|
/* is that the only thing on this line? */
|
|
|
|
if (off <= 2) return off;
|
|
|
|
|
|
|
|
/* if not, then there is the possibility that this header
|
|
|
|
* continues onto the next line, if it starts with a space
|
|
|
|
* or a tab.
|
|
|
|
*/
|
|
|
|
|
|
|
|
if (off + 1 < len &&
|
|
|
|
data[off+1] != ' ' &&
|
|
|
|
data[off+1] != '\t') return off;
|
|
|
|
|
|
|
|
/* the line does continue, so we have to keep going
|
|
|
|
* until we see an the header's "real" end of line.
|
|
|
|
*/
|
|
|
|
off++;
|
|
|
|
}
|
|
|
|
|
|
|
|
off++;
|
|
|
|
}
|
|
|
|
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
2018-05-27 11:29:33 +03:00
|
|
|
int proxy_http_negotiate (ProxySocket *p, int change)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
|
|
|
if (p->state == PROXY_STATE_NEW) {
|
|
|
|
/* we are just beginning the proxy negotiate process,
|
|
|
|
* so we'll send off the initial bits of the request.
|
|
|
|
* for this proxy method, it's just a simple HTTP
|
|
|
|
* request
|
|
|
|
*/
|
2002-12-18 19:23:11 +03:00
|
|
|
char *buf, dest[512];
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
char *username, *password;
|
2002-03-23 20:47:21 +03:00
|
|
|
|
2002-12-18 19:23:11 +03:00
|
|
|
sk_getaddr(p->remote_addr, dest, lenof(dest));
|
2002-03-23 20:47:21 +03:00
|
|
|
|
2002-11-07 22:49:03 +03:00
|
|
|
buf = dupprintf("CONNECT %s:%i HTTP/1.1\r\nHost: %s:%i\r\n",
|
|
|
|
dest, p->remote_port, dest, p->remote_port);
|
2002-03-23 20:47:21 +03:00
|
|
|
sk_write(p->sub_socket, buf, strlen(buf));
|
2002-11-07 22:49:03 +03:00
|
|
|
sfree(buf);
|
2002-03-23 20:47:21 +03:00
|
|
|
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
username = conf_get_str(p->conf, CONF_proxy_username);
|
|
|
|
password = conf_get_str(p->conf, CONF_proxy_password);
|
|
|
|
if (username[0] || password[0]) {
|
|
|
|
char *buf, *buf2;
|
2002-09-21 18:03:05 +04:00
|
|
|
int i, j, len;
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
buf = dupprintf("%s:%s", username, password);
|
2002-09-21 18:03:05 +04:00
|
|
|
len = strlen(buf);
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
buf2 = snewn(len * 4 / 3 + 100, char);
|
2003-03-18 22:12:40 +03:00
|
|
|
sprintf(buf2, "Proxy-Authorization: Basic ");
|
2002-09-21 18:03:05 +04:00
|
|
|
for (i = 0, j = strlen(buf2); i < len; i += 3, j += 4)
|
2003-01-04 19:56:33 +03:00
|
|
|
base64_encode_atom((unsigned char *)(buf+i),
|
|
|
|
(len-i > 3 ? 3 : len-i), buf2+j);
|
2002-09-21 18:03:05 +04:00
|
|
|
strcpy(buf2+j, "\r\n");
|
|
|
|
sk_write(p->sub_socket, buf2, strlen(buf2));
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
sfree(buf);
|
|
|
|
sfree(buf2);
|
2002-09-21 18:03:05 +04:00
|
|
|
}
|
|
|
|
|
2002-12-08 18:32:40 +03:00
|
|
|
sk_write(p->sub_socket, "\r\n", 2);
|
2002-09-21 18:03:05 +04:00
|
|
|
|
2002-03-23 20:47:21 +03:00
|
|
|
p->state = 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_CLOSING) {
|
|
|
|
/* if our proxy negotiation process involves closing and opening
|
|
|
|
* new sockets, then we would want to intercept this closing
|
|
|
|
* callback when we were expecting it. if we aren't anticipating
|
|
|
|
* a socket close, then some error must have occurred. we'll
|
|
|
|
* just pass those errors up to the backend.
|
|
|
|
*/
|
2016-06-03 01:03:24 +03:00
|
|
|
plug_closing(p->plug, p->closing_error_msg, p->closing_error_code,
|
|
|
|
p->closing_calling_back);
|
|
|
|
return 0; /* ignored */
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_SENT) {
|
|
|
|
/* some (or all) of what we wrote to the proxy was sent.
|
|
|
|
* we don't do anything new, however, until we receive the
|
|
|
|
* proxy's response. we might want to set a timer so we can
|
|
|
|
* timeout the proxy negotiation after a while...
|
|
|
|
*/
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_ACCEPTING) {
|
|
|
|
/* we should _never_ see this, as we are using our socket to
|
|
|
|
* connect to a proxy, not accepting inbound connections.
|
|
|
|
* what should we do? close the socket with an appropriate
|
|
|
|
* error message?
|
|
|
|
*/
|
2013-11-17 18:03:55 +04:00
|
|
|
return plug_accepting(p->plug,
|
|
|
|
p->accepting_constructor, p->accepting_ctx);
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_RECEIVE) {
|
|
|
|
/* we have received data from the underlying socket, which
|
|
|
|
* we'll need to parse, process, and respond to appropriately.
|
|
|
|
*/
|
|
|
|
|
2002-09-21 20:52:21 +04:00
|
|
|
char *data, *datap;
|
2002-03-23 20:47:21 +03:00
|
|
|
int len;
|
|
|
|
int eol;
|
|
|
|
|
|
|
|
if (p->state == 1) {
|
|
|
|
|
|
|
|
int min_ver, maj_ver, status;
|
|
|
|
|
|
|
|
/* get the status line */
|
2002-09-21 20:52:21 +04:00
|
|
|
len = bufchain_size(&p->pending_input_data);
|
|
|
|
assert(len > 0); /* or we wouldn't be here */
|
2004-02-10 22:07:45 +03:00
|
|
|
data = snewn(len+1, char);
|
2002-09-21 20:52:21 +04:00
|
|
|
bufchain_fetch(&p->pending_input_data, data, len);
|
2004-02-10 22:07:45 +03:00
|
|
|
/*
|
|
|
|
* We must NUL-terminate this data, because Windows
|
|
|
|
* sscanf appears to require a NUL at the end of the
|
|
|
|
* string because it strlens it _first_. Sigh.
|
|
|
|
*/
|
|
|
|
data[len] = '\0';
|
2002-09-21 20:52:21 +04:00
|
|
|
|
2002-03-23 20:47:21 +03:00
|
|
|
eol = get_line_end(data, len);
|
2002-09-21 20:52:21 +04:00
|
|
|
if (eol < 0) {
|
|
|
|
sfree(data);
|
|
|
|
return 1;
|
|
|
|
}
|
2002-03-23 20:47:21 +03:00
|
|
|
|
2002-09-21 20:52:21 +04:00
|
|
|
status = -1;
|
|
|
|
/* We can't rely on whether the %n incremented the sscanf return */
|
|
|
|
if (sscanf((char *)data, "HTTP/%i.%i %n",
|
|
|
|
&maj_ver, &min_ver, &status) < 2 || status == -1) {
|
|
|
|
plug_closing(p->plug, "Proxy error: HTTP response was absent",
|
|
|
|
PROXY_ERROR_GENERAL, 0);
|
|
|
|
sfree(data);
|
|
|
|
return 1;
|
|
|
|
}
|
2002-03-23 20:47:21 +03:00
|
|
|
|
|
|
|
/* remove the status line from the input buffer. */
|
|
|
|
bufchain_consume(&p->pending_input_data, eol);
|
2002-09-21 20:52:21 +04:00
|
|
|
if (data[status] != '2') {
|
2002-03-23 20:47:21 +03:00
|
|
|
/* error */
|
2002-11-07 22:49:03 +03:00
|
|
|
char *buf;
|
2002-09-21 20:52:21 +04:00
|
|
|
data[eol] = '\0';
|
|
|
|
while (eol > status &&
|
|
|
|
(data[eol-1] == '\r' || data[eol-1] == '\n'))
|
|
|
|
data[--eol] = '\0';
|
2002-11-07 22:49:03 +03:00
|
|
|
buf = dupprintf("Proxy error: %s", data+status);
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, buf, PROXY_ERROR_GENERAL, 0);
|
2002-11-07 22:49:03 +03:00
|
|
|
sfree(buf);
|
2002-09-21 20:52:21 +04:00
|
|
|
sfree(data);
|
2002-03-23 20:47:21 +03:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2002-09-21 20:52:21 +04:00
|
|
|
sfree(data);
|
|
|
|
|
2002-03-23 20:47:21 +03:00
|
|
|
p->state = 2;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (p->state == 2) {
|
|
|
|
|
|
|
|
/* get headers. we're done when we get a
|
|
|
|
* header of length 2, (ie. just "\r\n")
|
|
|
|
*/
|
|
|
|
|
2002-09-21 20:52:21 +04:00
|
|
|
len = bufchain_size(&p->pending_input_data);
|
|
|
|
assert(len > 0); /* or we wouldn't be here */
|
2003-03-29 19:14:26 +03:00
|
|
|
data = snewn(len, char);
|
2002-09-21 20:52:21 +04:00
|
|
|
datap = data;
|
|
|
|
bufchain_fetch(&p->pending_input_data, data, len);
|
|
|
|
|
|
|
|
eol = get_line_end(datap, len);
|
|
|
|
if (eol < 0) {
|
|
|
|
sfree(data);
|
|
|
|
return 1;
|
|
|
|
}
|
2002-03-23 20:47:21 +03:00
|
|
|
while (eol > 2)
|
|
|
|
{
|
|
|
|
bufchain_consume(&p->pending_input_data, eol);
|
2002-09-21 20:52:21 +04:00
|
|
|
datap += eol;
|
2002-12-08 18:32:40 +03:00
|
|
|
len -= eol;
|
2002-09-21 20:52:21 +04:00
|
|
|
eol = get_line_end(datap, len);
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
if (eol == 2) {
|
|
|
|
/* we're done */
|
|
|
|
bufchain_consume(&p->pending_input_data, 2);
|
|
|
|
proxy_activate(p);
|
|
|
|
/* proxy activate will have dealt with
|
|
|
|
* whatever is left of the buffer */
|
2002-09-21 20:52:21 +04:00
|
|
|
sfree(data);
|
2002-03-23 20:47:21 +03:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2002-09-21 20:52:21 +04:00
|
|
|
sfree(data);
|
2002-03-23 20:47:21 +03:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: unexpected proxy error",
|
2002-03-23 20:47:21 +03:00
|
|
|
PROXY_ERROR_UNEXPECTED, 0);
|
2002-04-27 19:01:18 +04:00
|
|
|
return 1;
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* ----------------------------------------------------------------------
|
2002-04-27 19:01:18 +04:00
|
|
|
* SOCKS proxy type.
|
2002-03-23 20:47:21 +03:00
|
|
|
*/
|
|
|
|
|
2002-04-27 19:01:18 +04:00
|
|
|
/* SOCKS version 4 */
|
2018-05-27 11:29:33 +03:00
|
|
|
int proxy_socks4_negotiate (ProxySocket *p, int change)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
2002-04-27 19:01:18 +04:00
|
|
|
if (p->state == PROXY_CHANGE_NEW) {
|
|
|
|
|
|
|
|
/* request format:
|
|
|
|
* version number (1 byte) = 4
|
|
|
|
* command code (1 byte)
|
|
|
|
* 1 = CONNECT
|
|
|
|
* 2 = BIND
|
|
|
|
* dest. port (2 bytes) [network order]
|
|
|
|
* dest. address (4 bytes)
|
|
|
|
* user ID (variable length, null terminated string)
|
|
|
|
*/
|
|
|
|
|
2018-05-24 15:30:16 +03:00
|
|
|
strbuf *command = strbuf_new();
|
|
|
|
char hostname[512];
|
|
|
|
int write_hostname = FALSE;
|
|
|
|
|
|
|
|
put_byte(command, 4); /* SOCKS version 4 */
|
|
|
|
put_byte(command, 1); /* CONNECT command */
|
|
|
|
put_uint16(command, p->remote_port);
|
|
|
|
|
|
|
|
switch (sk_addrtype(p->remote_addr)) {
|
|
|
|
case ADDRTYPE_IPV4:
|
|
|
|
{
|
|
|
|
char addr[4];
|
|
|
|
sk_addrcopy(p->remote_addr, addr);
|
|
|
|
put_data(command, addr, 4);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
case ADDRTYPE_NAME:
|
|
|
|
sk_getaddr(p->remote_addr, hostname, lenof(hostname));
|
|
|
|
put_uint32(command, 1);
|
|
|
|
write_hostname = TRUE;
|
|
|
|
break;
|
|
|
|
case ADDRTYPE_IPV6:
|
2012-10-17 00:15:52 +04:00
|
|
|
p->error = "Proxy error: SOCKS version 4 does not support IPv6";
|
2018-05-24 15:30:16 +03:00
|
|
|
strbuf_free(command);
|
|
|
|
return 1;
|
2002-04-27 19:01:18 +04:00
|
|
|
}
|
|
|
|
|
2018-05-24 15:30:16 +03:00
|
|
|
put_asciz(command, conf_get_str(p->conf, CONF_proxy_username));
|
|
|
|
if (write_hostname)
|
|
|
|
put_asciz(command, hostname);
|
|
|
|
sk_write(p->sub_socket, command->s, command->len);
|
|
|
|
strbuf_free(command);
|
2002-04-27 19:01:18 +04:00
|
|
|
|
|
|
|
p->state = 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_CLOSING) {
|
|
|
|
/* if our proxy negotiation process involves closing and opening
|
|
|
|
* new sockets, then we would want to intercept this closing
|
|
|
|
* callback when we were expecting it. if we aren't anticipating
|
|
|
|
* a socket close, then some error must have occurred. we'll
|
|
|
|
* just pass those errors up to the backend.
|
|
|
|
*/
|
2016-06-03 01:03:24 +03:00
|
|
|
plug_closing(p->plug, p->closing_error_msg, p->closing_error_code,
|
|
|
|
p->closing_calling_back);
|
|
|
|
return 0; /* ignored */
|
2002-04-27 19:01:18 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_SENT) {
|
|
|
|
/* some (or all) of what we wrote to the proxy was sent.
|
|
|
|
* we don't do anything new, however, until we receive the
|
|
|
|
* proxy's response. we might want to set a timer so we can
|
|
|
|
* timeout the proxy negotiation after a while...
|
|
|
|
*/
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_ACCEPTING) {
|
|
|
|
/* we should _never_ see this, as we are using our socket to
|
|
|
|
* connect to a proxy, not accepting inbound connections.
|
|
|
|
* what should we do? close the socket with an appropriate
|
|
|
|
* error message?
|
|
|
|
*/
|
2013-11-17 18:03:55 +04:00
|
|
|
return plug_accepting(p->plug,
|
|
|
|
p->accepting_constructor, p->accepting_ctx);
|
2002-04-27 19:01:18 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_RECEIVE) {
|
|
|
|
/* we have received data from the underlying socket, which
|
|
|
|
* we'll need to parse, process, and respond to appropriately.
|
|
|
|
*/
|
|
|
|
|
|
|
|
if (p->state == 1) {
|
|
|
|
/* response format:
|
|
|
|
* version number (1 byte) = 4
|
|
|
|
* reply code (1 byte)
|
|
|
|
* 90 = request granted
|
|
|
|
* 91 = request rejected or failed
|
|
|
|
* 92 = request rejected due to lack of IDENTD on client
|
|
|
|
* 93 = request rejected due to difference in user ID
|
|
|
|
* (what we sent vs. what IDENTD said)
|
|
|
|
* dest. port (2 bytes)
|
|
|
|
* dest. address (4 bytes)
|
|
|
|
*/
|
|
|
|
|
2002-09-21 20:52:21 +04:00
|
|
|
char data[8];
|
2002-04-27 19:01:18 +04:00
|
|
|
|
2002-09-21 20:52:21 +04:00
|
|
|
if (bufchain_size(&p->pending_input_data) < 8)
|
|
|
|
return 1; /* not got anything yet */
|
|
|
|
|
2002-04-27 19:01:18 +04:00
|
|
|
/* get the response */
|
2002-09-21 20:52:21 +04:00
|
|
|
bufchain_fetch(&p->pending_input_data, data, 8);
|
2002-04-27 19:01:18 +04:00
|
|
|
|
|
|
|
if (data[0] != 0) {
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: SOCKS proxy responded with "
|
2002-04-27 19:01:18 +04:00
|
|
|
"unexpected reply code version",
|
|
|
|
PROXY_ERROR_GENERAL, 0);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (data[1] != 90) {
|
|
|
|
|
|
|
|
switch (data[1]) {
|
|
|
|
case 92:
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: SOCKS server wanted IDENTD on client",
|
2002-04-27 19:01:18 +04:00
|
|
|
PROXY_ERROR_GENERAL, 0);
|
|
|
|
break;
|
|
|
|
case 93:
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: Username and IDENTD on client don't agree",
|
2002-04-27 19:01:18 +04:00
|
|
|
PROXY_ERROR_GENERAL, 0);
|
|
|
|
break;
|
|
|
|
case 91:
|
|
|
|
default:
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: Error while communicating with proxy",
|
2002-04-27 19:01:18 +04:00
|
|
|
PROXY_ERROR_GENERAL, 0);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 1;
|
|
|
|
}
|
2002-09-21 20:52:21 +04:00
|
|
|
bufchain_consume(&p->pending_input_data, 8);
|
2002-04-27 19:01:18 +04:00
|
|
|
|
|
|
|
/* we're done */
|
|
|
|
proxy_activate(p);
|
|
|
|
/* proxy activate will have dealt with
|
|
|
|
* whatever is left of the buffer */
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: unexpected proxy error",
|
2002-04-27 19:01:18 +04:00
|
|
|
PROXY_ERROR_UNEXPECTED, 0);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* SOCKS version 5 */
|
2018-05-27 11:29:33 +03:00
|
|
|
int proxy_socks5_negotiate (ProxySocket *p, int change)
|
2002-04-27 19:01:18 +04:00
|
|
|
{
|
|
|
|
if (p->state == PROXY_CHANGE_NEW) {
|
|
|
|
|
|
|
|
/* initial command:
|
|
|
|
* version number (1 byte) = 5
|
|
|
|
* number of available authentication methods (1 byte)
|
|
|
|
* available authentication methods (1 byte * previous value)
|
|
|
|
* authentication methods:
|
|
|
|
* 0x00 = no authentication
|
|
|
|
* 0x01 = GSSAPI
|
|
|
|
* 0x02 = username/password
|
|
|
|
* 0x03 = CHAP
|
|
|
|
*/
|
|
|
|
|
2018-05-24 15:30:16 +03:00
|
|
|
strbuf *command;
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
char *username, *password;
|
2018-05-24 15:30:16 +03:00
|
|
|
int method_count_offset, methods_start;
|
2002-04-27 19:01:18 +04:00
|
|
|
|
2018-05-24 15:30:16 +03:00
|
|
|
command = strbuf_new();
|
|
|
|
put_byte(command, 5); /* SOCKS version 5 */
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
username = conf_get_str(p->conf, CONF_proxy_username);
|
|
|
|
password = conf_get_str(p->conf, CONF_proxy_password);
|
2018-05-24 15:30:16 +03:00
|
|
|
|
|
|
|
method_count_offset = command->len;
|
|
|
|
put_byte(command, 0);
|
|
|
|
methods_start = command->len;
|
|
|
|
|
|
|
|
put_byte(command, 0x00); /* no authentication */
|
|
|
|
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
if (username[0] || password[0]) {
|
2018-05-24 15:30:16 +03:00
|
|
|
proxy_socks5_offerencryptedauth(BinarySink_UPCAST(command));
|
|
|
|
put_byte(command, 0x02); /* username/password */
|
2002-09-21 20:07:43 +04:00
|
|
|
}
|
2002-04-27 19:01:18 +04:00
|
|
|
|
2018-05-24 15:30:16 +03:00
|
|
|
command->u[method_count_offset] = command->len - methods_start;
|
|
|
|
|
|
|
|
sk_write(p->sub_socket, command->s, command->len);
|
|
|
|
strbuf_free(command);
|
2002-04-27 19:01:18 +04:00
|
|
|
|
|
|
|
p->state = 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_CLOSING) {
|
|
|
|
/* if our proxy negotiation process involves closing and opening
|
|
|
|
* new sockets, then we would want to intercept this closing
|
|
|
|
* callback when we were expecting it. if we aren't anticipating
|
|
|
|
* a socket close, then some error must have occurred. we'll
|
|
|
|
* just pass those errors up to the backend.
|
|
|
|
*/
|
2016-06-03 01:03:24 +03:00
|
|
|
plug_closing(p->plug, p->closing_error_msg, p->closing_error_code,
|
|
|
|
p->closing_calling_back);
|
|
|
|
return 0; /* ignored */
|
2002-04-27 19:01:18 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_SENT) {
|
|
|
|
/* some (or all) of what we wrote to the proxy was sent.
|
|
|
|
* we don't do anything new, however, until we receive the
|
|
|
|
* proxy's response. we might want to set a timer so we can
|
|
|
|
* timeout the proxy negotiation after a while...
|
|
|
|
*/
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_ACCEPTING) {
|
|
|
|
/* we should _never_ see this, as we are using our socket to
|
|
|
|
* connect to a proxy, not accepting inbound connections.
|
|
|
|
* what should we do? close the socket with an appropriate
|
|
|
|
* error message?
|
|
|
|
*/
|
2013-11-17 18:03:55 +04:00
|
|
|
return plug_accepting(p->plug,
|
|
|
|
p->accepting_constructor, p->accepting_ctx);
|
2002-04-27 19:01:18 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_RECEIVE) {
|
|
|
|
/* we have received data from the underlying socket, which
|
|
|
|
* we'll need to parse, process, and respond to appropriately.
|
|
|
|
*/
|
|
|
|
|
|
|
|
if (p->state == 1) {
|
|
|
|
|
|
|
|
/* initial response:
|
|
|
|
* version number (1 byte) = 5
|
|
|
|
* authentication method (1 byte)
|
|
|
|
* authentication methods:
|
|
|
|
* 0x00 = no authentication
|
|
|
|
* 0x01 = GSSAPI
|
2004-08-30 17:11:17 +04:00
|
|
|
* 0x02 = username/password
|
2002-04-27 19:01:18 +04:00
|
|
|
* 0x03 = CHAP
|
|
|
|
* 0xff = no acceptable methods
|
|
|
|
*/
|
2002-09-21 20:52:21 +04:00
|
|
|
char data[2];
|
|
|
|
|
|
|
|
if (bufchain_size(&p->pending_input_data) < 2)
|
|
|
|
return 1; /* not got anything yet */
|
2002-04-27 19:01:18 +04:00
|
|
|
|
|
|
|
/* get the response */
|
2002-09-21 20:52:21 +04:00
|
|
|
bufchain_fetch(&p->pending_input_data, data, 2);
|
2002-04-27 19:01:18 +04:00
|
|
|
|
|
|
|
if (data[0] != 5) {
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: SOCKS proxy returned unexpected version",
|
2002-04-27 19:01:18 +04:00
|
|
|
PROXY_ERROR_GENERAL, 0);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (data[1] == 0x00) p->state = 2; /* no authentication needed */
|
|
|
|
else if (data[1] == 0x01) p->state = 4; /* GSSAPI authentication */
|
|
|
|
else if (data[1] == 0x02) p->state = 5; /* username/password authentication */
|
|
|
|
else if (data[1] == 0x03) p->state = 6; /* CHAP authentication */
|
|
|
|
else {
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: SOCKS proxy did not accept our authentication",
|
2002-04-27 19:01:18 +04:00
|
|
|
PROXY_ERROR_GENERAL, 0);
|
|
|
|
return 1;
|
|
|
|
}
|
2002-09-21 20:07:43 +04:00
|
|
|
bufchain_consume(&p->pending_input_data, 2);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (p->state == 7) {
|
|
|
|
|
|
|
|
/* password authentication reply format:
|
|
|
|
* version number (1 bytes) = 1
|
|
|
|
* reply code (1 byte)
|
|
|
|
* 0 = succeeded
|
|
|
|
* >0 = failed
|
|
|
|
*/
|
2002-09-21 20:52:21 +04:00
|
|
|
char data[2];
|
|
|
|
|
|
|
|
if (bufchain_size(&p->pending_input_data) < 2)
|
|
|
|
return 1; /* not got anything yet */
|
2002-09-21 20:07:43 +04:00
|
|
|
|
|
|
|
/* get the response */
|
2002-09-21 20:52:21 +04:00
|
|
|
bufchain_fetch(&p->pending_input_data, data, 2);
|
2002-09-21 20:07:43 +04:00
|
|
|
|
|
|
|
if (data[0] != 1) {
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: SOCKS password "
|
|
|
|
"subnegotiation contained wrong version number",
|
2002-09-21 20:07:43 +04:00
|
|
|
PROXY_ERROR_GENERAL, 0);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (data[1] != 0) {
|
|
|
|
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: SOCKS proxy refused"
|
|
|
|
" password authentication",
|
2002-09-21 20:07:43 +04:00
|
|
|
PROXY_ERROR_GENERAL, 0);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
bufchain_consume(&p->pending_input_data, 2);
|
|
|
|
p->state = 2; /* now proceed as authenticated */
|
2002-04-27 19:01:18 +04:00
|
|
|
}
|
|
|
|
|
2004-08-30 17:11:17 +04:00
|
|
|
if (p->state == 8) {
|
|
|
|
int ret;
|
|
|
|
ret = proxy_socks5_handlechap(p);
|
|
|
|
if (ret) return ret;
|
|
|
|
}
|
|
|
|
|
2002-04-27 19:01:18 +04:00
|
|
|
if (p->state == 2) {
|
|
|
|
|
|
|
|
/* request format:
|
|
|
|
* version number (1 byte) = 5
|
|
|
|
* command code (1 byte)
|
|
|
|
* 1 = CONNECT
|
|
|
|
* 2 = BIND
|
|
|
|
* 3 = UDP ASSOCIATE
|
|
|
|
* reserved (1 byte) = 0x00
|
|
|
|
* address type (1 byte)
|
|
|
|
* 1 = IPv4
|
|
|
|
* 3 = domainname (first byte has length, no terminating null)
|
|
|
|
* 4 = IPv6
|
|
|
|
* dest. address (variable)
|
|
|
|
* dest. port (2 bytes) [network order]
|
|
|
|
*/
|
|
|
|
|
2018-05-24 15:30:16 +03:00
|
|
|
strbuf *command = strbuf_new();
|
|
|
|
put_byte(command, 5); /* SOCKS version 5 */
|
|
|
|
put_byte(command, 1); /* CONNECT command */
|
|
|
|
put_byte(command, 0x00); /* reserved byte */
|
|
|
|
|
|
|
|
switch (sk_addrtype(p->remote_addr)) {
|
|
|
|
case ADDRTYPE_IPV4:
|
|
|
|
put_byte(command, 1); /* IPv4 */
|
|
|
|
sk_addrcopy(p->remote_addr, strbuf_append(command, 4));
|
|
|
|
break;
|
|
|
|
case ADDRTYPE_IPV6:
|
|
|
|
put_byte(command, 4); /* IPv6 */
|
|
|
|
sk_addrcopy(p->remote_addr, strbuf_append(command, 16));
|
|
|
|
break;
|
|
|
|
case ADDRTYPE_NAME:
|
|
|
|
{
|
|
|
|
char hostname[512];
|
|
|
|
put_byte(command, 3); /* domain name */
|
|
|
|
sk_getaddr(p->remote_addr, hostname, lenof(hostname));
|
|
|
|
if (!put_pstring(command, hostname)) {
|
|
|
|
p->error = "Proxy error: SOCKS 5 cannot "
|
|
|
|
"support host names longer than 255 chars";
|
|
|
|
strbuf_free(command);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
break;
|
2002-04-27 19:01:18 +04:00
|
|
|
}
|
|
|
|
|
2018-05-24 15:30:16 +03:00
|
|
|
put_uint16(command, p->remote_port);
|
2002-04-27 19:01:18 +04:00
|
|
|
|
2018-05-24 15:30:16 +03:00
|
|
|
sk_write(p->sub_socket, command->s, command->len);
|
2002-04-27 19:01:18 +04:00
|
|
|
|
2018-05-24 15:30:16 +03:00
|
|
|
strbuf_free(command);
|
2002-04-27 19:01:18 +04:00
|
|
|
|
|
|
|
p->state = 3;
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (p->state == 3) {
|
|
|
|
|
|
|
|
/* reply format:
|
|
|
|
* version number (1 bytes) = 5
|
|
|
|
* reply code (1 byte)
|
|
|
|
* 0 = succeeded
|
|
|
|
* 1 = general SOCKS server failure
|
|
|
|
* 2 = connection not allowed by ruleset
|
|
|
|
* 3 = network unreachable
|
|
|
|
* 4 = host unreachable
|
|
|
|
* 5 = connection refused
|
|
|
|
* 6 = TTL expired
|
|
|
|
* 7 = command not supported
|
|
|
|
* 8 = address type not supported
|
|
|
|
* reserved (1 byte) = x00
|
|
|
|
* address type (1 byte)
|
|
|
|
* 1 = IPv4
|
|
|
|
* 3 = domainname (first byte has length, no terminating null)
|
|
|
|
* 4 = IPv6
|
|
|
|
* server bound address (variable)
|
|
|
|
* server bound port (2 bytes) [network order]
|
|
|
|
*/
|
2002-09-21 20:52:21 +04:00
|
|
|
char data[5];
|
|
|
|
int len;
|
|
|
|
|
|
|
|
/* First 5 bytes of packet are enough to tell its length. */
|
|
|
|
if (bufchain_size(&p->pending_input_data) < 5)
|
|
|
|
return 1; /* not got anything yet */
|
2002-04-27 19:01:18 +04:00
|
|
|
|
|
|
|
/* get the response */
|
2002-09-21 20:52:21 +04:00
|
|
|
bufchain_fetch(&p->pending_input_data, data, 5);
|
2002-04-27 19:01:18 +04:00
|
|
|
|
|
|
|
if (data[0] != 5) {
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: SOCKS proxy returned wrong version number",
|
2002-04-27 19:01:18 +04:00
|
|
|
PROXY_ERROR_GENERAL, 0);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (data[1] != 0) {
|
2002-09-21 20:52:21 +04:00
|
|
|
char buf[256];
|
|
|
|
|
|
|
|
strcpy(buf, "Proxy error: ");
|
2002-04-27 19:01:18 +04:00
|
|
|
|
|
|
|
switch (data[1]) {
|
2002-09-21 20:52:21 +04:00
|
|
|
case 1: strcat(buf, "General SOCKS server failure"); break;
|
|
|
|
case 2: strcat(buf, "Connection not allowed by ruleset"); break;
|
|
|
|
case 3: strcat(buf, "Network unreachable"); break;
|
|
|
|
case 4: strcat(buf, "Host unreachable"); break;
|
|
|
|
case 5: strcat(buf, "Connection refused"); break;
|
|
|
|
case 6: strcat(buf, "TTL expired"); break;
|
|
|
|
case 7: strcat(buf, "Command not supported"); break;
|
|
|
|
case 8: strcat(buf, "Address type not supported"); break;
|
|
|
|
default: sprintf(buf+strlen(buf),
|
|
|
|
"Unrecognised SOCKS error code %d",
|
|
|
|
data[1]);
|
2002-04-27 19:01:18 +04:00
|
|
|
break;
|
|
|
|
}
|
2002-09-21 20:52:21 +04:00
|
|
|
plug_closing(p->plug, buf, PROXY_ERROR_GENERAL, 0);
|
|
|
|
|
|
|
|
return 1;
|
|
|
|
}
|
2002-04-27 19:01:18 +04:00
|
|
|
|
2002-09-21 20:52:21 +04:00
|
|
|
/*
|
|
|
|
* Eat the rest of the reply packet.
|
|
|
|
*/
|
|
|
|
len = 6; /* first 4 bytes, last 2 */
|
|
|
|
switch (data[3]) {
|
|
|
|
case 1: len += 4; break; /* IPv4 address */
|
|
|
|
case 4: len += 16; break;/* IPv6 address */
|
|
|
|
case 3: len += (unsigned char)data[4]; break; /* domain name */
|
|
|
|
default:
|
|
|
|
plug_closing(p->plug, "Proxy error: SOCKS proxy returned "
|
|
|
|
"unrecognised address format",
|
|
|
|
PROXY_ERROR_GENERAL, 0);
|
2002-04-27 19:01:18 +04:00
|
|
|
return 1;
|
|
|
|
}
|
2002-09-21 20:52:21 +04:00
|
|
|
if (bufchain_size(&p->pending_input_data) < len)
|
|
|
|
return 1; /* not got whole reply yet */
|
|
|
|
bufchain_consume(&p->pending_input_data, len);
|
2002-04-27 19:01:18 +04:00
|
|
|
|
|
|
|
/* we're done */
|
|
|
|
proxy_activate(p);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (p->state == 4) {
|
|
|
|
/* TODO: Handle GSSAPI authentication */
|
2002-09-24 23:27:58 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: We don't support GSSAPI authentication",
|
2002-04-27 19:01:18 +04:00
|
|
|
PROXY_ERROR_GENERAL, 0);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (p->state == 5) {
|
2018-05-24 15:30:16 +03:00
|
|
|
const char *username = conf_get_str(p->conf, CONF_proxy_username);
|
|
|
|
const char *password = conf_get_str(p->conf, CONF_proxy_password);
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
if (username[0] || password[0]) {
|
2018-05-24 15:30:16 +03:00
|
|
|
strbuf *auth = strbuf_new();
|
|
|
|
put_byte(auth, 1); /* version number of subnegotiation */
|
|
|
|
if (!put_pstring(auth, username)) {
|
|
|
|
p->error = "Proxy error: SOCKS 5 authentication cannot "
|
|
|
|
"support usernames longer than 255 chars";
|
|
|
|
strbuf_free(auth);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
if (!put_pstring(auth, password)) {
|
|
|
|
p->error = "Proxy error: SOCKS 5 authentication cannot "
|
|
|
|
"support passwords longer than 255 chars";
|
|
|
|
strbuf_free(auth);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
sk_write(p->sub_socket, auth->s, auth->len);
|
|
|
|
strbuf_free(auth);
|
2002-09-21 20:07:43 +04:00
|
|
|
p->state = 7;
|
|
|
|
} else
|
2002-09-24 23:27:58 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: Server chose "
|
2002-09-21 20:07:43 +04:00
|
|
|
"username/password authentication but we "
|
|
|
|
"didn't offer it!",
|
2002-04-27 19:01:18 +04:00
|
|
|
PROXY_ERROR_GENERAL, 0);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (p->state == 6) {
|
2004-08-30 17:11:17 +04:00
|
|
|
int ret;
|
|
|
|
ret = proxy_socks5_selectchap(p);
|
|
|
|
if (ret) return ret;
|
2002-04-27 19:01:18 +04:00
|
|
|
}
|
2002-09-21 20:07:43 +04:00
|
|
|
|
2002-04-27 19:01:18 +04:00
|
|
|
}
|
|
|
|
|
2002-09-24 23:27:58 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: Unexpected proxy error",
|
2002-04-27 19:01:18 +04:00
|
|
|
PROXY_ERROR_UNEXPECTED, 0);
|
|
|
|
return 1;
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* ----------------------------------------------------------------------
|
2002-03-28 00:09:16 +03:00
|
|
|
* `Telnet' proxy type.
|
2002-03-23 20:47:21 +03:00
|
|
|
*
|
|
|
|
* (This is for ad-hoc proxies where you connect to the proxy's
|
|
|
|
* telnet port and send a command such as `connect host port'. The
|
|
|
|
* command is configurable, since this proxy type is typically not
|
|
|
|
* standardised or at all well-defined.)
|
|
|
|
*/
|
|
|
|
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
char *format_telnet_command(SockAddr addr, int port, Conf *conf)
|
2002-03-23 20:47:21 +03:00
|
|
|
{
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
char *fmt = conf_get_str(conf, CONF_proxy_telnet_command);
|
2003-05-06 23:52:31 +04:00
|
|
|
char *ret = NULL;
|
|
|
|
int retlen = 0, retsize = 0;
|
|
|
|
int so = 0, eo = 0;
|
|
|
|
#define ENSURE(n) do { \
|
|
|
|
if (retsize < retlen + n) { \
|
|
|
|
retsize = retlen + n + 512; \
|
|
|
|
ret = sresize(ret, retsize, char); \
|
|
|
|
} \
|
|
|
|
} while (0)
|
|
|
|
|
|
|
|
/* we need to escape \\, \%, \r, \n, \t, \x??, \0???,
|
|
|
|
* %%, %host, %port, %user, and %pass
|
|
|
|
*/
|
2002-03-28 00:09:16 +03:00
|
|
|
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
while (fmt[eo] != 0) {
|
2002-03-28 00:09:16 +03:00
|
|
|
|
2003-05-06 23:52:31 +04:00
|
|
|
/* scan forward until we hit end-of-line,
|
|
|
|
* or an escape character (\ or %) */
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
while (fmt[eo] != 0 && fmt[eo] != '%' && fmt[eo] != '\\')
|
|
|
|
eo++;
|
2002-03-28 00:09:16 +03:00
|
|
|
|
2003-05-06 23:52:31 +04:00
|
|
|
/* if we hit eol, break out of our escaping loop */
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
if (fmt[eo] == 0) break;
|
2002-03-28 00:09:16 +03:00
|
|
|
|
2003-05-06 23:52:31 +04:00
|
|
|
/* if there was any unescaped text before the escape
|
|
|
|
* character, send that now */
|
|
|
|
if (eo != so) {
|
|
|
|
ENSURE(eo - so);
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
memcpy(ret + retlen, fmt + so, eo - so);
|
2003-05-06 23:52:31 +04:00
|
|
|
retlen += eo - so;
|
|
|
|
}
|
2002-03-28 00:09:16 +03:00
|
|
|
|
2003-05-06 23:52:31 +04:00
|
|
|
so = eo++;
|
2002-03-28 00:09:16 +03:00
|
|
|
|
2003-05-06 23:52:31 +04:00
|
|
|
/* if the escape character was the last character of
|
|
|
|
* the line, we'll just stop and send it. */
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
if (fmt[eo] == 0) break;
|
2002-03-28 00:09:16 +03:00
|
|
|
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
if (fmt[so] == '\\') {
|
2002-03-28 00:09:16 +03:00
|
|
|
|
2003-05-06 23:52:31 +04:00
|
|
|
/* we recognize \\, \%, \r, \n, \t, \x??.
|
|
|
|
* anything else, we just send unescaped (including the \).
|
|
|
|
*/
|
2002-03-28 00:09:16 +03:00
|
|
|
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
switch (fmt[eo]) {
|
2003-05-06 23:52:31 +04:00
|
|
|
|
|
|
|
case '\\':
|
|
|
|
ENSURE(1);
|
|
|
|
ret[retlen++] = '\\';
|
|
|
|
eo++;
|
|
|
|
break;
|
|
|
|
|
|
|
|
case '%':
|
|
|
|
ENSURE(1);
|
|
|
|
ret[retlen++] = '%';
|
|
|
|
eo++;
|
|
|
|
break;
|
|
|
|
|
|
|
|
case 'r':
|
|
|
|
ENSURE(1);
|
|
|
|
ret[retlen++] = '\r';
|
|
|
|
eo++;
|
|
|
|
break;
|
|
|
|
|
|
|
|
case 'n':
|
|
|
|
ENSURE(1);
|
|
|
|
ret[retlen++] = '\n';
|
|
|
|
eo++;
|
|
|
|
break;
|
|
|
|
|
|
|
|
case 't':
|
|
|
|
ENSURE(1);
|
|
|
|
ret[retlen++] = '\t';
|
|
|
|
eo++;
|
|
|
|
break;
|
|
|
|
|
|
|
|
case 'x':
|
|
|
|
case 'X':
|
|
|
|
{
|
2002-03-28 00:09:16 +03:00
|
|
|
/* escaped hexadecimal value (ie. \xff) */
|
|
|
|
unsigned char v = 0;
|
|
|
|
int i = 0;
|
|
|
|
|
|
|
|
for (;;) {
|
|
|
|
eo++;
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
if (fmt[eo] >= '0' && fmt[eo] <= '9')
|
|
|
|
v += fmt[eo] - '0';
|
|
|
|
else if (fmt[eo] >= 'a' && fmt[eo] <= 'f')
|
|
|
|
v += fmt[eo] - 'a' + 10;
|
|
|
|
else if (fmt[eo] >= 'A' && fmt[eo] <= 'F')
|
|
|
|
v += fmt[eo] - 'A' + 10;
|
2002-03-28 00:09:16 +03:00
|
|
|
else {
|
|
|
|
/* non hex character, so we abort and just
|
|
|
|
* send the whole thing unescaped (including \x)
|
|
|
|
*/
|
2003-05-06 23:52:31 +04:00
|
|
|
ENSURE(1);
|
|
|
|
ret[retlen++] = '\\';
|
2002-03-28 00:09:16 +03:00
|
|
|
eo = so + 1;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* we only extract two hex characters */
|
|
|
|
if (i == 1) {
|
2003-05-06 23:52:31 +04:00
|
|
|
ENSURE(1);
|
|
|
|
ret[retlen++] = v;
|
2002-03-28 00:09:16 +03:00
|
|
|
eo++;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
i++;
|
|
|
|
v <<= 4;
|
|
|
|
}
|
|
|
|
}
|
2003-05-06 23:52:31 +04:00
|
|
|
break;
|
2002-03-28 00:09:16 +03:00
|
|
|
|
2003-05-06 23:52:31 +04:00
|
|
|
default:
|
|
|
|
ENSURE(2);
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
memcpy(ret+retlen, fmt + so, 2);
|
2003-05-06 23:52:31 +04:00
|
|
|
retlen += 2;
|
|
|
|
eo++;
|
|
|
|
break;
|
2002-03-28 00:09:16 +03:00
|
|
|
}
|
2003-05-06 23:52:31 +04:00
|
|
|
} else {
|
2002-03-28 00:09:16 +03:00
|
|
|
|
2003-05-06 23:52:31 +04:00
|
|
|
/* % escape. we recognize %%, %host, %port, %user, %pass.
|
2005-01-07 17:22:17 +03:00
|
|
|
* %proxyhost, %proxyport. Anything else we just send
|
|
|
|
* unescaped (including the %).
|
2003-05-06 23:52:31 +04:00
|
|
|
*/
|
2002-03-28 00:09:16 +03:00
|
|
|
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
if (fmt[eo] == '%') {
|
2003-05-06 23:52:31 +04:00
|
|
|
ENSURE(1);
|
|
|
|
ret[retlen++] = '%';
|
|
|
|
eo++;
|
|
|
|
}
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
else if (strnicmp(fmt + eo, "host", 4) == 0) {
|
2003-05-06 23:52:31 +04:00
|
|
|
char dest[512];
|
|
|
|
int destlen;
|
|
|
|
sk_getaddr(addr, dest, lenof(dest));
|
|
|
|
destlen = strlen(dest);
|
|
|
|
ENSURE(destlen);
|
|
|
|
memcpy(ret+retlen, dest, destlen);
|
|
|
|
retlen += destlen;
|
|
|
|
eo += 4;
|
|
|
|
}
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
else if (strnicmp(fmt + eo, "port", 4) == 0) {
|
2003-05-06 23:52:31 +04:00
|
|
|
char portstr[8], portlen;
|
|
|
|
portlen = sprintf(portstr, "%i", port);
|
|
|
|
ENSURE(portlen);
|
|
|
|
memcpy(ret + retlen, portstr, portlen);
|
|
|
|
retlen += portlen;
|
|
|
|
eo += 4;
|
|
|
|
}
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
else if (strnicmp(fmt + eo, "user", 4) == 0) {
|
|
|
|
char *username = conf_get_str(conf, CONF_proxy_username);
|
|
|
|
int userlen = strlen(username);
|
2003-05-06 23:52:31 +04:00
|
|
|
ENSURE(userlen);
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
memcpy(ret+retlen, username, userlen);
|
2003-05-06 23:52:31 +04:00
|
|
|
retlen += userlen;
|
|
|
|
eo += 4;
|
|
|
|
}
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
else if (strnicmp(fmt + eo, "pass", 4) == 0) {
|
|
|
|
char *password = conf_get_str(conf, CONF_proxy_password);
|
|
|
|
int passlen = strlen(password);
|
2003-05-06 23:52:31 +04:00
|
|
|
ENSURE(passlen);
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
memcpy(ret+retlen, password, passlen);
|
2003-05-06 23:52:31 +04:00
|
|
|
retlen += passlen;
|
|
|
|
eo += 4;
|
|
|
|
}
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
else if (strnicmp(fmt + eo, "proxyhost", 9) == 0) {
|
|
|
|
char *host = conf_get_str(conf, CONF_proxy_host);
|
|
|
|
int phlen = strlen(host);
|
2005-01-07 17:22:17 +03:00
|
|
|
ENSURE(phlen);
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
memcpy(ret+retlen, host, phlen);
|
2005-01-07 17:22:17 +03:00
|
|
|
retlen += phlen;
|
|
|
|
eo += 9;
|
|
|
|
}
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
else if (strnicmp(fmt + eo, "proxyport", 9) == 0) {
|
|
|
|
int port = conf_get_int(conf, CONF_proxy_port);
|
2005-01-07 17:22:17 +03:00
|
|
|
char pport[50];
|
|
|
|
int pplen;
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
sprintf(pport, "%d", port);
|
2007-01-22 02:34:51 +03:00
|
|
|
pplen = strlen(pport);
|
2005-01-07 17:22:17 +03:00
|
|
|
ENSURE(pplen);
|
|
|
|
memcpy(ret+retlen, pport, pplen);
|
|
|
|
retlen += pplen;
|
|
|
|
eo += 9;
|
|
|
|
}
|
2003-05-06 23:52:31 +04:00
|
|
|
else {
|
|
|
|
/* we don't escape this, so send the % now, and
|
|
|
|
* don't advance eo, so that we'll consider the
|
|
|
|
* text immediately following the % as unescaped.
|
|
|
|
*/
|
|
|
|
ENSURE(1);
|
|
|
|
ret[retlen++] = '%';
|
|
|
|
}
|
2002-03-28 00:09:16 +03:00
|
|
|
}
|
|
|
|
|
2003-05-06 23:52:31 +04:00
|
|
|
/* resume scanning for additional escapes after this one. */
|
|
|
|
so = eo;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* if there is any unescaped text at the end of the line, send it */
|
|
|
|
if (eo != so) {
|
|
|
|
ENSURE(eo - so);
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
memcpy(ret + retlen, fmt + so, eo - so);
|
2003-05-06 23:52:31 +04:00
|
|
|
retlen += eo - so;
|
|
|
|
}
|
|
|
|
|
|
|
|
ENSURE(1);
|
|
|
|
ret[retlen] = '\0';
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
#undef ENSURE
|
|
|
|
}
|
|
|
|
|
2018-05-27 11:29:33 +03:00
|
|
|
int proxy_telnet_negotiate (ProxySocket *p, int change)
|
2003-05-06 23:52:31 +04:00
|
|
|
{
|
|
|
|
if (p->state == PROXY_CHANGE_NEW) {
|
|
|
|
char *formatted_cmd;
|
|
|
|
|
|
|
|
formatted_cmd = format_telnet_command(p->remote_addr, p->remote_port,
|
Post-release destabilisation! Completely remove the struct type
'Config' in putty.h, which stores all PuTTY's settings and includes an
arbitrary length limit on every single one of those settings which is
stored in string form. In place of it is 'Conf', an opaque data type
everywhere outside the new file conf.c, which stores a list of (key,
value) pairs in which every key contains an integer identifying a
configuration setting, and for some of those integers the key also
contains extra parts (so that, for instance, CONF_environmt is a
string-to-string mapping). Everywhere that a Config was previously
used, a Conf is now; everywhere there was a Config structure copy,
conf_copy() is called; every lookup, adjustment, load and save
operation on a Config has been rewritten; and there's a mechanism for
serialising a Conf into a binary blob and back for use with Duplicate
Session.
User-visible effects of this change _should_ be minimal, though I
don't doubt I've introduced one or two bugs here and there which will
eventually be found. The _intended_ visible effects of this change are
that all arbitrary limits on configuration strings and lists (e.g.
limit on number of port forwardings) should now disappear; that list
boxes in the configuration will now be displayed in a sorted order
rather than the arbitrary order in which they were added to the list
(since the underlying data structure is now a sorted tree234 rather
than an ad-hoc comma-separated string); and one more specific change,
which is that local and dynamic port forwardings on the same port
number are now mutually exclusive in the configuration (putting 'D' in
the key rather than the value was a mistake in the first place).
One other reorganisation as a result of this is that I've moved all
the dialog.c standard handlers (dlg_stdeditbox_handler and friends)
out into config.c, because I can't really justify calling them generic
any more. When they took a pointer to an arbitrary structure type and
the offset of a field within that structure, they were independent of
whether that structure was a Config or something completely different,
but now they really do expect to talk to a Conf, which can _only_ be
used for PuTTY configuration, so I've renamed them all things like
conf_editbox_handler and moved them out of the nominally independent
dialog-box management module into the PuTTY-specific config.c.
[originally from svn r9214]
2011-07-14 22:52:21 +04:00
|
|
|
p->conf);
|
2003-05-06 23:52:31 +04:00
|
|
|
|
2015-11-22 15:15:52 +03:00
|
|
|
{
|
|
|
|
/*
|
|
|
|
* Re-escape control chars in the command, for logging.
|
|
|
|
*/
|
|
|
|
char *reescaped = snewn(4*strlen(formatted_cmd) + 1, char);
|
|
|
|
const char *in;
|
|
|
|
char *out;
|
|
|
|
char *logmsg;
|
|
|
|
|
|
|
|
for (in = formatted_cmd, out = reescaped; *in; in++) {
|
|
|
|
if (*in == '\n') {
|
|
|
|
*out++ = '\\'; *out++ = 'n';
|
|
|
|
} else if (*in == '\r') {
|
|
|
|
*out++ = '\\'; *out++ = 'r';
|
|
|
|
} else if (*in == '\t') {
|
|
|
|
*out++ = '\\'; *out++ = 't';
|
|
|
|
} else if (*in == '\\') {
|
|
|
|
*out++ = '\\'; *out++ = '\\';
|
|
|
|
} else if ((unsigned)(((unsigned char)*in) - 0x20) <
|
|
|
|
(0x7F-0x20)) {
|
|
|
|
*out++ = *in;
|
|
|
|
} else {
|
|
|
|
out += sprintf(out, "\\x%02X", (unsigned)*in & 0xFF);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
*out = '\0';
|
|
|
|
|
|
|
|
logmsg = dupprintf("Sending Telnet proxy command: %s", reescaped);
|
|
|
|
plug_log(p->plug, 2, NULL, 0, logmsg, 0);
|
|
|
|
sfree(logmsg);
|
|
|
|
sfree(reescaped);
|
|
|
|
}
|
|
|
|
|
2003-05-06 23:52:31 +04:00
|
|
|
sk_write(p->sub_socket, formatted_cmd, strlen(formatted_cmd));
|
|
|
|
sfree(formatted_cmd);
|
|
|
|
|
2002-03-28 00:09:16 +03:00
|
|
|
p->state = 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_CLOSING) {
|
|
|
|
/* if our proxy negotiation process involves closing and opening
|
|
|
|
* new sockets, then we would want to intercept this closing
|
|
|
|
* callback when we were expecting it. if we aren't anticipating
|
|
|
|
* a socket close, then some error must have occurred. we'll
|
|
|
|
* just pass those errors up to the backend.
|
|
|
|
*/
|
2016-06-03 01:03:24 +03:00
|
|
|
plug_closing(p->plug, p->closing_error_msg, p->closing_error_code,
|
|
|
|
p->closing_calling_back);
|
|
|
|
return 0; /* ignored */
|
2002-03-28 00:09:16 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_SENT) {
|
|
|
|
/* some (or all) of what we wrote to the proxy was sent.
|
|
|
|
* we don't do anything new, however, until we receive the
|
|
|
|
* proxy's response. we might want to set a timer so we can
|
|
|
|
* timeout the proxy negotiation after a while...
|
|
|
|
*/
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_ACCEPTING) {
|
|
|
|
/* we should _never_ see this, as we are using our socket to
|
|
|
|
* connect to a proxy, not accepting inbound connections.
|
|
|
|
* what should we do? close the socket with an appropriate
|
|
|
|
* error message?
|
|
|
|
*/
|
2013-11-17 18:03:55 +04:00
|
|
|
return plug_accepting(p->plug,
|
|
|
|
p->accepting_constructor, p->accepting_ctx);
|
2002-03-28 00:09:16 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
if (change == PROXY_CHANGE_RECEIVE) {
|
|
|
|
/* we have received data from the underlying socket, which
|
|
|
|
* we'll need to parse, process, and respond to appropriately.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* we're done */
|
|
|
|
proxy_activate(p);
|
|
|
|
/* proxy activate will have dealt with
|
|
|
|
* whatever is left of the buffer */
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2002-09-24 23:27:58 +04:00
|
|
|
plug_closing(p->plug, "Proxy error: Unexpected proxy error",
|
2002-03-28 00:09:16 +03:00
|
|
|
PROXY_ERROR_UNEXPECTED, 0);
|
2002-04-27 19:01:18 +04:00
|
|
|
return 1;
|
2002-03-23 20:47:21 +03:00
|
|
|
}
|