-
-
Notifications
You must be signed in to change notification settings - Fork 177
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
Error creating launcher form: Unknown OpenSSL error #3701
Comments
Same error, same OS, but I have things in a conda env where the openssl version is 1.1.1s and cryptography version is 38.0.4. |
Something must have gone wrong with the upgrade to openssl 3.x and / or the packaging of python-cryptography. I will investigate asap but I won't have access to my MacOS test env for a few days. |
Thanks for the update. I'm willing to try things out if that would be useful too. |
As suggested I ran with --ssh-upgrade=no, and got a slightly different error message:
|
Ah, so you're using an ssh connection. |
That seems to work! Thanks! |
Same error, I have appending |
Thank you for this solution!! I have spent a lot of time trying to understand what was going on. I know enough stuff to get in trouble, as I like to say. I'm completely new to If possible, could you explain what the Many thanks for your time and help! |
the options apply to when you launch xpra from the command line, with |
Contrary to what is said above, these options should apply to every xpra subcommand you can run. Though obviously, this is only relevant in the cases where ssh is going to be used. |
This link is to an instance of the problem see on MacOS 12.6.1 (Monterey): |
OK, the above fixes worked for me (on Monterey). In particular, this command worked: |
We have encountered this bug trying to deploy xpra for students to use for remote access. Is there a reason that using the system system ssh isn't default? It's superior in almost every way (paramiko ignores .ssh/config, the running ssh key agent, existing control sockets, etc.) in our experience using Xpra. I have been putting ssh=ssh in my xpra.conf on all systems for some time now. I understand that some systems may not have an ssh binary, but (essentially) all Linux/BSD/Mac hosts should. Is paramiko buying xpra something that we just haven't noticed? |
Many.
No it does not. That would be a bug. xpra/xpra/net/ssh/paramiko_client.py Lines 161 to 170 in 5269aff
It does support agents: https://docs.paramiko.org/en/stable/api/agent.html
|
OK -- then I guess i need to file bugs that paramiko doesn't do any of those things on any system I use. |
@eblanton Please include |
I've dug a little bit, and I think the problem is actually that Paramiko doesn't support ProxyJump; between not supporting ProxyJump and not supporting ControlMaster, the behavior without dumping debug information appears as if it's ignoring .ssh/config for the hosts I'm using (because it's ignoring the two relevant config options), by coincidence. I'm filing an Xpra bug (#3745) since Paramiko is default for Xpra and seems to be preferred, but I'll be digging to see if I need to file a Paramiko feature request in the meantime. This is a problem with no macOS hosts anywhere in sight. |
@kcleal Ah, MacOS "features" strike again: the OS doesn't handle config files as arguments so we construct the window using the default config before being able to load the file specified at some point afterwards. echo "ssh=ssh" >> ~/.xpra/xpra.conf
echo "ssh-upgrade=no" >> ~/.xpra/xpra.conf Another potential workaround would be to nuke the |
None of the workarounds should be needed with the latest releases. |
Hi,
Im using macOS big sur 11.7.1. Ive tried installing xpra using the mac installer or via brew and am using xpra version 4.4.3-r1, and OpenSSL 3.0.7 1 Nov 2022. I cant seem to start xpra attach. I keep running into this error:
I also get the same error when using the xpra user-interface. Thanks
The text was updated successfully, but these errors were encountered: