keybase / keybase/keybase-issues

Use Case For Developers - Storing and Sharing Credentials

Open
#2,792 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

I'm novice and new to keybase, but I have seen a common problem I'm hoping Keybase could potentially solve.

Many integration tests require credentials like connection strings to be used during development on many different developer machines. Some credentials are user-specific, others are shared. Many teams have many methods for sharing these, few of which are ideal, almost none of which are encrypted end to end.

Is it possible to have an effective workflow using Keybase where:
-Each developer has a standard file or location for personal test credentials
-Teams can have a standard file or location for shared test credentials

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue does not identify files, tests, or an implementation entry point. First review the Keybase client’s existing storage and team-sharing capabilities, then define a supported workflow for personal and shared integration-test credentials and document how completion would be verified.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.