<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pam-any.git/src-repo/src/mode.rs, branch main</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>https://git.kobert.dev/pam-any.git/atom/src-repo/src/mode.rs?h=main</id>
<link rel='self' href='https://git.kobert.dev/pam-any.git/atom/src-repo/src/mode.rs?h=main'/>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pam-any.git/'/>
<updated>2026-03-11T13:16:07Z</updated>
<entry>
<title>Port pam-any from pam-bindings to nonstick crate</title>
<updated>2026-03-11T13:16:07Z</updated>
<author>
<name>Dennis Kobert</name>
<email>dennis@kobert.dev</email>
</author>
<published>2026-03-11T13:15:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kobert.dev/pam-any.git/commit/?id=a9a74679fbec07cf158f2295513e3d4c4adc2666'/>
<id>urn:sha1:a9a74679fbec07cf158f2295513e3d4c4adc2666</id>
<content type='text'>
The pam-bindings crate has a critical bug where pam_try! returns
PAM_SUCCESS on error in release builds (anowell/pam-rs#16), causing
authentication to always succeed. This replaces it with nonstick
and a custom pam_client module with raw PAM FFI for thread-safe
conversation forwarding.
</content>
</entry>
</feed>
