Android: Panics with unhelpful message when used in Termux
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 43/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- rust
- Domain
- mobile-dev, security
Research direction
Start by inspecting the Android verifier path associated with rustls-platform-verifier/src/android.rs:90:10 and reproduce the standalone aarch64-linux-android binary from a Termux shell. Determine how the initialization failure is surfaced; done means the Termux case no longer ends with an unhelpful panic message.
Written by the indexing model from the issue text.
Description
I compiled for aarch64-linux-android and run as a standalone bnary directly from a Termux shell and got these panics
thread 'main' (25165) panicked at /Users/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/rustls-platform-verifier-0.7.0/src/android.rs:90:10:
Expect rustls-platform-verifier to be initialized
stack backtrace:
0: 0x740830e2fc - <unknown>
1: 0x74081a8ed4 - <unknown>
2: 0x740830d1fc - <unknown>
3: 0x740830cf64 - <unknown>
4: 0x740832e11c - <unknown>
5: 0x740832e0d8 - <unknown>
6: 0x740832e59c - <unknown>
7: 0x74081a8e74 - <unknown>
8: 0x74081ad9c0 - <unknown>
9: 0x7408305dec - <unknown>
10: 0x7408305170 - <unknown>
11: 0x74082f1920 - <unknown>
12: 0x7408247d90 - <unknown>
13: 0x740824b534 - <unknown>
14: 0x740824d294 - <unknown>
15: 0x7408244510 - <unknown>
16: 0x7408251650 - <unknown>
17: 0x740826aa6c - <unknown>
18: 0x74082601cc - <unknown>
19: 0x740825e064 - <unknown>
20: 0x7408298404 - <unknown>
21: 0x74082970b0 - <unknown>
22: 0x740814475c - <unknown>
23: 0x740814af80 - <unknown>
24: 0x740815c228 - <unknown>
25: 0x7408128a78 - <unknown>
26: 0x740816b3a0 - <unknown>
27: 0x7407cab94c - __libc_init
Aborted```
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rustls/rustls-platform-verifier
-
O-Android
Difficulty 5/5 Over a week Newbie friendliness 12/100
rustls/rustls-platform-verifier#260 · 4 comments ·
-
`CertificateVerifier.verifyCertificateChain` on Android can cause `NetworkOnMainThreadException`May be free again A pull request for this issue was closed without being merged. Openbug O-Android
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rustls/rustls-platform-verifier#256 · 5 comments ·
-
Windows: revocation check blocks up to 10s with no effect on verification outcomePossibly taken @djc claimed this 129 days ago. OpenO-Windows
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
rustls/rustls-platform-verifier#230 · 2 comments ·
-
O-Android
Difficulty 3/5 1-2 days Newbie friendliness 45/100
rustls/rustls-platform-verifier#228 · 3 comments ·
All issues in rustls/rustls-platform-verifier
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Eyevinn/open-live-ingest#36 · 1 comment ·
Maintainers usually reply within 1 day
-
app
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug bug jury peripheral:i2s
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
esp-rs/esp-hal#6828 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
ライブラリを追加Openpriority middle
Difficulty 1/5 Under an hour Newbie friendliness 62/100
KATO-Hiro/AtCoderClans#13015 ·
Maintainers usually reply within 1 day