From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Add login to remote protocol
Date: Sat, 10 Apr 2010 07:10:00 -0000 [thread overview]
Message-ID: <83bpdrzsu0.fsf@gnu.org> (raw)
In-Reply-To: <4BBFA9E1.1020609@codesourcery.com>
> Date: Fri, 09 Apr 2010 15:27:45 -0700
> From: Stan Shebs <stan@codesourcery.com>
>
> + @item set remote username @var{username}
> + @itemx show remote username
> + Set the username to be sent to targets that require a login. The
> + username is an arbitary string.
> +
> + @item set remote password @var{password}
> + @itemx show remote password
> + Set the password to be sent to targets that require a login. The
> + password is an arbitary string. At present it is stored as cleartext.
> +
Two comments:
. This needs @cindex entries for "remote username" and "remote
password".
. Wouldn't it be better to have just one command for both?
A related question: once a non-empty password was specified, how to
reset it back to empty?
> + If the target requires a login (@samp{MustAuth} feature),
> + then if this packet is not supplied soon after connection, then the
> + target may choose to return errors to all subsequent packets and/or
> + disconnect.
Too many "then"s. I would simply remove the second one.
> + @value{GDBN} must send an authorization packet @samp{qAuth} and the
> + username/password pair must be accepted, otherwise the target will
> + return an error and refuse to continue with the session. ^^^^
Probably "may" instead of "will" is more appropriate, since we don't
actually know what the target does without the credentials.
> + remote_username = xstrdup ("");
> + add_setshow_string_noescape_cmd ("username", class_files,
> + &remote_username, _("\
> + Set the remote username"), _("\
> + Show the remote username"), NULL, NULL, NULL,
> + &remote_set_cmdlist, &remote_show_cmdlist);
> +
> + remote_password = xstrdup ("");
> + add_setshow_string_noescape_cmd ("password", class_files,
> + &remote_password, _("\
> + Set the remote password"), _("\
> + Show the remote password"), NULL, NULL, NULL,
> + &remote_set_cmdlist, &remote_show_cmdlist);
> +
Please consider adding some explanatory text to the doc strings.
Also, we will need a NEWS entry for this new feature.
next prev parent reply other threads:[~2010-04-10 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 22:27 Stan Shebs
2010-04-10 7:10 ` Eli Zaretskii [this message]
2010-04-10 8:52 ` Mark Kettenis
2010-04-27 3:15 ` Hui Zhu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bpdrzsu0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox