Description of problem: Login to NX server fails with "404 ERROR: wrong password or login" when ProxyCommand is set in ssh_config. (ProxyCommand is for example set by ipa-client) Version-Release number of selected component (if applicable): freenx-server-0.7.3-27.fc17.x86_64 ProxyCommand is executed with the user's shell. For nx this is nxserver and obviously not working. Solution is to call ssh with -o "ProxyCommand none" from nxnode-login. That should not conflict with the intended use of ProxyCommand in global ssh_config. (neither the normal use of setting a proxy nor the special use of sssd)
Same problem for Fedora 18, took me an hour to figure out that 'ProxyCommand' is the problem, the solution from #1 worked for me as well. Is it possible to add the patch from comment #1 to the official RPM for Fedora 17 and Fedora 18?
I do also confirm that I was impacted on our client machines running RHEL 6.4 with ipa client (ipa-client-3.0.0-26.el6_4.2.x86_64) and freenx (freenx-server-0.7.3-18.el6.x86_64). The proposed workaround from Description solves the problem.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I assume it's not fixed in F19 either? Upstream has no development activity for several years now. Is this package/project dead?
Yep, looks like the problem exist in F19 as well. I assume the package/project is dead?
I checked Bug #903186 and it looks like Ville Skyttä <ville.skytta> maintains now this package, so could please someone assign this bug to Ville Skyttä?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
(In reply to JM from comment #6) > looks like Ville Skyttä <ville.skytta> maintains now this package I'm no longer using or maintaining freenx-server, I'm a x2goclient/server user now.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.