ChocolateLoverRaj/pam-any

Investigate and document thread safety requirements

Open

#3 opened on Mar 18, 2024

View on GitHub
 (3 comments) (1 reaction) (1 assignee)Rust (4 forks)auto 404
help wanted

Repository metrics

Stars
 (34 stars)
PR merge metrics
 (PR metrics pending)

Description

According to pam(3)

The libpam interfaces are only thread-safe if each thread within the multithreaded application uses its own PAM handle.

Looks to me like the current implementation either is unsound due to violating libpam thread-safety requirements or relies on some internal libpam implementation details for soundness.

Contributor guide

Research direction
Review the current implementation for potential thread safety violations by examining how PAM handles are used across threads. Check if each thread uses its own handle or if global state is shared unsafely. Document findings and propose fixes.
Tech stack
rust
Domain
securityauthentication
Issue type
Research
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustThread safety
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30