Ideally, our command:pass event should receive the candidate username of the previous command:user event, so you can decide whether they are admin, and can set an admin flag in a per-connection namespace provided for such purposes. Then, later, in command:dele and command:rmd event handlers, you could check whether the admin flag is set for that connection, and throw an error if not.

Unfortunately, we currently seem to provide none of those features. :-(

Thus, the current approach would probably be to:

For each incoming connection, install a connection-specific pair of event handlers for command:user and command:pass, with a connection-specific shared variable to track the username.
In the command:pass event, after verifying the password, check the username for whether they're admin. If not, give a custom Filesystem Abstraction object that will always deny rmdir and unlink.

The code for the latter could look something like this:

function alwaysDeny() { throw …/* fake an access denied FS error */; }

const limitedFs = Object.assign(Object.create(actualFs), {
  unlink: alwaysDeny,
  rmdir: alwaysDeny,
});

There's probably a lot of journey ahead of you, but I hope this helps you at least have an initial direction.

Uh oh!

permissions #152

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions