-
Notifications
You must be signed in to change notification settings - Fork 182
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
[BUG] Using a long project name causes provisioning failure #3093
Comments
First of all, to be precise, the problem is not about the name of the "project" - it is rather about the name of the "server" in the "participants" section. Secondly, this is a known limitation since the server name is the Common Name (CN) in the server cert, and CN cannot exceed 63 chars. Today, you can only use server name to specify the server's host name. So if your host name exceeds 63 chars, you are stuck. Version 2.6 will fix this problem by allowing multiple host names and IP addresses for the server, and you no longer have to use the server name as the host name: the server name can be a simple unique string. |
One more note on the issue. We also found cryptography fixed an issue a few months ago. That fix changed how cryptography handled long CN field. Previously, it allowed CN longer than 64. After the fix, it enforced the limitation on CN length so it's compliant with the standard. With different versions of cryptography packages, users may see either the reported errors or no errors during provisioning with long project names. |
* Fix NVIDIA#3093 * Address comments
Setting a project name of over 64 characters causes provisioning failure.
Traceback:
To Reproduce
Expected behavior
Successful provisioning, or at least an informative error message.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: