user_j are users that have access to a windows account in the same installation, owners of the
J: drives respectively.
user_j started a session and left his account locked (the seadrive process started by this user is still active, but due to user isolation, only the owner is allowed to talk to it), meanwhile
user_v logged in and was able to reach
user_j's drive, and basically impersonate
user_j as far as the server is concerned.
I thought that issues like these were resolved before allowing users to select a drive letter.
SeaDrive version: 0.9.0