cryptomator / cryptomator/android

Using custom CA certificates

Abierto
#653 0 comentarios 0 reacciones 0 asignados Ver en GitHub
type:feature-request
Lenguaje dominante
Kotlin
Estrellas
1.2k
Forks
216
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Please agree to the following

- [x] I have searched [existing issues](https://github.com/cryptomator/android/issues?q=) for duplicates
- [x] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/android/blob/develop/.github/CODE_OF_CONDUCT.md)

### Summary

Implementing the ability to use custom CA certificates for webdav

### Motivation

When I connect to my server over webdav-https, I am asked if I trust the certificate. I do in my case and normally the root CA, which is my custom certificate, is already stored in the android certificate manager. Thus, it seems what is missing is a way to automatically compare TLS certificates against custom root certificates.

This can for example be done by somehow accessing the system CA certificates or by for example importing a CA file when setting up a webdav connection.

### Considered Alternatives

_No response_

### Anything else?

_No response_

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Start with the WebDAV-HTTPS connection setup and Android certificate manager behavior described in the issue. Compare using system CA certificates with importing a CA file, then define the supported configuration and verify that a WebDAV connection using a trusted custom root certificate succeeds without an unwanted certificate prompt.

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

Evaluación

Stack tecnológico
android, kotlin
Área
security
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Tranquilo
Claridad
Necesita aclaración
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.