Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[TSP] Support TSP-level encryption in private/direct rooms

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

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
rust
Área
authentication, security

Línea de trabajo

No files or tests are named; start with issue #551 and trace the existing TSP signing flow, User Profile Sliding Pane, and message composer. Review how two-person rooms, TSP verification, DID association, Matrix message types, and confirmation modals are currently handled. Done means private/direct rooms can send TSP-encrypted messages only to a verified recipient, with signing enabled and an explicit warning.

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

Descripción

tsp

This is the form of "double encryption" that our original TSP support issue (#551) referred to:

  1. Offer a full additional layer of encryption (using TSP text mode) such that even in an encrypted Matrix room, nobody can read your messages even if they hack into your Matrix account and are able to verify it to enable Matrix-level encryption.
    • Additional feature: private messages within a public room. This is a bad idea, as sending un-decryptable messages in a public room would irritate users. This should only be available in private, direct rooms.
    • Implementation idea: use either MessageType::Text with a custom MessageFormat, or a custom MessageType entirely for TSP-encrypted messages.

Implementation Notes

  • We need to add another checkbox (or perhaps a dropdown or multi-state selector widget) that allows the user to enable/disable TSP
    • TSP-encrypting a message should automatically check/enable the TSP-sign checkbox too, since TSP encryption is a superset of signing.
  • A TSP-encrypted message must have a specific intended receiver, so we need a way to allow the user to select a specific user.
    • Initially, this will only be available in rooms where there are two people, so that shouldn't be needed since the other user will implicitly be the recipient.
    • It must also only be available when the other user in the room has been verified using TSP and their TSP DID has been associated with their Matrix User ID, which is obvious when looking at the User Profile Sliding Pane for their user.
  • When sending a TSP-encrypted message, we need to show a positive confirmation modal to confirm that the user actually wants to send a TSP-encrypted message.
    • Something like "Warning: sending a TSP-encrypted message can only be decrypted and read by the single target recipient, and only if they have the original TSP wallet with your verified identity in it."
Lenguaje dominante
Rust
Estrellas
489
Forks
71
Merge medio
1 h 27 min
PR fusionados (30 d)
72

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 project-robius/robrix

Todos los issues de project-robius/robrix

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.