NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io · #2855 most downloaded on crates.io
Bindings for Cyrus SASL.
Last release 2 years ago
no release in 18 months
Ships unpredictably
gaps range from 2 weeks to 2.0 years
Most releases are documented
notes for 20 of 23 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
23 releases · first in 2020
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
(cargo-release) sasl2-sys version 0.1.19+2.1.27
(cargo-release) sasl2-sys version 0.1.19+2.1.27
(cargo-release) sasl2-sys version 0.1.18
(cargo-release) sasl2-sys version 0.1.18
Backwards-incompatible change. Change the type of the log level constants
constants from c_uint to c_int to match the type of the level
parameter of the sasl_log_t typedef ([#40]). The log level constants are:
SASL_LOG_NONESASL_LOG_ERRSASL_LOG_FAILSASL_LOG_WARNSASL_LOG_NOTESASL_LOG_DEBUGSASL_LOG_TRACESASL_LOG_PASSDon't derive Copy or Clone for the sasl_secret_t type, as it represents
a variable-length struct whose true length is not correctly handled by the
auto-derived implementations of Copy and Clone ([#36]).
(cargo-release) sasl2-sys version 0.1.17
(cargo-release) sasl2-sys version 0.1.17
Blindly assume the presence of the system libsasl2 when dynamically linking on
macOS without the vendored feature. (The check that validated the presence
of the system library became invalid in macOS Big Sur, and there isn't an
obvious replacement.)
Backwards-incompatible change. Change the type of SASL_PATH_TYPE_PLUGIN
and SASL_PATH_TYPE_CONFIG from c_uint to c_int to match the type of the
path_type parameter in the sasl_set_path function ([#34]).
Thanks, [@pbor]!
Update to the latest config.guess and config.sub versions. This notably fixes compilation on some MacOS machines with the M1 CPU architecture ([#29]).
config.guess and config.sub versions. This notably
fixes compilation on some MacOS machines with the M1 CPU architecture ([#29]).Include a macOS hint in the message for the error that occurs if libsasl2 is not found.
Include a macOS hint in the message for the error that occurs if libsasl2 is not found.
Update to v0.3.0 of [krb5-src] which bundles libkrb5 v1.19.2.
Introduce the scram feature to enable the SCRAM authentication method via the --enable-scram configure option. This feature requires linking against O
scram feature to enable the SCRAM authentication method via
the --enable-scram configure option. This feature requires linking against
OpenSSL by way of the [openssl-sys] crate. For convenience, the new
openssl-vendored feature re-exports the openssl-sys's crates vendored
feature.When linking against a system copy of libsasl2, permit manually specifying the search directory via the SASL2_DIR, SASL2_LIB_DIR, and SASL2_INCLUDE_DI
SASL2_DIR, SASL2_LIB_DIR, and
SASL2_INCLUDE_DIR environment variables.Introduce the plain feature to enable the PLAIN authentication method via the --enable-plain configure option.
plain feature to enable the PLAIN authentication method via
the --enable-plain configure option.When the gssapi-vendored feature is enabled, don't link against libresolv if the target system is DragonflyBSD, FreeBSD, NetBSD, or OpenBSD. Libresolv
gssapi-vendored feature is enabled, don't link against libresolv if
the target system is DragonflyBSD, FreeBSD, NetBSD, or OpenBSD. Libresolv
does not exist on these platforms, nor is it necessary; the relevant functions
are part of libc directly.Detect when the host system is DragonflyBSD, FreeBSD, NetBSD, or OpenBSD and invoke gmake instead of make, as libsasl2 is only compatible with GNU Mak
gmake instead of make, as libsasl2 is only compatible with GNU
Make, and make on BSD systems defaults to BSD Make.Don't fail cross-compilation on the check for GSSAPI SPNEGO availability. Instead conservatively disable it, but allow it to be manually enabled with
Update to v0.2.0 of [krb5-src] for cross-compilation support.
Ensure the GSSAPI plugin is position independent (i.e., compiled with -fPIC) when the gssapi-vendored feature is enabled.
-fPIC)
when the gssapi-vendored feature is enabled.Introduce the gssapi-vendored Cargo feature, which enables the GSSAPI plugin by building and statically linking against [libkrb5], MIT's Kerberos impl
gssapi-vendored Cargo feature, which enables the GSSAPI plugin
by building and statically linking against [libkrb5], MIT's Kerberos
implementation.Backwards-incompatible change. Use libc types rather than Rust types for constants (e.g., libc::c_int rather than i32) to reduce the number of casts r
Backwards-incompatible change. Use libc types rather than Rust types for
constants (e.g., libc::c_int rather than i32) to reduce the number of
casts required when passing those constants to other sasl2-sys functions.
Thanks, [@sandhose]!
Don't build documentation and tests. This saves time and avoids depending on somewhat esoteric tools like nroff.
Disable maintainer mode in the libsasl2 build system. Because Git does not preserve timestamps on source files, configure can look out-of-date with re
configure can look out-of-date with
respect to configure.ac (et al.), and so make will try to rebuild
configure, which requires autotools. Disabling maintainer mode ensures Make
will never invoke autotools, even if the autotools files look out of date.Pass the --with-pic configure option when building the vendored libsasl2 to enable position-independent code in static archives. This appears to be ne
Pass the --with-pic configure option when building the vendored libsasl2 to
enable position-independent code in static archives. This appears to be
necessary for linking to succeed with some cross-compilation toolchains.
Remove the dependency on autotools when building the vendored libsasl2 by vendoring the source tarball directly, rather than using a Git submodule.
Improve several build script error messages.
Include README contents on the [crates.io crate description][crates-io-page].
<!-- #release:next-url --> [Unreleased]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.22...HEAD [0.1.22]: https://github.com/MaterializeIn
Initial release.
<!-- #release:next-url --> [Unreleased]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.22...HEAD [0.1.22]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.21...v0.1.22 [0.1.21]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.20...v0.1.21 [0.1.20]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.19+2.1.27...v0.1.20 [0.1.19+2.1.27]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.18...v0.1.19+2.1.27 [0.1.18]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.17...v0.1.18 [0.1.17]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.16...v0.1.17 [0.1.16]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.15...v0.1.16 [0.1.15]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.14...v0.1.15 [0.1.14]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.13...v0.1.14 [0.1.13]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.12...v0.1.13 [0.1.12]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.11...v0.1.12 [0.1.11]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.10...v0.1.11 [0.1.10]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.9...v0.1.10 [0.1.9]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.8...v0.1.9 [0.1.8]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.7...v0.1.8 [0.1.7]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.6...v0.1.7 [0.1.6]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.5...v0.1.6 [0.1.5]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.4...v0.1.5 [0.1.4]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.3...v0.1.4 [0.1.3]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.2...v0.1.3 [0.1.2]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.1...v0.1.2 [0.1.1]: https://github.com/MaterializeInc/rust-sasl/compare/v0.1.0...v0.1.1
Your coding agent can read these notes before it upgrades. Set up the MCP server →