Skip to content

Accessing history in multiuser environment #194

Open
@gitqlt

Description

@gitqlt

By default, the .history files have strict access permissions (usually -rw-------) so that only the creator user has access to them.

With RESH, running rawinstall as a normal user starts a resh daemon owned by that user. Then the root user can also run rawinstall. After that, only a single resh daemon (owned by the normal user) will be running.

At this point, both are free to write and browse the RESH history, and even the normal user can see the root user's commands. The commands executed by the two users appear mixed up. Moreover, displaying the ~ (home directory) is ambiguous because the /root directory and the /home/<user> directory both appear as ~.
When a third, ordinary user also starts RESH, that user will also view the command history of the first two.

RESH should keep the history private and not shuffle the search result.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions