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

Works at Utena University of Applied Sciences (Utenos kolegija), LT #24

Closed
grawity opened this issue Aug 10, 2018 · 2 comments
Closed

Comments

@grawity
Copy link

grawity commented Aug 10, 2018

Confirming that this configuration (EAP-PEAP with MSCHAPv2) will work with @ukolegija.lt and @utenos-kolegija.lt accounts.

(Not that I want to encourage using a configuration that broadcasts your easily-crackable password hash literally everywhere you go, but if it does the job for you...)

@oleks
Copy link
Owner

oleks commented Aug 11, 2018

What exactly is the alternative? WPA PSK didn't work for me last time I checked, but maybe my configuration was bad.

@grawity
Copy link
Author

grawity commented Aug 11, 2018

The same WPA-EAP/PEAP/MSCHAPv2, but with the server's certificate validation enabled. Same logic as HTTPS (and it's even the same SSL/TLS behind the scenes) – if you verify the cert, you know you're always talking to your home institution's auth server. If you don't, it could be anybody's.

(We use a standard web CA from /etc/ssl/certs, so domain_suffix_match="utenos-kolegija.lt" would be the important part. Unfortunately the path to standard CAs is distro-dependent...)

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

No branches or pull requests

2 participants