[Auth] Certificates and devices
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 20/100
- issue の種類
- 機能追加
- 明瞭さ
- 説明が足りない
- 活発さ
- 停滞
調査の方向性
Read the authentication discussion in the linked May 17, 2018 meeting notes and compare the certificate, device identity, and passcode exchange ideas with the Wi-Fi Alliance Device Provisioning Protocol reference. The issue raises several possible approaches but does not identify a specific change or completion criteria, so first establish which proposal the project wants to pursue.
索引モデルが issue の本文から書いたものです。
説明
These comments relate to the authentication discussion of the open screen protocol. In particular I wanted to comment on the devices and their certificate discussion from the last F2F meeting.
There is a discussion in the meeting notes:
an area for exploration, with hardware backed certificates, show device number as trusted information in the UI. we could eventually find a way for trusted manufacturer public keys to incorporated
… another idea that could be explored is generating new certificates when changing the friendly name of the device. it's about the integrity of the information we display to the user
Although the device number from a trusted device is a truth, anybody can produce a cert with any ID as the subject (if there is no root CA then there is no trusted assertion of the key-to-ID binding). If an attacker persuades the client to trust the bogus cert - because the subject matches the known ID of the receiver in the same room, the controller will authenticate with unknown receivers. IDs cannot be proxies for public keys. Perhaps receivers need to have their public keys stamping on the front?
If there is a trusted common root CA and device specific certificate, then TLS almost wins anyway. Authentication of the specific physical device just needs a quick visual test through the channel before any confidential data. (I suppose the equivalent step in SSL is the check that the DNS domain matches the certificate subject)
is there a way for a controller and receiver to agree on the mechanism to use for passcode exchange (e.g, QR code, NFC, or other mechanisms)?
… it could enable the receiver to choose which UI to present
This looks a bit like the Wi-fi alliance device provisioning protocol 1.0 which seems to enable all of these. See https://www.wi-fi.org/discover-wi-fi/specifications
- 主要言語
- Bikeshed
- スター
- 115
- フォーク
- 21
- 平均マージ
- 5時間 2分
- マージ済み PR（30日）
- 2
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
w3c/openscreenprotocol のほかの issue
-
難易度 5/5 1週間以上 初心者へのやさしさ 18/100
w3c/openscreenprotocol#380 ·
-
osp-application
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
w3c/openscreenprotocol#377 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 38/100
w3c/openscreenprotocol#376 ·
-
osp-application
難易度 2/5 1〜3時間 初心者へのやさしさ 55/100
w3c/openscreenprotocol#375 ·
-
osp-application question
難易度 5/5 1週間以上 初心者へのやさしさ 30/100
w3c/openscreenprotocol#374 ·
w3c/openscreenprotocol の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
google/osv-scalibr#2586 ·
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
devswha/herdr-web-ui#2884 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 79/100
メンテナーはふだん 1 日以内に返信
-
area:fs type:fix
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
Tripstack-Corp/spyc#1002 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100