From: Hui Zhu <teawater@gmail.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>,
Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Add login to remote protocol
Date: Tue, 27 Apr 2010 03:15:00 -0000 [thread overview]
Message-ID: <h2sdaef60381004262014x467c8b4du65c28ac9eae09730@mail.gmail.com> (raw)
In-Reply-To: <201004100850.o3A8oAq8009927@glazunov.sibelius.xs4all.nl>
On Sat, Apr 10, 2010 at 16:50, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>> Date: Fri, 09 Apr 2010 15:27:45 -0700
>> From: Stan Shebs <stan@codesourcery.com>
>>
>> This patch is somewhat more specialized than the tracepoint stuff, but
>> may be of wider interest, so we offer it for your consideration. It
>> adds a login capability to the remote protocol; the user sets a username
>> and password in GDB, then upon connection to a target that requires
>> them, GDB supplies the two. It is completely up to the target what do
>> with them, for instance it could simply close the connection in response
>> to a bad login.
>>
>> The design is simple, and not especially secure, as the password is sent
>> in the clear - it's mostly appropriate for direct connections or secured
>> intranets. We don't do anything to conceal the password from the
>> console, but one could add a non-echoing reader, and write a password
>> show that kept it concealed.
>
> Sorry, but I think that an authentication protocol that sends
> passwords in cleartext is worse than no authentication at all.
>
Maybe we can do md5 for password or something like it in client and
server. It will simple like before, we just need add a encode
function.
Regards,
Hui
prev parent reply other threads:[~2010-04-27 3:15 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
2010-04-10 8:52 ` Mark Kettenis
2010-04-27 3:15 ` Hui Zhu [this message]
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=h2sdaef60381004262014x467c8b4du65c28ac9eae09730@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--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