From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Documenting (system repl server)
Date: Wed, 27 Mar 2013 22:35:32 +0100 [thread overview]
Message-ID: <87boa4h6fv.fsf@pobox.com> (raw)
In-Reply-To: <871ub0r1km.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 27 Mar 2013 22:10:33 +0100")
On Wed 27 Mar 2013 22:10, ludo@gnu.org (Ludovic Courtès) writes:
> Thanks for working on this!
Indeed.
Incidentally I think it would be a good idea to default to using named
pipes. Not sure we can change that in 2.0, but having a locally open
TCP port to a shell is a security risk if you run a web browser on that
same machine:
http://wingolog.org/archives/2013/02/04/knocking-on-private-back-doors-with-the-web-browser
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-03-27 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 19:01 Documenting (system repl server) Ian Price
2013-03-27 21:10 ` Ludovic Courtès
2013-03-27 21:35 ` Andy Wingo [this message]
2013-03-28 0:32 ` Ian Price
2013-03-28 0:24 ` Ian Price
2013-03-28 16:51 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87boa4h6fv.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).