Skip to content

web app access - via remote vault #24

@bsutton

Description

@bsutton

We originally had this idea of a web app randomly accessing files in vault but with the decryption happening in the browser.

This doesn't currently work as the page cache decrypts pages before they are available at a higher level.

is it practical to put an adaptor between the main api and the page cache. The adaptor would allow network calls to happen between
the api and the cache with the default adapter being a no op with calls going directly to the page cache.

This would allow the web code and the local code to be identically except for the adaptor.

The adaptor would need to tell the cache not to decrypt the pages and the adaptor on the web side would decrypt the pages as they arrive.
The web side might then want its own page cache.

Or do we just treat the file as a byte stream and its the read/writes which are done across the network with all code shared.

So the page cache would run in the browser and just use a generic web server to pull back chunks of the lock box as required.

  • this does feel better and means we don't need a specialised web server.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions