Taru Karttunen
Taru Karttunen
@stemid, There is support for changing the mountpoint to an another drive letter. Using non-drive letter mountpoints can unravel an unfortunate amount of bugs with various software and e.g. path...
Seems like the following: 1) Kaspersky tries to access KBFS as an another user than the one running KBFS 2) Kaspersky is denied access 3) goto 1. In a busy...
This should be fixed by https://github.com/keybase/kbfs/pull/1016 but that is not yet in a release. You can remove Dokan via control panel, then the drive dissapears. We could fake a larger...
We block other users from accessing the drive by design. This is also true with fuse typically on *nix.
Although I guess the SID checking could be extended in theory for this...
@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.
Allowing files that won't work with common applications could lead to problems. Especially in shared folders with multiple people. @barcelona-messi what kind of use-cases do you have? E.g. for maildirs...
Suspect conflicting drivers causing K: to be hidden, even though the mount was succesfull. @Tenrys are you running any AV/backup/filesystem software that could be causing conflicts?
If you touch/try to open `K:\.kbfs_unmount` kbfsdokan will exit. Of course the service can restart it after an exit.
@ledur, we disable access for other accounts than the one running kbfsdokan. Creating symbolic links from cmd.exe works as you have discovered. Pondering on what would be the best way...