view Cargo.toml @ 141:a508a69c068a

Remove a lot of Results from functions. Many functions are documented to only return failing Results when given improper inputs or when there is a memory allocation failure (which can be verified by looking at the source). In cases where we know our input is correct, we don't need to check for memory allocation errors for the same reason that Rust doesn't do so when you, e.g., create a new Vec.
author Paul Fisher <paul@pfish.zone>
date Sat, 05 Jul 2025 17:16:56 -0400
parents efbc235f01d3
children 4b3a5095f68c
line wrap: on
line source

[workspace]
members = ["testharness"]
exclude = ["libpam-sys"]

[workspace.package]
license = "MIT"
version = "0.0.8-alpha0"
authors = ["Paul Fisher <paul@pfish.zone>"]
edition = "2021"
rust-version = "1.75.0"

[package]
name = "nonstick"
description = "PAM bindings for Rust"
readme = "README.md"
keywords = ["pam", "ffi", "linux", "authentication"]
license.workspace = true
version.workspace = true
authors.workspace = true
edition.workspace = true
rust-version.workspace = true

[features]
default = ["link", "basic-ext"]

# Enable this to actually link against your system's PAM library.
#
# This will fail if you have extensions enabled that are not compatible
# with your system's PAM.
link = ["libpam-sys"]

basic-ext = []
linux-pam-ext = []
openpam-ext = []
sun-ext = []

# This feature exists only for testing.
test-install = []

[dependencies]
bitflags = "2.9.0"
libc = "0.2"
memoffset = "0.9.1"
num_enum = "0.7.3"
libpam-sys = { optional = true, path = "libpam-sys" }
libpam-sys-helpers = { path = "libpam-sys/libpam-sys-helpers" }

[build-dependencies]
libpam-sys-helpers = { path = "libpam-sys/libpam-sys-helpers" }