keybase / keybase/client

firewall rules - whitelist only

Open
#6,490 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

Which exe's on windows need to be allowed to access the internet. or/and what do hey need access too.

I run white list only and currently have to temporary disable to send/recieve keybase messages or use the KBFS.

thank you in advanced.

new user and loving the concept, trying to get my friends to start using.

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

The issue names no files, tests, or entry points. Start by determining which Windows executables Keybase uses for messaging and KBFS, and which network destinations they require. Done means documenting whitelist rules that let messaging and KBFS work without disabling the firewall.

Written by the indexing model from the issue text.

Assessment

Domain
networking, security
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.