Using keys instead of password on ubuntu server

One of the ways to harden SSH protocol on Ubuntu is to use private and public keys instead passwords.

First go to ssh directory on your ubuntu client machine:

cd ~/.ssh

Then generate ssh keys on your client machine as the user, not as a root:

ssh-keygen -t dsa (Keep the defaults by just pressing enter a few times.)

Next step is to copy the public (very important!) key to the server machine:


Then go to your server (still sing password since the keys are not properly set up yet):


Go to ssh directory on your server:

cd ~/.ssh

Now is the time to put the content of the client public key to the authorized_keys file on the server. We will do this with ‘cat’ command:

cat >> authorized_keys

For security purposes we will remove client’s public key file from the server since we don’t need it anymore:


Finally it is time to test the hardened SSH protocol. Go to your client machine and try to connect to the server

ssh username@server

If you have done everything correctly the password prompt will not be displayed and you will be directly connected to your server.

Well done!

Juniper NC on ubuntu

To install Network Connect on your fresh Ubuntu installation follow these steps:

update the system:

sudo apt-get update

To make NC work you have to install those packages:

sudo apt-get install -y openjdk-7-jre; apt-get install -y openjdk-7-jdk; apt-get install -y icedtea-7-plugin

And then reboot the system

sudo reboot

In case your  network connect does not work execute this command:

sudo update-alternatives --config java 

and choose opensource java version:


Now everything should work and you will be able to connect to your VPN.

Shellshock – Critical bash vulnerability

Unfortunately all UNIX based systems are affected by this new vulnerability. Make sure you follow the steps listed in this manual to patch your system.

Here are instructions how to do this:

1. Open terminal on your Ubuntu/Debian/Redhat/Fedora/CentOS

2. Check if your system is vulnerable (auto update might have updated it for you already). To perform this run the following command in your CLI:

env VAR=’() { :;}; echo Bash is vulnerable!’ bash -c “echo Bash Test”


If you get this output, then your system is vulnerable




If you only get this, then your system is patched:



3. Update the bash to the newest security patches

3a.  Ubuntu/Debian: Run this command

sudo apt-get update && sudo apt-get install –only-upgrade bash

3b. CentOS / Red Hat / Fedora command:

sudo yum update bash

4. Recheck your system with this command:

env VAR=’() { :;}; echo Bash is vulnerable!’ bash -c “echo Bash Test”

5. You should get only this response:



Congratulations! Your system is patched!

MS Office in Ubuntu

Since I started working in IT I was using Linux Ubuntu as my main OS and a Windows virtual machine to prepare Excel, Word and Visio documents. I was a bit of hassle with two machines.

There is an easier solution: run MS Office in ubuntu – it is called wine

How to install MS Office on Ubuntu?

Go to Ubuntu software center, type in “wine” and find it on the list

How to install MS office on ubuntu with use of ubuntu software centre.

In the picture above button “Remove” is displayed. In your case it is going to be “Install” since you do not have wine installed yet.

Now when wine is installed the EXE files are recognised by Ubuntu:

How to install MS office with use of EXE file on ubuntu

It is time to double click the setup.exe icon and follow the installation process as usual in Windows.

When the software is successfully installed you can find EXE files here:

/home/user/.wine/drive_c/Program\ Files/Microsoft\ Office/

Fully functional MS Visio in Ubuntu 1204 looks like that:

MS office Visio fully functional and working on Ubuntu.

MS Word:

Fully functional MS Office Word in Linux Ubuntu 1204.

And MS Excel:

Ubuntu 1204 with fully functional MS Office Excel

So you no longer have to ask yourself How to run MS Office in Ubuntu?

testing quickpress

Penetration testing is our core capability, but we also do: PCI Compliance Testing; We are fully conversant with the technical security requirements for PCI. We are up to date with version 2.0 of the PCI standard as well as the Point to Point Encryption standard released in September 2011.

There are two types of penetration tests we provide our clients:
• Application; and
• Hardware/Network.

During an Application penetration test we use the OWASP application testing methodology to manually test each of fields in your application to ensure no vulnerabilities are present which can be exploited to gain unauthorised access. If requested