Replace `subtle` with `ctutils`?
@newpavlov ya está trabajando en esto.
Desde el 27/12/2025.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
I've written a modern replacement for subtle which uses the cmov crate to support constant-time predication instructions (cmov/csel families) via asm!, along with a portable "best effort" fallback similar to what subtle was doing before:
https://github.com/RustCrypto/utils/tree/master/ctutils
It's also an extraction of what we had built in crypto-bigint as a sort of half-baked subtle replacement to work around many issues we were having with subtle, including lack of const fn support, and the inability to support heap-allocated types due to copy bounds. I am in the process of completely switching crypto-bigint over to ctutils (while maintaining optional backwards compatibility with subtle, in part through the subtle interop built into ctutils). Preliminary benchmarking in crypto-bigint has not shown notable performance changes, either.
I've tried making some of these changes upstream to subtle, but it seems somewhat unmaintained at this point, and with an entrenched userbase making breaking changes seems difficult:
- https://github.com/dalek-cryptography/subtle/pull/118
- https://github.com/dalek-cryptography/subtle/pull/136
- https://github.com/dalek-cryptography/subtle/pull/137
ctutils is otherwise mostly an easy drop-in replacement for subtle, and I think we could potentially adopt it in the places we are currently using subtle so as to have a maintained, in-org crate which should theoretically provide better guarantees on most modern platforms. I've just released v0.2.0 and I think it's ready to begin adopting.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 13
- Forks
- 4
- Merge medio
- 41 min
- PR fusionados (30 d)
- 1
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
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de RustCrypto/meta
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
RustCrypto/meta#38 · 5 comentarios ·
-
Proof systemAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
RustCrypto/meta#37 · 3 comentarios ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
RustCrypto/meta#36 · 8 comentarios ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 32/100
RustCrypto/meta#34 · 8 comentarios ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
RustCrypto/meta#28 · 1 comentario ·