Windows - Running cmd as administrator doesn't allow access to K:\ about kbfs HOT 8 OPEN

We block other users from accessing the drive by design.

This is also true with fuse typically on *nix.

from kbfs.

Although I guess the SID checking could be extended in theory for this...

from kbfs.

That makes sense. I'll leave the SID checking to your discretion. Maybe an informative message somewhere to advise that you're running as Administrator?

from kbfs.

I am unable to access the kbfs folder using the shell at all in any capacity. When I type cs k: it outputs k:\ and redirects me back to the folder I started in. I can't access it as an administrator or as a user, even if I am the user who made the keybase installation. I have a 10 GiB partition on my computer I can't do anything with at all.

from kbfs.

@averagejoey2000

Can you try to access with cmd as the same user that keybase is run as, and do a keybase log send and attach the log id here.

from kbfs.

Update: I can execute mv secret.txt to k:/private/averagejoey2000 and I can
also notepad k:/public/chris/plan.txt

On Oct 24, 2016 6:37 AM, "Joseph Simone" [email protected] wrote:

I can't run these commands from the keybase shell as root or as
averagejoey2000@keybase. I can move files in an out of the directory, but
I cannot force the cmd or keybase shell to stay in k:/

On Oct 24, 2016 1:38 AM, "Taru Karttunen" [email protected]
wrote:

@averagejoey2000 https://github.com/averagejoey2000

Can you try to access with cmd as the same user that keybase is run as,
and do a keybase log send and attach the log id here.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#353 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHKJE5VcE0dWePUvYfYi-i7wZulCh51wks5q3G5tgaJpZM4J9uP4
.

from kbfs.

I can't run these commands from the keybase shell as root or as
averagejoey2000@keybase. I can move files in an out of the directory, but I
cannot force the cmd or keybase shell to stay in k:/

On Oct 24, 2016 1:38 AM, "Taru Karttunen" [email protected] wrote:

@averagejoey2000 https://github.com/averagejoey2000

Can you try to access with cmd as the same user that keybase is run as,
and do a keybase log send and attach the log id here.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#353 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHKJE5VcE0dWePUvYfYi-i7wZulCh51wks5q3G5tgaJpZM4J9uP4
.

from kbfs.

I have the same issue, but work around it by using one window as a regular user and one as an administrator (using cmder). It would probably be preferable that if I ran keybase as an administrator then the kbfs drive would be accessible in the administrator context as well or in both admin and regular user contexts. Or maybe when running kbfsmount it would mount in the current context...

from kbfs.