Mercurial > crates > nonstick

comparison README.md @ 57:2a5c83d04b93 v0.0.4

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Update some docs; bump to v0.0.4.
author Paul Fisher <paul@pfish.zone>
date Mon, 05 May 2025 00:16:00 -0400
parents ce47901aab7a
children d83623951070
comparison
equal deleted inserted replaced
56:daa2cde64601 57:2a5c83d04b93
4 4
5 ## Status 5 ## Status
6 6
7 It is currently very incomplete. 7 It is currently very incomplete.
8 It only provides functionality for developing your own PAM authentication module (i.e., a backend that PAM calls to authenticate a user or do something similar). 8 It only provides functionality for developing your own PAM authentication module (i.e., a backend that PAM calls to authenticate a user or do something similar).
9 If you’re looking for a library to implement a PAM client (i.e., something that authenticates using PAM), consider the [`pam` crate](https://crates.io/crates/pam).
9 At the moment, [Linux-PAM](https://github.com/linux-pam/linux-pam) is the only supported PAM implementation. 10 At the moment, [Linux-PAM](https://github.com/linux-pam/linux-pam) is the only supported PAM implementation.
10 11
11 I will make an effort not to break APIs with development, but consider it alpha, pre-1.0 software. 12 An earlier version of this suggested that I would try not to break APIs.
12 While the code itself should be _secure_ and mostly safe, the API may not be completely stable. 13 This was optimistic on my part; it is likely APIs will break before v0.1.0, after which I _will_ try to break things _less_.
13 14
14 Goals include: 15 Goals include:
15 16
16 - Bindings for PAM clients. 17 - Bindings for PAM clients.
17 - Support for non–Linux-PAM implementations. 18 - Support for non–Linux-PAM implementations.