-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
SSL Key to Small?? #126
Comments
I have gotten it to work by disabling SSL on barrier but this is not the ideal solution, if anyone has any idea, let me know! |
I'm not able to reproduce this error for myself, but after a small bit of research (see https://weakdh.org/) I believe bumping the SSL cert key size is a good idea regardless. Please reopen if this issue comes back. Thanks! |
Done in order to match the size specified in src/gui/src/SslCertificate.cpp Also see Debian bug #907528 http://bugs.debian.org/907528 Related to Barrier Issue #126
I've encountered this problem with the latest version. Built v2.2.0 (master) from sources both on Mac and Linux. Error: |
Found workaround:
|
that works for me, but now I feel less secure? 😟 |
Of course. Don't lower
|
@rustyx any ideas how to resolve this issue if you still get it after you have confirmed that you are using 2048 bits with RSA? |
Changed
and it solved my problem |
I had this problem and found [https://wiki.archlinux.org/title/Barrier] that helped me get past the problem. In my case I needed to:
|
ref: debauchee/barrier#126 Upload REAME.md
If you are using RHEL 8 & above, Steps to resolve. update-crypto-policies --show update-crypto-policies --set DEFAULT reboot |
I installed barrier on both my desktop and laptop, both running Debian sid. Install went perfectly, but I seem to have a problem using the application itself. On the server log, I keep on receiving
ERROR: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small
On the client the log says:
ERROR: ssl error occurred (system call failure) ERROR: failed to connect to a secure socket
This happens regardless of which machines is server/client.
Any ideas what this means and the solution?
Using
OpenSSL 1.1.1
if that matters at all.The text was updated successfully, but these errors were encountered: