-
Notifications
You must be signed in to change notification settings - Fork 60
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
Added support for SASL EXTERNAL #363
Conversation
Native TLS using openssl is waiting on sfackler/rust-native-tls#209, which will make it much more convenient to add the user's certificate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @trevarj! Reviewed the front-end parts for now. I'll review the client parts tomorrow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, thanks again @trevarj.
Are you currently using this? I didn't test it myself.
Yes, I think I will continue once merged too. |
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
- Showing SASL errors in the respective server tab - Error message changes
Made the SASL config backwards compatible.
f604119
to
934cc02
Compare
Fixed conflicts after pass cmd feature. Needs testing still. |
@osa1 Tested using new password commands and SASL EXTERNAL. Both working as expected! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @trevarj. Code looks good. I will have to read a bit about SASL EXTERNAL before merging this. Hopefully this week..
crates/tiny/config.yml
Outdated
# Providing a path to a PEM file will configure SASL EXTERNAL | ||
# For SASL EXTERNAL certificate and fingerprint generation, see server documentation. | ||
# You will need to register the cert's fingerprint with NickServ | ||
# ex. https://www.oftc.net/NickServ/CertFP/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove this paragraph please. The config is getting quite large. We have an example below on how to use SASL EXTERNAL. We should add this info to the README if necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will add to the Wiki and link to it from the README? (Since the README is getting large too...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 moving this to wiki makes sense to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Add to wiki once merged
Links that I also put in code comments: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @trevarj. Before merging this, could you update CHANGELOG adding your name to "Thanks to ..." part and also a line to describe these changes? I would do it myself but I don't know what this is about and I don't have time to study it now. If it works I'm happy to merge.
@osa1 Updated CHANGELOG. I created a stub page on the wiki to add configuration details later. |
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: