Giter VIP home page Giter VIP logo

footlights's People

Contributors

trombonehero avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar

Forkers

mounirnasrallah

footlights's Issues

Easy startup

Users need to be able to start Footlights without a whole lot of messing about: visit a web page, authorise a JNLP and then don't think about it any more.

This means that we need persistence (e.g. "run on login") and some kind of detection that "we are already running, don't try to start up again".

Placeholders

Plugins need to be able to express something like "please create a DOM text node with the value ${user.name}".

Need async JVM -> UI channel

We really need a channel that the JVM side of things can use to send asynchronous events to the UI.

This shouldn't be very hard to implement.

Persistent state for plugins

Plugins ought to have some persistent state that they can use to bootstrap themselves.

This will probably take the form of a Map<String,String>, since other data can be stored in encrypted FIle objects, and plugins ought to be able to open explicitly crypto-named files.

Sandboxed JS can modify its sandbox's name

Within a sandbox, context.name = 'HACKED' succeeds. Since the context's name is used to drive Ajax, malicious JavaScript could send requests to other sandboxes' servers, or even the root context.

Event handlers can access naked DOM object

Currently, a sandbox can create event handlers like:

proxiedImage.onmouseover = function()
{
    this.parentNode.[...];
};

and this will refer to the naked DOM image rather than the proxied image.

Need async JVM -> UI channel

We really need a channel that the JVM side of things can use to send asynchronous events to the UI.

This shouldn't be very hard to implement.

Multi-user strategy

How will multiple Footlights users co-exist on a machine?

The most natural way (which aligns best with existing security mechanisms such as DAC) is for each user to run her own Footlights instance. If we do this, however, we need a way for each user to connect to her local instance: should the port number be a hash of the username, for example?

This also requires a login mechanism (which could involve cookies in the browser) to prevent casual use by others on the same machine.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.