Date: Tue, 15 Feb 2022 10:23:59 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 261941] [NEW PORT] net/nxssh: Modified openssh client, used by rxclient (formerly opennx) Message-ID: <bug-261941-7788-j7APxKXVaB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261941-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-261941-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261941 --- Comment #3 from Timothy Beyer <beyert@cs.ucr.edu> --- The opennx port (much like it's replacement rxclient) does not work without= an nxssh executable present, and prior nxssh executables to my knowledge were = just proprietary linux binaries, and prior to this, I do not recall nxssh being available on FreeBSD, at least without the linuxulator. That being said, for years I've used RDP with xrdp in a commercial context = for remote access, and have found it more than satisfactory, so this submission= is mostly to resolve a long-standing issue ("Fails to execute /usr/local/bin/nxssh", PR #240234) with the net/opennx port, which I mainta= in. In short, I do not believe that net/opennx ever worked due to this previous= ly missing executable. I don't know what the correct answer is, as I don't have the motivation or = the use case to port rxclient right now, but as long as we still keep net/openn= x, then we will need this in the ports tree. I understand the motivation to remove that port to reduce maintenance burden for everyone involved, and to make this port unnecessary, if that is deemed= the correct approach. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261941-7788-j7APxKXVaB>