Share This

Share This

sudo aptitude search ABC (apt-cache search ABC)
sudo aptitude install ABC (sudo apt-get install ABC)
sudo aptitude remove ABC (sudo apt-get remove ABC)

.deb (watch out for unresolved dependencies!)

sudo dpkg -i ABC.deb

.rpm (use .deb packages preferably though)

sudo alien -i *.rpm

.tar.gz (requires sudo aptitude install checkinstall)

tar xzvf ABC.tar.gz
cd ABC
./configure
make
sudo checkinstall

.package, .sh, .bin (just download and execute)

chmod +x ABC
./ABC

.exe (requires you to have wine installed)

wine ABC.exe

Share This

1. Download and install the deborphan package. This is the application that finds unnecessary dependencies: “sudo apt-get install deborphan”
2. Execute this command until there are no more dependencies: “apt-get remove $(deborphan)”

Alternatively, you can also put that command into a script, if you don’t want to remember that line:

1. Download the script here: del_orph_pkgs.txt
2. Change the filename from “del_orph_pkgs.txt” to “del_orph_pkgs.sh” and do a “chmod +x del_orph_pkgs.sh” so we can execute it.
3. Execute the script with “sudo del_orph_pkgs.sh” multiple times until it won’t find anymore dependencies. This is necessary, because those libraries, which are not needed anymore, might have dependencies them self, which become obsolete. So another execution cycle will eliminate those as well.

Share This

1. Install Linux header for your current kernel: sudo apt-get install build-essential linux-headers-`uname -r`
2. Download these two files: vmmon.tar & vmnet.tar
3. Move them to VMWare’s module folder: sudo mv vmmon.tar vmnet.tar /usr/lib/vmware/modules/source/
4. It’s also a good idea to change the owner of those files to root.root: sudo chown root.root /usr/lib/vmware/modules/source/*tar
5. Last but not least, rerun VMWare’s config file: sudo /usr/bin/vmware-config.pl

If the above mentioned solution should not work for you, please post a comment and I will see how I can help you.

Share This

Install the following: “sudo apt-get install g++ gcc make automake1.9 libtool” and restart KDevelop. You should now be able to compile your projects without that error.

Share This

“None of the pre-built vmmon modules for VMware Workstation is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)?”

It seemed like I didn’t have the headers for my current kernel installed. A short “ sudo apt-get install build-essential linux-headers-$(uname -r)” quickly did the trick and I was able to successfully complete the configuration.

Share This

Share This

Step 1: Generate a Private Key

The first step is to create your RSA Private Key. This key is a 1024 bit RSA key which is encrypted using Triple-DES and stored in a PEM format so that it is readable as ASCII text.

Step 2: Generate a CSR (Certificate Signing Request)

Once the private key is generated a Certificate Signing Request can be generated. The CSR is then used in one of two ways. Ideally, the CSR will be sent to a Certificate Authority, such as Thawte or Verisign who will verify the identity of the requestor and issue a signed certificate. The second option is to self-sign the CSR, which will be demonstrated in the next section.

During the generation of the CSR, you will be prompted for several pieces of information. These are the X.509 attributes of the certificate. One of the prompts will be for “Common Name (e.g., YOUR name)”. It is important that this field be filled in with the fully qualified domain name of the server to be protected by SSL. If the website to be protected will be https://www.yatblog.com, then enter www.yatblog.com at this prompt. If you want to create a so called “wildcard” certificate, which means the same certificate can be used on an unlimited number of subdomains, just enter an asterisk as the hostname, in our example that would be *.yatblog.com. The command to generate the CSR is as follows:

Step 3: Remove Passphrase from Key

One unfortunate side-effect of the pass-phrased private key is that Apache will ask for the pass-phrase each time the web server is started. Obviously this is not necessarily convenient as someone will not always be around to type in the pass-phrase, such as after a reboot or crash. mod_ssl includes the ability to use an external program in place of the built-in pass-phrase dialog, however, this is not necessarily the most secure option either. It is possible to remove the Triple-DES encryption from the key, thereby no longer needing to type in a pass-phrase. If the private key is no longer encrypted, it is critical that this file only be readable by the root user! If your system is ever compromised and a third party obtains your unencrypted private key, the corresponding certificate will need to be revoked. With that being said, use the following command to remove the pass-phrase from the key:

The newly created server.key file has no passphrase in it anymore.

Step 4: Generating a Self-Signed Certificate

At this point you will need to generate a self-signed certificate because you either don’t plan on having your certificate signed by a CA, or you wish to test your new SSL implementation while the CA is signing your certificate. This temporary certificate will generate an error in the client browser to the effect that the signing certificate authority is unknown and not trusted.

To generate a temporary certificate which is good for 365 days, issue the following command:

Step 5: Installing the Private Key and Certificate

When Apache with mod_ssl is installed, it creates several directories in the Apache config directory. The location of this directory will differ depending on how Apache was compiled.

Step 6: Configuring SSL Enabled Virtual Hosts

If you want to redirect connections to the standard, unencrypted port 80, simply use the following lines:

Step 7: Restart Apache and Test

Share This