F-Droid doesn't trust the Kotlin archive

Open
  • Is something wrong?
#260 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
android, kotlin, rust
Domain
mobile, security

Research direction

The payload names no files or tests. Start with the linked ruffle-android issue #861, which gives the F-Droid context, and the platform verifier's existing Android integration. The open question is whether F-Droid's cloud build can use this dependency or whether CA roots must be bundled, so this needs a maintainer decision before any code. Done means that decision is recorded, and the title's Kotlin reference is checked against this Rust repository.

Written by the indexing model from the issue text.

Description

O-Android

Re: https://github.com/ruffle-rs/ruffle-android/issues/861

Is building on F-Droid's cloud with this dep possible, or should I bundle the CA roots instead?

Dominant language
Rust
Stars
162
Forks
67
Avg merge
5d 14h
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rustls/rustls-platform-verifier

All issues in rustls/rustls-platform-verifier

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.