This repository was archived by the owner on Oct 11, 2024. It is now read-only.
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1489 +/- ##
==========================================
+ Coverage 67.93% 68.15% +0.22%
==========================================
Files 54 54
Lines 4026 4026
==========================================
+ Hits 2735 2744 +9
+ Misses 891 882 -9
Partials 400 400
Continue to review full report at Codecov.
|
pav-kv
approved these changes
Mar 5, 2020
docs/use-cases.md
Outdated
| Key Transparency ensures, with mathematical certainty, that account owners can | ||
| see all the public keys that have been associated with their account. | ||
|
|
||
| This zero-trust architecture is useful in a variety of scenarios from end-to-end encryption to enterprise account management. |
Contributor
There was a problem hiding this comment.
Is it zero trust, or something a bit weaker? Some sort of "trust but verify" thing?
Just want to make sure we don't promise too much here.
Contributor
Author
There was a problem hiding this comment.
Good point. How's "assured system design"?
docs/use-cases.md
Outdated
|
|
||
|
|
||
| Key Transparency ensures, with mathematical certainty, that account owners can | ||
| see all the public keys that have been associated with their account. |
Contributor
There was a problem hiding this comment.
Would it be worth elaborating a bit on what "associated" means? Like, some other user using my key is included here, right?
Contributor
Author
There was a problem hiding this comment.
How's "see all the public keys that have been used to authenticate their account or send them messages." ?
docs/use-cases.md
Outdated
| |---------------|------------------| | ||
| | Encrypted Messaging | Key Transparency is ideal for user friendly end-to-end encrypted messaging. By making key management analogous to device management, users do not have to learn any new concepts, and no additional UI beyond device management is needed. Key management fits seamlessly into existing account life-cycle flows, and users are protected without requiring them to take additional actions. | | ||
| | PGP Encrypted Email | Key Transparency was initially built to solve the problem of public key lookup for PGP email encryption. KT has the potential to make PGP significantly more usable than the existing web-of-trust model. | | ||
| | Insider Risk | Key Transparency removes the possibility that a system administrator, whether accidentally, on purpose, or via a hack, might add or remove public keys (eg. [U2F Security Keys](https://en.wikipedia.org/wiki/Universal_2nd_Factor)) from a user account without detection. This enables new levels of security in authentication systems. | |
Contributor
There was a problem hiding this comment.
Suggested change
| | Insider Risk | Key Transparency removes the possibility that a system administrator, whether accidentally, on purpose, or via a hack, might add or remove public keys (eg. [U2F Security Keys](https://en.wikipedia.org/wiki/Universal_2nd_Factor)) from a user account without detection. This enables new levels of security in authentication systems. | | |
| | Insider Risk | Key Transparency removes the possibility that a system administrator, whether accidentally, on purpose, or via a hack, adds or removes public keys (eg. [U2F Security Keys](https://en.wikipedia.org/wiki/Universal_2nd_Factor)) from a user account without detection. This enables new levels of security in authentication systems. | |
gdbelvin
added a commit
to gdbelvin/keytransparency
that referenced
this pull request
Mar 25, 2020
* master: (109 commits) Upgrade Prometheus (google#1500) Run `go build ./...` with github action (google#1446) Replace tinkio.ProtoFile with keyset.BinaryReader (google#1492) Bump github.com/golang/mock from 1.4.1 to 1.4.2 Bump github.com/prometheus/client_golang from 1.5.0 to 1.5.1 Bump github.com/golang/protobuf from 1.3.3 to 1.3.5 Bump github.com/google/tink from 1.3.0-rc4 to 1.3.0 New Design Doc (google#1469) Acknowledgements (google#1490) Use cases (google#1489) Bump github.com/prometheus/client_golang from 1.4.1 to 1.5.0 (google#1486) README.md # Related (google#1485) Explain authorized keys (google#1484) Use new prometheus sidecar deployment (google#1483) don't overwrite the ReplicaSet service label (google#1482) Update encrypted creds (google#1481) Pickup DB_HOST env variable (google#1480) Fix credential encryption (google#1479) Use Cloud MySQL in GKE (google#1473) Update client_secrets.json.enc (google#1478) ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.