2003-03-14 21:35:01 +03:00
|
|
|
/*
|
|
|
|
* uxcfg.c - the Unix-specific parts of the PuTTY configuration
|
|
|
|
* box.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <assert.h>
|
|
|
|
#include <stdlib.h>
|
|
|
|
|
|
|
|
#include "putty.h"
|
|
|
|
#include "dialog.h"
|
|
|
|
#include "storage.h"
|
|
|
|
|
2006-08-29 13:18:09 +04:00
|
|
|
void unix_setup_config_box(struct controlbox *b, int midsession, int protocol)
|
2003-03-14 21:35:01 +03:00
|
|
|
{
|
2005-02-14 10:41:41 +03:00
|
|
|
struct controlset *s;
|
2003-03-14 21:35:01 +03:00
|
|
|
union control *c;
|
|
|
|
|
|
|
|
/*
|
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
|
|
|
* The Conf structure contains two Unix-specific elements which
|
|
|
|
* are not configured in here: stamp_utmp and login_shell. This
|
|
|
|
* is because pterm does not put up a configuration box right at
|
|
|
|
* the start, which is the only time when these elements would
|
|
|
|
* be useful to configure.
|
2003-03-14 21:35:01 +03:00
|
|
|
*/
|
|
|
|
|
2003-04-05 20:12:52 +04:00
|
|
|
/*
|
|
|
|
* On Unix, we don't have a drop-down list for the printer
|
|
|
|
* control.
|
|
|
|
*/
|
|
|
|
s = ctrl_getset(b, "Terminal", "printing", "Remote-controlled printing");
|
|
|
|
assert(s->ncontrols == 1 && s->ctrls[0]->generic.type == CTRL_EDITBOX);
|
|
|
|
s->ctrls[0]->editbox.has_list = 0;
|
|
|
|
|
2003-05-06 23:52:31 +04:00
|
|
|
/*
|
|
|
|
* Unix supports a local-command proxy. This also means we must
|
|
|
|
* adjust the text on the `Telnet command' control.
|
|
|
|
*/
|
2003-05-07 17:14:48 +04:00
|
|
|
if (!midsession) {
|
2003-05-06 23:52:31 +04:00
|
|
|
int i;
|
2003-05-07 17:14:48 +04:00
|
|
|
s = ctrl_getset(b, "Connection/Proxy", "basics", NULL);
|
2003-05-06 23:52:31 +04:00
|
|
|
for (i = 0; i < s->ncontrols; i++) {
|
|
|
|
c = s->ctrls[i];
|
|
|
|
if (c->generic.type == CTRL_RADIO &&
|
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
|
|
|
c->generic.context.i == CONF_proxy_type) {
|
|
|
|
assert(c->generic.handler == conf_radiobutton_handler);
|
2003-05-06 23:52:31 +04:00
|
|
|
c->radio.nbuttons++;
|
|
|
|
c->radio.buttons =
|
|
|
|
sresize(c->radio.buttons, c->radio.nbuttons, char *);
|
|
|
|
c->radio.buttons[c->radio.nbuttons-1] =
|
|
|
|
dupstr("Local");
|
|
|
|
c->radio.buttondata =
|
|
|
|
sresize(c->radio.buttondata, c->radio.nbuttons, intorptr);
|
|
|
|
c->radio.buttondata[c->radio.nbuttons-1] = I(PROXY_CMD);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
2003-05-07 16:07:23 +04:00
|
|
|
|
2003-05-06 23:52:31 +04:00
|
|
|
for (i = 0; i < s->ncontrols; i++) {
|
|
|
|
c = s->ctrls[i];
|
|
|
|
if (c->generic.type == CTRL_EDITBOX &&
|
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
|
|
|
c->generic.context.i == CONF_proxy_telnet_command) {
|
|
|
|
assert(c->generic.handler == conf_editbox_handler);
|
2003-05-06 23:52:31 +04:00
|
|
|
sfree(c->generic.label);
|
|
|
|
c->generic.label = dupstr("Telnet command, or local"
|
|
|
|
" proxy command");
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2006-08-28 18:29:02 +04:00
|
|
|
/*
|
|
|
|
* Serial back end is available on Unix. However, we have to
|
|
|
|
* mask out a couple of the configuration options: mark and
|
|
|
|
* space parity are not conveniently supported, and neither is
|
|
|
|
* DSR/DTR flow control.
|
|
|
|
*/
|
2006-08-29 13:18:09 +04:00
|
|
|
if (!midsession || (protocol == PROT_SERIAL))
|
|
|
|
ser_setup_config_box(b, midsession, 0x07, 0x07);
|
2003-03-14 21:35:01 +03:00
|
|
|
}
|