KeyBase and a symlink to BitLocker encrypted volume
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
My Win10 user profile folder (%USERPROFILE%) is symlinked to another partition.
The destination partition is encrypted with microsoft's BitLocker full-volume-encryption feature.
When launched, KeyBase client keeps staying in the "starting up keybase..." screen and won't get to the login screen.
This problem does not occur with the same KeyBase.io user, on the same machine, with a different Win10 user profile where the %USERPROFILE% folder is not symlinked and resides on a non-encrypted volume.
my log id: e2a8f0e097386d4087fc901c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provided log ID e2a8f0e097386d4087fc901c and reproduce the Windows 10 setup using a symlinked %USERPROFILE% on a BitLocker-encrypted partition. Compare it with the working profile configuration; done means Keybase proceeds past the startup screen to the login screen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- desktop, operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100