#pam #linux #wrapper #bindings #safe-wrapper #module


[MOVED TO pam] Safe Rust wrapper for PAM authentification

21 releases

0.6.0 Feb 7, 2019
0.5.5 Jul 4, 2018
0.5.4 Mar 21, 2018
0.5.3 Dec 4, 2017
0.0.5-pre Mar 29, 2015

#379 in Authentication

Download history 68/week @ 2024-02-25 184/week @ 2024-03-31

184 downloads per month
Used in 5 crates (2 directly)



[MOVED TO pam]

pam-auth is deprecated and was renamed to pam. Please use the new crate for any future projects and consider switching if you still use this crate.

pam-auth Version License Build Status

Safe Rust bindings to Linux Pluggable Authentication Modules (PAM). Currently only supports basic username/password authentication.

Documentation @ docs.rs


Environment support through the env module is probably broken and should not be used in the current state!

Supported Rust versions

The library is only continuously built against Rust stable, beta and nightly but as it does not use a lot of new language features it should probably compile on older versions as well. If you encounter problems building on older versions and a small fix can be applied to make the build succeed, consider opening a pull request.

Note about stability

This crate follows semantic versioning. As such all versions below 1.0.0 should be considered development versions. This means the API could change any time.


  1. Add pam-auth to your Cargo.toml:
pam-auth = "0.5.0"
  1. Use the Authenticator struct to authenticate and open a session
extern crate pam_auth;
pub fn main() {
        let service = "<yourapp>";
        let user = "<user>";
        let password = "<pass>";

        let mut auth = pam_auth::Authenticator::new(service).unwrap();
        auth.set_credentials(user, password);
        if auth.authenticate().is_ok() && auth.open_session().is_ok() {
            println!("Successfully opened a session!");
        else {
            println!("Authentication failed =/");


  • Implement basic user/password authentication
  • Add Authenticator struct
  • Add documentation
  • Verify current conv does not leak memory
  • Allow custom conv functions to be passed (in pam-sys?)
  • Code cleanup


Licensed under either of

at your option.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

No runtime deps