LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Any advice on building and running xrdp and xorgxrdp on Slackware? (https://www.linuxquestions.org/questions/slackware-14/any-advice-on-building-and-running-xrdp-and-xorgxrdp-on-slackware-4175617278/)

allend 11-09-2017 08:17 AM

Any advice on building and running xrdp and xorgxrdp on Slackware?
 
My work IT department (in their widely debated wisdom) have now implemented Windows Applocker functionality that has killed the Cygwin setup that I was using on my work provided computer running Windows to access and maintain my Slackware intranet server. After consultation, the suggestion is to pay the extra money to get a less locked down setup and take responsibility for on-going maintenance. I do not like this because:
1. I am pig-headed and do not want to have to pay for restoring previous functionality.
2. I have a role implementing and maintaining an application that should be usable to anybody using the standard environment, so I would prefer to develop and test in the standard environment.
3. I want to not have to deal with suggestions that a non-standard environment is the cause of any future issues.

I have found that the Google Chrome Secure Shell webapp allows SSH access, but I would like to get access to a full remote desktop.
As the Windows Terminal Services Client (mstsc.exe) is still functional, I am considering setting up my server to use xrdp and xorgxrdp. Looking at SlackBuilds.org, there is a script to build xrdp 0.6.1, but the latest version is 0.9.3.1 Also, xrdp now supports xorgxrdp, that as I understand it adds additional driver support to X11 in a less intrusive manner. However, there is no SlackBuild script for xorgxrdp.
After that long preamble, has anybody got any experience or advice they can share?

business_kid 11-09-2017 03:29 PM

Time for a memo to management.

Problem: This intranet server can no longer be maintained because Applocker had reduced the functionality of Office computers. The options are

Option A: Outline needs, time (estimated), drawbacks, security issues & Costs
Option B: Outline needs, time (estimated), drawbacks, security issues & Costs
etc.
At least one of those should be a linux VM in a windows machine. Managers are nuts about conformity and ignorance is bliss. Don't leave any reasonable option out, because the memo will be shown to 'the dark side' i.e. windows nerds, and you wouldn't want them trumping you.

Let the managers decide. If it's a windows solution, let the nerds do the spadework. Answer the question what will happen to their service if I come to a sticky end? A similar question is Can They Fire You? If they need you, it's bad management on their part, especially if you meet a sticky end.

They will choose an option. If they don't supply the needs, memo again and accuse them of not being serious because they didn't supply your needs, so they're obviously not serious about this. that usually works.

Alien Bob 11-09-2017 04:31 PM

You could try KDE's krdc (frontend to VNC and RDP) combined with freerdp for the actual RDP implementation.

allend 11-09-2017 06:07 PM

Quote:

Time for a memo to management.
:D
The managers have decided and the solution being rolled out is a separate network that will allow for less locked down environments. Just has not arrived here yet.
Quote:

You could try KDE's krdc (frontend to VNC and RDP) combined with freerdp for the actual RDP implementation.
I had not considered that particular combo.

Thanks for the support and suggestions.

glorsplitz 11-09-2017 08:49 PM

couple stupid questions

why are you accessing and maintaining your Slackware intranet server from work, shouldn't you be working? :tisk:

How far does Windows Applocker go, would it prevent say slackware vbox vm?

GazL 11-10-2017 05:28 AM

Quote:

Originally Posted by allend (Post 5778664)
My work IT department (in their widely debated wisdom) have now implemented Windows Applocker functionality

When you have so many idiot users who will happily run ransomware that someone sends them in email without even a thought, I suppose this is the sort of totalitarian stand you have to make. In retrospect there was a lot to be said for the 3270 era. :)

I'm sorry to hear that you were caught in the collateral damage.

Quote:

Originally Posted by allend (Post 5778864)
The managers have decided and the solution being rolled out is a separate network that will allow for less locked down environments. Just has not arrived here yet.

Phew! at least they didn't decide to move the intranet to IIS!
Dodged a bullet there. ;)

igadoter 11-10-2017 05:32 AM

Is this
Quote:

Originally Posted by business_kid (Post 5778816)
trumping you

somehow related to action of recent US president? I am only curious, English is funny language, or maybe rather people make it funny.

allend 11-10-2017 06:59 AM

Quote:

couple stupid questions
I am from the camp that says there are _no_ stupid questions.
Quote:

why are you accessing and maintaining your Slackware intranet server from work, shouldn't you be working?
Er - The server is at work, hiding machines that otherwise would not be allowed. They are controller PCs that run software that is not supported on current operating systems and that is not compatible with anti-virus software. Accessing the server to check backups, reset printer queues and restart samba mounts is work related on-going maintenance.
Quote:

How far does Windows Applocker go, would it prevent say slackware vbox vm?
The current standard operating system is Windows 7 Enterprise. No VM capability is available. Nor do I want it. I had a bad experience with Hyper V when a power failure on the host irrecoverably corrupted a VM that I had spent quite some time building. What Applocker does is decided by the person setting the policies.
Quote:

When you have so many idiot users who will happily run ransomware that someone sends them in email without even a thought
Explains why I get an email about once a week warning not to click on the latest circulating threat, coming from the same IT department that occasionally sends an email asking you to click on a link to register your machine for an unattended upgrade. The phrase 'go figure' springs to mind.
Quote:

Phew! at least they didn't decide to move the intranet to IIS!
Shh! They might hear you.
Quote:

trumping you
That phrase actually arises from card games where a card suit is declared as the trump suit (e.g. bridge, five hundred) that gives them special powers. A low pip trump card card can overpower a high pip or picture card, hence you have been "trumped". (I will leave the irony of the joker being the most powerful trump card to others.)
Quote:

English is funny language, or maybe rather people make it funny.
Both. On the former, "impossible" might be better while on the latter "we try".

Slax-Dude 11-10-2017 10:47 AM

Quote:

Originally Posted by Alien Bob (Post 5778837)
You could try KDE's krdc (frontend to VNC and RDP) combined with freerdp for the actual RDP implementation.

I think he wants to access Slackware from Windows, not the other way around.

I use xrdp with vnc to access my remote Slackware systems, but would like to try xorgxrdp as alternative to vnc backend.
Performance is OK, although not on the same level as nx (when it worked on Slackware).
I remember following a thread where someone was trying to get a x2go server going on Slackware 14.2 but no news there as well.

business_kid 11-10-2017 11:29 AM

Quote:

Originally Posted by igadoter (Post 5778980)
Is this

somehow related to action of recent US president? I am only curious, English is funny language, or maybe rather people make it funny.

Definitely not. The dumb blonde you mention is the embodiment of Parkin's Peter Principle: "Everyone is promoted to the level at which he is incompetent!" I was thinking of one-upmanship by windows activists.

Gerard Lally 11-10-2017 11:37 AM

Quote:

Originally Posted by Slax-Dude (Post 5779078)
I remember following a thread where someone was trying to get a x2go server going on Slackware 14.2 but no news there as well.

That might have been me. I lost interest in a Slackware terminal server when I realised the teachers refused to work with anything other than Microsoft (probably because Microsoft were giving them freebies like tablets and copies of Office).

OP - have you considered Xorg for Windows (that's if Applocker doesn't block it, of course)?

vcxsrv is an excellent implementation. SSH (with X forwarding) to your Slackware server and X clients will display on your Windows machine.

kjhambrick 11-10-2017 12:19 PM

Quote:

Originally Posted by Slax-Dude (Post 5779078)
I remember following a thread where someone was trying to get a x2go server going on Slackware 14.2 but no news there as well.

Quote:

Originally Posted by Gerard Lally (Post 5779098)
That might have been me. I lost interest in a Slackware terminal server when I realised the teachers refused to work with anything other than Microsoft (probably because Microsoft were giving them freebies like tablets and copies of Office).

And me too in a recent thread but I gave up on x2goserver myself.

I never got it to work with my 'standard' Slackware 14.2 KDE4 Desktop.

There were some recommendations to fall back to to a minimal DE but what's the point in that ? I can always use VNC.

As for allend's questions about xrdp and xorgxrdp ...

Thank you for mentioning these programs !

I've been looking at the documentation and source code for xorgxrdp v0.2.4 as well as the README and the files in the xrdp.SlackBuild ...

I've still got some reading to do but it certainly looks promising and if it works as advertised, this should provide a solution to allow a Windows Client to run X on a Linux Box via RDesktop ...

( :) Boy do I miss the 'Free Forever' NX Version 3.x :) )

Getting xorgxrdp + xrdp running on Slackware 14.2 is now on my ToDo list ... I'll report back when I get a round tuit.

Please let us know if you learn anything too !

Thanks again allend

-- kjh

kjhambrick 11-10-2017 03:23 PM

3 Attachment(s)
allend --

Edit: Fixed a bug and reattached xrdp.SlackBuild.txt

I was not able to build xrdp v0.6.1 on my Slackware64 14.2 + MultiLib system unless I fiddled with the LDFLAGS in the SlackBuild before it invoked ./configure

However, I downloaded xrdp-0.9.4.tar.gz and it built without patches ...

All I really changed in the SlackBuild was the sense of the USE_PAM Variable ( changed it to: NOPAM_OPT="--disable-pam" ) and the list of km-????????.ini files has changed.

EDIT: oops ... I also pounded out the v0.6.1-specific patch work in the SlackBuild.

Anyhow, if you're interested, the xrdp.SlackBuild.txt, xrdp.info.txt and doinst.sh.txt files are below.

Download the official xrdp SlackBuild directory someplace convenient and replace the official SBo xrdp.SlackBuild, xrdp.info and doinst.sh files with the three files below ( i.e. drop the .txt extents ).

Download xrdp 0.9.4 into the SlackBuild Directory and try the xrdp.SlackBuild.

YMMV ... I am running Slackware64 14.2 + Multilib + NVIDIA-Linux-x86_64-384.98.run + a few Alien and SBo Packages on this System ... but xrdp v0.9.4 built OK for me.

My next step is to construct an xorgxrdp.SlackBuild ... will let you know.

-- kjh

willysr 11-10-2017 06:51 PM

xrdp has been updated in my branch and will be included in this week's public update

kjhambrick 11-11-2017 08:20 AM

5 Attachment(s)
Quote:

Originally Posted by willysr (Post 5779240)
xrdp has been updated in my branch and will be included in this week's public update

Wow ! Thanks willysr.

I didn't mean to hijack Phillip Warner xrdp.SlackBuild ...

Oh well, as they say -- in for a penny, in for a pound ... So, here we go :)

After installing xrdp version 0.9.4 via the new xrdp.SlackBuild, I was able to compile the xorgxrdp XOrg modules 'by hand, the old way into a clean TOPDIR:
Code:

configure --prefix=/usr/local/test && make && make install DESTDIR=/usr/local/test
Once I saw what's what, I made an xorgxrdp.SlackBuild

Attached below are the essential pieces for an xorgxrdp.SlackBuild

I have not yet studied the xorgxrdp docs enough to actually test the system but it compiled very cleanly and all the files in the Package are new files so it looks safe enough :)

Anyhow, if you want xorgxrdp:

After installing xrdp ...

Save the attached files into a directory, say xorgxrdp/ ; remove the .txt extension from each file ; optionally chmod 755 xorgxrdp.SlackBuild

Download xorgxrdp version 0.2.4 into your xorgxrdp/ SlackBuild directory and try the xorgxrdp.SlackBuild ( ! check the gpg signature and/or the md5sum which is in the xorgxrdp.info file )

The xorgxrdp modules build fine on my Slackware64 14.2 + MultiLib + NVIDIA-Linux-x86_64-384.98.run system

I will follow up on this !

Here's to high hopes for a new way for Windows Users to connect to a Linux X Desktop !

Have Fun All'Y'All !

EDIT: Found and fixed a bug in the xorgxrdp.SlackBuild where it did not delete the old working directory when rebuilding the Package.

-- kjh


All times are GMT -5. The time now is 03:14 PM.