Quentin Gliech
2d3bf03d63
`rand` 0.10 and the new RustCrypto generation both build on `rand_core` 0.10, so they have to move together: - `rand`, `rand_chacha` and `rand_core` 0.10 - `digest` 0.11, `sha2` 0.11, `hmac` 0.13, `const-oid` 0.10 - `elliptic-curve` 0.14, `ecdsa` 0.17, `p256`, `p384` and `k256` 0.14, `signature` 3 - `der`, `spki` and `sec1` 0.8, `pkcs8` 0.11, `pem-rfc7468` 1.0 - `rsa` 0.10.0-rc.19 and `pkcs1` 0.8.0-rc.5, which have no stable release yet. They are pinned exactly, because release candidates break their API between releases. - `argon2` 0.6 and `pbkdf2` 0.13 On the `rand` side, `RngCore` becomes `Rng` and the old `Rng` becomes `RngExt`. `gen_*` becomes `random_*`, `thread_rng` becomes `rng`, `distributions` becomes `distr`, and `from_rng` can no longer fail. On the crypto side, `mas-jose` and `mas-keystore` move to `BoxedUint` for RSA, to the `pkcs1` and `pkcs8` reference types, and to the `Generate` trait for key generation, and `mas-jose` no longer depends on `generic-array`. Password hashing goes through `hash_password_with_rng`. Stored data is unaffected. The password hashing snapshots are unchanged, so bcrypt, Argon2 and PBKDF2 produce the same hashes for the same input and salt, and `pbkdf2` 0.13 keeps the same defaults (SHA-256, 600 000 rounds). The keystore snapshots change only because keys generated from a seeded RNG differ. The snapshots of keys loaded from files are unchanged. `opa-wasm` 0.3.3 already uses this generation, so most of the duplicate crates it pulled in go away. The `deny.toml` skip list now names what still pulls the older versions: cookie, sqlx, headers, wasmtime and pest for RustCrypto, and opentelemetry_sdk, sentry and ulid for `rand` 0.9.
Matrix Authentication Service
MAS (Matrix Authentication Service) is a user management and authentication service for Matrix homeservers, written and maintained by Element. You can directly run and manage the source code in this repository, available under an AGPL license (or alternatively under a commercial license from Element). Support is not provided by Element unless you have a subscription.
It has been created to support the migration of Matrix to a next-generation of auth APIs per MSC3861.
See the Documentation for information on installation and use.
You can learn more about Matrix and next-generation auth at areweoidcyet.com.
🚀 Getting started
This component is developed and maintained by Element. It gets shipped as part of the Element Server Suite (ESS) which provides the official means of deployment.
ESS is a Matrix distribution from Element with focus on quality and ease of use. It ships a full Matrix stack tailored to the respective use case.
There are three editions of ESS:
- ESS Community - the free Matrix distribution from Element tailored to small-/mid-scale, non-commercial community use cases
- ESS Pro - the commercial Matrix distribution from Element for professional use
- ESS TI-M - a special version of ESS Pro focused on the requirements of TI-Messenger Pro and ePA as specified by the German National Digital Health Agency Gematik
💬 Community room
Developers and users of Matrix Authentication Service can chat in the #matrix-auth:matrix.org room on Matrix.
🛠️ Standalone installation and configuration
The best way to get a modern Element Matrix stack is through the Element Server Suite, which includes MAS.
The MAS documentation describes how to install and configure MAS. We recommend using the Docker image or the pre-built binaries.
📖 Translations
Matrix Authentication Service is available in multiple languages. Anyone can contribute to translations through Localazy.
🏗️ Contributing
See the contribution guidelines for information on how to contribute to this project.
⚖️ Copyright & License
Copyright 2021-2024 The Matrix.org Foundation C.I.C.
Copyright 2024, 2025 New Vector Ltd.
Copyright 2025, 2026 Element Creations Ltd.
This software is dual-licensed by Element Creations Ltd (Element). It can be used either:
(1) for free under the terms of the GNU Affero General Public License (as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version); OR
(2) under the terms of a paid-for Element Commercial License agreement between you and Element (the terms of which may vary depending on what you and Element have agreed to). Unless required by applicable law or agreed to in writing, software distributed under the Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses.