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

Bump up shared secret limit to 512? #119

Open
DimitriPapadopoulos opened this issue May 8, 2024 · 2 comments
Open

Bump up shared secret limit to 512? #119

DimitriPapadopoulos opened this issue May 8, 2024 · 2 comments

Comments

@DimitriPapadopoulos
Copy link
Contributor

In practice, I doubt anyone uses shared secrets of more than 256 characters. However, a Google search provided some empirical information about maximal lengths for various implementations. The AWS Directory Service is documented to have an exceptional upper limit of 512.

From the AWS Directory Service Documentation:

Length Constraints: Minimum length of 8. Maximum length of 512.

@alandekok
Copy link
Member

We can update the length to 512, but I doubt many people will use it. There really is little point to any shared secret longer than 256 characters. If people are that worried about security, they should use TLS.

@DimitriPapadopoulos
Copy link
Contributor Author

I totally agree, even 96 was overkill. It's just that some might set a long secret just because it's possible.

For example, see discussion in Please enlarge the maximum Shared secret lengt in RADIUS Authenticattion Server settings:

Thanks for your reply, but it still doesn't change the fact that my client is allready running this on multiple locations from different suppliers, and only Unifi doesn't support this while Microsoft RADIUS server does go up to 128 chars. I can't change the source. Can only ask Ubiquity to follow Microsoft standards.

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