-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SASL External #196
Labels
Comments
trevarj
added a commit
to trevarj/tiny
that referenced
this issue
Nov 12, 2021
A user can now generate a x509 certificate, register it with a server, and provide the PEM file to tiny for use over TLS. Closes osa1#196
trevarj
added a commit
to trevarj/tiny
that referenced
this issue
Nov 12, 2021
A user can now generate a x509 certificate, register it with a server, and provide the PEM file to tiny for use over TLS. Closes osa1#196
This was referenced Nov 14, 2021
trevarj
added a commit
to trevarj/tiny
that referenced
this issue
Mar 28, 2022
A user can now generate a x509 certificate, register it with a server, and provide the PEM file to tiny for use over TLS. Closes osa1#196
trevarj
added a commit
to trevarj/tiny
that referenced
this issue
Dec 18, 2022
A user can now generate a x509 certificate, register it with a server, and provide the PEM file to tiny for use over TLS. Closes osa1#196
osa1
pushed a commit
that referenced
this issue
Dec 31, 2022
A user can now generate a x509 certificate, register it with a server, and provide the PEM file to tiny for use over TLS. Closes #196 Overview: 1. Bumped rustls crates 2. Added configuration for SASL EXTERNAL, where a user specifies a path to a PEM file with a certificate inside (generated with instructions from server). 3. Use user provided certificate in TLS connector config for client authorization (crates/libtiny_client/src/stream.rs)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can you add support for the SASL external (rfc 4422)?
Refs:
https://tools.ietf.org/html/rfc4422
https://ircv3.net/specs/extensions/sasl-3.1
The text was updated successfully, but these errors were encountered: