Skip to content
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 is "secure, encrypted authentication with the server" #107

Open
Mikaela opened this issue Feb 11, 2015 · 4 comments
Open

SASL is "secure, encrypted authentication with the server" #107

Mikaela opened this issue Feb 11, 2015 · 4 comments
Labels

Comments

@Mikaela
Copy link

Mikaela commented Feb 11, 2015

SASL (PLAIN (communi/libcommuni#23)) is not any more secure/encrypted than any other way to identify and if you want it to be encrypted, you also use SSL connection and check server certificates (communi doesn't do this as far as I know).

@Venemo
Copy link
Contributor

Venemo commented Aug 18, 2015

I don't understand, what exactly is the issue here?

@Mikaela
Copy link
Author

Mikaela commented Aug 18, 2015

That the "Use SASL" checkbox misleadingly calls it as "secure, encrypted authentication with the server". In reality IRC SASL doesn't have encryption (unless you use SSL/TLS) and isn't more secure than any other way to identify to services.

More proper message would be that "SASL automatically identifies you to NickServ before you join channels", which is simplification, but everyone would understand what it does.

@Venemo
Copy link
Contributor

Venemo commented Aug 21, 2015

@Mikaela So if I understand correctly, there isn't an actual problem with SASL, just the wording that is on the UI is not clear enough, right?

@Venemo Venemo added the BUG label Aug 21, 2015
@Mikaela
Copy link
Author

Mikaela commented Aug 21, 2015

Yes, the only issue is misleading wording.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants