kornelski/rust-security-framework

Cipher configuration test fails on iOS

Open

#10 opened on Jul 16, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (102 forks)github user discovery
help wanted

Repository metrics

Stars
 (304 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

    thread 'secure_transport::test::cipher_configuration' panicked at 'assertion failed: `(left == right)` (left: `[TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256]`, right: `[TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_NULL_WITH_NULL_NULL, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_NULL_WITH_NULL_NULL, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_NULL_WITH_NULL_NULL, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_NULL_WITH_NULL_NULL]`)', security-framework/src/secure_transport.rs:1120
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Contributor guide

Research direction
Investigate the cipher configuration test failure on iOS. Compare expected cipher suites with actual available suites on iOS, possibly due to platform specific restrictions or security policies. Check the security framework source for conditional compilation or feature flags.
Tech stack
rust
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50