[Auth] Trusted Displays

Abierto
  • ¿Algo no está bien?
#114 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Área
security

Línea de trabajo

Read the linked May 2018 meeting minutes and this issue’s authentication discussion. The payload names no code files, tests, or entry points; first establish whether the protocol has a decided approach to trusted-device identity and compliance. Done would require a clear, agreed scope, which this discussion does not provide.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

osp-network v2

These comments relate to the authentication discussion of the open screen protocol. In particular I wanted to comment on the trusted displays discussion from the last F2F meeting.

Presentation API assumes the device is trusted. device could be compromised or impersonated on the network
… we need to verify the identity before exchanging information”

Agree, a password usually belongs to a user and is pre-shared with the service or is an ephemeral input to a pair of devices. It cannot help in determining whether the device is to be trusted with the presentation (e.g., won’t store and forward), that has to come from the manufacturer?

If the scheme incorporates a transition from PAKE to self-signed certificate it seems important to know that the cert is ‘honest’ and that the receiver isn’t subverting the process by presenting a compromised key. This is hard because if we have a means to certify a device compliance we should have incorporated it into the whole protocol anyway.

Trusted devices have to be certified as compliant by someone (manufacturer?) and somehow be recognised as such on the wire, e.g, have public + private keys and cert - with known root. This is difficult to coordinate. It may be that the device is generally known to be trusted within the LAN by nature of its model/spec and then has to be nominated ‘in the room’ by typing in a password, then authenticated as being ‘that device’ over the network using a PAKE protocol.

I suppose this is just observing that for robust end to end trust the integrity of the device is a critical factor.

Lenguaje dominante
Bikeshed
Estrellas
115
Forks
21
Merge medio
5 h 2 min
PR fusionados (30 d)
2

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de w3c/openscreenprotocol

Todos los issues de w3c/openscreenprotocol

Issues similares

Más issues de Security

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.