You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
I do agree that RESH shouldn't mix the history of all users together.
You should be able to get separate histories by running RESH multiple times on the same machine.
And you should use different ports in RESH config for each user:
Hi @curusarn,
Certainly starting separate daemons with different ports is a solution to confusion.
However, I think being able to connect to another user's daemon is a security issue.
An unaware (or malicious) user starts RESH with the default setting and will read/[write] the other user's history.
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 runrawinstall
. 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.
The text was updated successfully, but these errors were encountered: