Mercurial > crates > nonstick

changeset 88:c9fc7e6257d3 default tip

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
This is a v0.0.7 if I ever saw one.
author Paul Fisher <paul@pfish.zone>
date Tue, 10 Jun 2025 05:36:58 -0400
parents 05291b601f0a
children
files Cargo.toml README.md
diffstat 2 files changed, 10 insertions(+), 9 deletions(-) [+]
line wrap: on
line diff
--- a/Cargo.toml	Tue Jun 10 04:40:01 2025 -0400
+++ b/Cargo.toml	Tue Jun 10 05:36:58 2025 -0400
@@ -1,7 +1,7 @@
 [package]
 name = "nonstick"
 description = "PAM bindings for Rust"
-version = "0.0.6"
+version = "0.0.7"
 authors = ["Paul Fisher <paul@pfish.zone>", "Anthony Nowell <anowell@gmail.com>" ]
 repository = "https://hg.pfish.zone/crates/nonstick/"
 readme = "README.md"
--- a/README.md	Tue Jun 10 04:40:01 2025 -0400
+++ b/README.md	Tue Jun 10 05:36:58 2025 -0400
@@ -4,20 +4,21 @@
 
 ## Status
 
-This is currently very incomplete.
-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).
-A very immature implementation of the PAM Conversation structure is gated behind the `experimental` feature.
-At the moment, [Linux-PAM](https://github.com/linux-pam/linux-pam) is the only supported PAM implementation.
+This is currently somewhat incomplete.
+
+It provides fairly robust functionality for developing PAM modules (i.e., backends that PAM calls to authenticate users or do something similar).
+[Linux-PAM](https://github.com/linux-pam/linux-pam) is the only _tested_ PAM implementation, but it compiles against OpenPAM.
 
-*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).
+*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) for now.
 
-APIs are likely to break before v0.1.0, and thereafter should stabilize to an eventual 1.0 release.
+APIs are likely to break before v0.1.0, but thereafter should stabilize to an eventual 1.0 release.
+After v0.1.0, the shape of the API should be mostly formed, and most of what happens will be adding new features.
 
 Goals include:
 
 - Bindings for PAM clients.
-- A robust and mature implementation of Conversation.
-- Support for non–Linux-PAM implementations.
+- Additional PAM features, like environment variables.
+- Way more documentation.
 
 ## Credits