keybase / keybase/keybase-issues

Device naming scheme

Open
#2,231 9 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 want a summary of how to name devices with Keybase. How will the names be used?

What's the idea when a device is lost or compromised?

I'd like to be informed about not only the technical reason it has to be this way, but how to work with it.

People may have different setups including several similar devices. Can we develop a generic naming scheme?

`--` or `-`?
First laptop: `Laptop-1-1`. After first recreation (lost/compromised/...): `Laptop-1-2`.
Third phone fourth iteration: `Phone-3-4`.
I imagine many people have a `Laptop-Work`. Third work laptop first iteration: `Laptop-Work-3-1`.
I call my laptop `HipAir` (which I initially used and then reset my Keybase account). `HipAir-2` would conceivably be the next name I'd use following that convention.

I guess we could omit the identifying `-1` on the first iteration, but will likely need a number eventually and consistency is often useful.

> we want people to be able to think of devices by name - say, when seeing them in a list, or when talking about them - and never have to think about key fingerprints or id's.

How compatible can a naming scheme be with that?

Loss and compromise shouldn't be more of a hassle than it already is. People shouldn't be discouraged to discontinue use of a compromised key for the sole purpose of keeping a clean device name.

Is there no way we can reuse names such as `Laptop` and `Phone`? Perhaps it's actually impossible, but can the sigchain not be used to track updates of device name to ID mappings? I realise there may be user experience difficulties, but the current situation seems to have issues as well.
## Relevant

Based on discussion from https://github.com/keybase/keybase-issues/issues/1952 “Unable to add previous device name on reset account”.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start with issue #1952 and the questions in this issue; done would be a documented, agreed naming scheme covering resets, loss, compromise, reuse, and multiple similar devices.

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.