> ## Content Index
> Fetch the complete content index at: https://johnwlittle.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Covert Contact 69: Securing Data, Communications, and Identity with Keybase
- URL: https://johnwlittle.com/securing-data-communications-and-identity-with-keybase/
- Published: 2017-06-08T12:25:24.000Z
- Updated: 2026-10-17T16:25:11.000Z
- Description: Keybase co-founder Max Krohn discusses cryptographic identity, simpler key management, secure collaboration, and authenticating published material in this June 2017 conversation.
- Author: John Little
- Tags: Covert Contact, Interviews, Technology, Security, Crypto

In this June 2017 conversation, [Keybase](https://keybase.io/?ref=johnwlittle.com) co-founder [Max Krohn](https://keybase.io/max?ref=johnwlittle.com) joins me to discuss making encryption easier to use and connecting online identities to cryptographic keys. I had [used Keybase](https://keybase.io/johnwlittle?ref=johnwlittle.com) and followed its development from an identity directory into a service offering [encrypted chat](https://keybase.io/blog/keybase-chat?ref=johnwlittle.com), file sharing, and [applications across multiple platforms](https://keybase.io/download?ref=johnwlittle.com).

Max explains the idea behind linking accounts people already recognize, such as Twitter and GitHub handles, to a cryptographic identity. The aim is to help people check whom they are communicating with before exchanging private information. We also discuss the practical difficulty of managing keys across devices and Keybase's move away from its early password-based approach toward device-held secret keys.

The conversation explores a broader use for this infrastructure: verifying the source of published material. Using the [reported Qatar News Agency hack](http://www.zdnet.com/article/it-was-easy-to-cause-the-qatar-diplomatic-crisis/?ref=johnwlittle.com#ftag=YHFb1d24ec?yptr=yahoo) as a starting point, we consider how digital signatures could help authenticate articles, software, and other communications. Max emphasizes an important limitation: a compromised device can still allow an attacker to impersonate its owner.

We also look at the deliberate pace of development, open-source scrutiny, mobile applications, and plans for richer team collaboration. Max describes the challenge of building a durable record of identity and device changes while keeping the experience understandable to people who do not want to manage cryptographic details themselves.

We close with the tension between privacy and the needs of law enforcement and intelligence agencies. Max argues for protecting ordinary users against data theft and impersonation, while acknowledging that encryption does not solve the problem of access to a compromised endpoint.

This episode was originally released on June 8, 2017\. Product features, development plans, and security assessments reflect the discussion at that time.