edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Kevin Carhart <kevin@carhart.net>
Cc: Karl Dahlke <eklhad@comcast.net>, Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] js command line access
Date: Fri, 25 Sep 2015 23:16:12 +0100	[thread overview]
Message-ID: <20150925221612.GJ2254@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <alpine.LRH.2.03.1509250037470.21964@carhart.net>

[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]

On Fri, Sep 25, 2015 at 12:55:47AM -0700, Kevin Carhart wrote:
> 
> >This is damn clever!
> 
> The idea is actually courtesy of Chris Brannon,
> because we were once emailing briefly about this thing
> called MozRepl.  I took it from there and found
> bits of javascript on that idea.  So thank you Chris!

Definitely, sounds seriously cool, I'm thinking in particular about when I
start playing with js engines etc, not to mention all the times when I wish for
an equivalent to the various developer consoles in other browsers.

> I know there are security issues, and you should
> not allow arbitrary strings to get run as code.

In this case I don't really see the security argument.
The user is typing in the js, so it's only as insecure as... say...
a shell or the like. As for the security of the site on the other end of the
connection, plenty of tools already exist (including extensions to the major
popular browsers I think) to mess with js behavior.

> I assumed this feature was too underground to mention,
> or I may have mentioned it sooner.  Grin.

Personally I'd document it. There's nothing worse than an undocumented feature
like this, that's one of the ways things fail to be maintained and security holes happen.
If it's there then not documenting it just means someone has to look at the
code, and if they're looking for exploits they'll do that anyway.

> We could use my code for this, but the output
> has not been edbrowzised or carved into lines.
> I don't bring it back into an edbrowse buffer.
> So the output could be a pain in the butt at
> the moment, but I could give you what I have
> and you could optimize it.
> It also depends on what you echo.

Fair enough, I say put it in and we'll run with it from there.

> Glad we might do this - it has certainly been
> invaluable for me,

Indeed. It also gives me some interesting ideas re:
using Edbrowse for page automation.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-09-25 22:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25  7:25 Karl Dahlke
2015-09-25  7:55 ` Kevin Carhart
2015-09-25 22:16   ` Adam Thompson [this message]
2015-09-25 23:11     ` Kevin Carhart

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=20150925221612.GJ2254@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    --cc=kevin@carhart.net \
    /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 NNTP newsgroup(s).