keybase / keybase/client

Access denied, keybase shell, fresh install, windows 10 (domain admin)

Open
#6,502 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Fresh install of Keybase this afternoon.

Windows 10 Pro.

Domain admin account.

Getting access denied:

C:\Users\gellenburg\AppData\Local\Keybase>keybase sign

  • ERROR Access is denied.

C:\Users\gellenburg\AppData\Local\Keybase>keybase status

  • ERROR Access is denied.

C:\Users\gellenburg\AppData\Local\Keybase>keybase login

  • ERROR Access is denied.

C:\Users\gellenburg\AppData\Local\Keybase>keybase log
NAME:
keybase log - Manage keybase logs

USAGE:
keybase log [arguments...]

COMMANDS:
send Send recent debug logs to keybase
help, h Shows a list of commands or help for one command

C:\Users\gellenburg\AppData\Local\Keybase>keybase log send
This command will send recent keybase log entries to keybase.io
for debugging purposes only.

These logs don’t include your private keys or encrypted data,
but they will include filenames and other metadata keybase normally
can’t read, for debugging purposes.

Continue sending logs to keybase.io? (type 'YES' to confirm): yes

  • INFO ignoring error getting keybase status: Access is denied.
  • INFO ignoring UI logs: Access is denied.

Success! Your log ID is:

e0a9f6abe335772f2a6b2d1c

Here's a URL to submit new bug reports containing this ID:

https://github.com/keybase/client/issues/new?body=[write%20something%20useful%20and%20descriptive%20here]%0A%0Amy%20log%20id:%20e0a9f6abe335772f2a6b2d1c

Thanks!

C:\Users\gellenburg\AppData\Local\Keybase>

my log id: e0a9f6abe335772f2a6b2d1c

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported keybase sign, status, login, and log commands on a fresh Windows 10 installation using the conditions in the report. Review the submitted log ID and determine where the Access is denied result occurs; done means the affected commands work without that error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.