Recently I needed to configure a solution for remote desktop on a Linux server. I decided to give XRDP a shot which uses TigerVNC Server by forwarding the standard RDP port of 3389 to a port VNC is listening on. The end result is to set up a SSH tunnel that forwards local port 3389 over SSH to XDRP which is listening only on the remote localhost on port 3389 as well. Use the information below to set this up on CentOS Linux though the instructions will be similar for other Linux distros as well.
I ran into an annoying problem today. I normally use Firefox for all my pentesting needs and I use google chrome as my default browser for everything else. I was setting up a new Backtrack image for myself and I installed the .deb archive for google chrome which is available on the google web site. When I went to start it up I received the following error message.
Below I will outline the simple steps to overcome this error:
IBM Java SDK Install Error: Failed dependencies: /usr/lib64/libstdc++.so.5 is needed by ibm-java-x86_64-sdk-6.0-9.1.x86_64
While setting up a websphere test server I ran into a minor dependency error during the beginning of installing the necessary packages for websphere. The IBM Java SDK RPM on CentOS 6 was complaining about a failed dependency of a libstdc++ library. The RPM I was attempting to install required libstdc++.so.5 and CentOS 6 has libstdc++.so.6 installed by default. All that is required is to install the libstdc++ compat RPM. The information below describes the error in more detail, how I located the package that installed the necessary file(s), and an example of installing the needed package.
Earlier when configuring XRDP I could not find out how to make XRDP only listen to 127.0.0.1 or localhost. Finally after playing around with multiple variables I thought it might be I picked the right one. Below is an example of my xrdp.ini before modifying the listen address and after modifying the listen address.
When attempting to burn a DVD tonight I was getting a message from within the OSX Disk Utility stating that the Disc Drive was busy. At first I thought it must be a DVD that was not compatible with the DVD burner however I attempted to use three different types of DVD’s with the same message. Finally I realized that I had VMWare Fusion running and one of the VM’s I was using at the time was sharing the Disc Drive with the host OS or OSX. Below are more details about what the message from the OSX Disk Utility will look like and how to remove the disc drive from being shared with a VMWare image.