mirrors/xrdp
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #2030 from metalefty/cleanup

Browse Source 
Cleanup unnecessary files #2030
This commit is contained in:
matt335672 2021-10-26 09:28:36 +01:00 committed by GitHub
commit dd2336f8c6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
8 changed files with 0 additions and 274 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
Makefile.am
View File

@ -11,15 +11,8 @@ EXTRA_DIST = \
astyle_config.as \
bootstrap \
coding_style.md \
description-pak \
design.txt \
faq-compile.txt \
faq-general.txt \
file-loc.txt \
fontdump \
install.txt \
m4 \
postinstall-pak \
vrplayer
if XRDP_NEUTRINORDP

1
description-pak
View File

@ -1 +0,0 @@
RDP server for Linux

35
design.txt
View File

@ -1,35 +0,0 @@
This document is intended to explain xrdp server design.
Many connections, all capable of running different modules
one connection could be using a vnc connection
one could be running a custom app made for xrdp
one could be running a X11 session
clients control the screen size and color depth
all controlled by a configuration file.
you can create a lib or use a lib with your executable that talks
to xrdp server.
------ ----------
-xrdp---linked-------mylib.so- session 1
------ ----------
|
| -------------------------
|----unix socket--myapp linked to libxrdp- session 2
| -------------------------
|
| -----------
|----linked-------mylib2.so- session 3
-----------
Any of the above sessions can repeat or have different session
numbers or not even be used.
If a session is disconnected, all that changes is the rdp connection
is lost, the session remains.
For X11, start the XServer after the user is
authenticated. First check for the next available X11 display,
create a user session, start the XServer and set the DISPLAY environment
variable.

56
faq-compile.txt
View File

@ -1,56 +0,0 @@
Compile FAQ
Q. I get one of the following errors:
- "security/pam_appl.h: File or directory doesn't exist"
- "configure: error: please install libpam0g-dev or pam-devel"
What is wrong?
A. You need to install the pam development package.
For Debian / Ubuntu this package is called libpam0g-dev.
For Red Hat / SUSE this package is called pam-devel.
Q. I get an error: "configure: error: please install libssl-dev or openssl-devel"
A. You need to install the openssl development package.
For Debian / Ubuntu this package is called libssl-dev.
For Red Hat / Fedora this package is called openssl-devel.
For SUSE / openSUSE this package is called libopenssl-devel.
Q. I get one of the following errors:
- "configure: error: please install libx11-dev or libX11-devel"
- "configure: error: please install libx11-dev and libxfixes-dev or libXfixes-devel"
A. You need to install the X11 and X11 Xfixes development package(s).
For Debian: libx11-dev and libxfixes-dev.
For Red Hat / SUSE: libX11-devel and libXfixes-devel.
Q. I get an error: "rail.c:31:35: fatal error: X11/extensions/Xrandr.h: No such file or directory"
A. You need to install the Xrandr development package.
For Debian / Ubuntu this package is called libxrandr-dev.
For SUSE / openSUSE this package is called libXrandr-devel.
Q. How do I configure the same continuous integration bulids for my XRDP fork as the official XRDP repository?
A. The XRDP project uses both Travis-CI.org and Cirrus-CI.com for continuous integration.
Both of these services are free for open source projects (both the official
repository and forks), and these services integrate with Github to build any
changes pushed to public Github repositories.
To configure Travis CI for your XRDP fork on github:
1. Follow Travis CI instructions for connecting your github account to Travis CI
https://docs.travis-ci.com/user/tutorial/#to-get-started-with-travis-ci-using-github
2. In the Travis CI dashboard setting page select your XRDP fork repository for building pushed branches.
3. Push a commit to a branch in your XRDP fork on github and Travis CI should
start building the branch because the XRDP repository already contain a .travis.yml file.
To configure Cirrus CI for your XRDP fork on github:
1. Follow Cirrus CI instructions for connecting your github account to Cirrus CI
https://cirrus-ci.org/guide/quick-start/
2. In the Github setting page for the Cirrus CI application, enable Cirrus CI
access to your XRDP fork repository.
3. Push a commit to a branch in your XRDP fork on github and Cirrus CI should
start building the branch because the XRDP repository already contain a .cirrus.yml file.

22
faq-general.txt
View File

@ -1,22 +0,0 @@
General FAQ
Q. What is RDP?
A. RDP stands for Remote Desktop Protocol. It's the protocol used by Windows
terminal servers to talk to the terminal server clients.
Q. What is xrdp?
A. xrdp, usually spelled in lower case, is as open source implementation of the
RDP protocol.
Q. I can't get xrdp to compile in Ubuntu. What can I do?
A. See faq-compile.txt.
Q. Can I use LDAP?
A. Yes, xrdp uses PAM and thus can be configured to use LDAP for authentication.

78
file-loc.txt
View File

@ -1,78 +0,0 @@
default build will install the following
/usr/local/lib/xrdp
libcommon.so
libmc.so
libscp.so
libvnc.so
libxrdp.so
libxrdpapi.so
libxup.so
/usr/local/bin
xrdp-dis
xrdp-genkeymap
xrdp-keygen
xrdp-sesadmin
xrdp-sesrun
/usr/local/sbin
xrdp
xrdp-sesman
xrdp-sessvc
xrdp-chansrv
/etc/xrdp
km-xxxxxxxx.ini
sesman.ini
rsakeys.ini
startwm.sh
xrdp.ini
xrdp_keyboard.ini
/etc/xrdp/pulse
default.pa
/etc/pam.d
xrdp-sesman
/usr/local/share/man/man1
xrdp-dis.1
/usr/local/share/man/man5
sesman.ini.5
xrdp.ini.5
/usr/local/share/man/man8
xrdp-chansrv.8
xrdp-genkeymap.8
xrdp-keygen.8
xrdp-sesadmin.8
xrdp-sesman.8
xrdp-sesrun.8
xrdp-sessvc.8
xrdp.8
/usr/local/share/xrdp
ad24b.bmp
ad256.bmp
cursor0.cur
cursor1.cur
sans-10.fv1
xrdp24b.bmp
xrdp256.bmp
xrdp_logo.bmp
when running, the following are created and written to
/var/run
xrdp.pid
sesman.pid
/var/log
xrdp.log
xrdp-sesman.log
/tmp/.xrdp
xrdp*

54
install.txt
View File

@ -1,54 +0,0 @@
Installation directions for xrdp.
Things you need to compile and install. Most systems don't
have these installed by default.
gcc and make
Header files for pam
Header files for openssl
You can build sesman without pam, there is a Makefile parameter
for that.
I also have a replacement ssl_calls.c to avoid the openssl dependency
email me(Jay) for it or see http://server1.xrdp.org/xrdp/openssl.
Due to the license, I can't include it in this project.
http://server1.xrdp.org/xrdp/openssl/
unpack the tarball
tar -zxvf xrdp-0.1.tar.gz
this will create a folder xrdp
switch to the xrdp folder(cd xrdp)
run make
as root, run make install
This will install most of the files in /usr/local/xrdp.
Some files install in /etc/xrdp. These are configuration
files.
files and location
/usr/local/xrdp/startwm.sh - script that starts the window manager
You may need to edit this file to run your window manager.
/etc/sesman.ini - sesman configuration file
/etc/rsakeys.ini - rsa stuff
/etc/xrdp.ini - xrdp configuration file
/var/run/sesman.pid
/var/rub/xrdp.pid
Sesman and xrdp both have to be running as root.
You should set them to start when the system starts.
You can use xrdp_control.sh script to start them.
To completely remove xrdp
remove directory /usr/local/xrdp
remove directory /etc/xrdp
remove file /var/run/xrdp.pid
remove file /var/run/sesman.pid
remove any startup links added to /etc/init.d or /etc/rcX.d
jay.sorg@gmail.com

21
postinstall-pak
View File

@ -1,21 +0,0 @@
#!/bin/sh -e
if ! ([ "$1" = "configure" ] || [ "$1" = "reconfigure" ]); then
exit 0
fi
XRDP="xrdp"
ADDUSER="/usr/sbin/adduser"
XRDPLOG="/var/log/xrdp-sesman.log"
SESMANLOG="/var/log/xrdp-sesman.log"
[ -d /var/run/xrdp ] || mkdir -p /var/run/xrdp
$ADDUSER --system --disabled-password --disabled-login --home /var/run/xrdp \
--no-create-home --quiet --group $XRDP
touch $SESMANLOG $XRDPLOG
chown $XRDP:$XRDP $SESMANLOG
chown $XRDP:$XRDP $XRDPLOG
#DEBHELPER#