Ye blog of Adam Wright

DIY, tutorials, stuff for geeks, all updated when I have the time to spare.

How To Fix “Server refused our key” Error in CentOS 6

I recently fired up a CentOS 6 VPS for debugging and testing some remote stuff. However, when I tried using an SSH key to remotely login, I was stopped with the dreaded “Server refused our key” error that we’ve all seen when we mess up an SSH key or use a PuttyGen-created public key rather than copy/pasting the OpenSSH key contents into authorized_keys like we should (don’t act like you’ve never done it).

So I triple-checked everything and even used ssh-keygen on the server to create the keys rather than using PuttyGen, but it still wouldn’t work. As I was Googling around searching for answers, I noticed people using a restorecon command and the “PermitRootLogin without-password” setting in their sshd_config file for enabling root login via passwordless keys. An example post can be found here.

Turns out the restorecon command is what we need to use. I don’t know much about the command but it’s man-page says it “restore file(s) default SELinux security contexts”.

After running this on my server, I was able to login as user adam with a password-less SSH key:

restorecon -R -v /home/adam/.ssh

I’m honestly not sure what the resetorecon command does, but I know its what’s needed to make password-less SSH keys work for user adam. If you want to login as root with a password-less SSH key, then you’d run this command:

restorecon -R -v /root/.ssh

As a note, I’m unsure if this is just CentOS 6 or not, but a friend that uses CentOS 5.x said that he has never had to use the restorecon command to get SSH keys to work, so it might be a new standard feature found in the release notes of CentOS 6.


How To Password Protect A Directory In Dropbox Or Other Cloud Storage

Let’s face it, most of the stuff you keep in Dropbox aren’t important. No one will be trying to guess your password for your archive of gifs and lolcat pics. However, you might have some sensitive data such as personal pictures or legal documents. Here are a couple of the simplest methods to protect your sensitive data. These methods are based on protecting individual directories/folders, so they should work for any cloud storage solution such as Dropbox, Skydrive, Google Drive, SugarSync, etc.

Method #1 – Simple password-protected folder compression

The easiest method of password protecting a directory is to compress it as a ZIP file with a password.

  1. In Linux Mint, and most other Ubuntu derivatives and Windows, there should be an entry in the right-click menu to compress a file or folder such as this:
    Screenshot from 2013-03-29 14:51:56
  2. Compress the folder as a ZIP file and set a password.
    Screenshot from 2013-03-29 14:56:44
  3. Now you have a password protected ZIP file of the folder. No one can open, see, or edit any of the files in the folder without knowing the password.
    Screenshot from 2013-03-29 14:58:18

Now just delete the uncompressed folder. Each time you need to edit or see files in the folder you’ll have to unzip it, and rezip it when you’re done.

Method #2 – Encrypting the directory

Using TrueCrypt, you can securely encrypt the directory with a password. With this method, the directory can be mounted as a drive anytime you’d like to use it. Then you can add, remove, or alter files as you want before unmounting it. I chose TrueCrypt because they have clients for Windows, Mac, and Linux. I will be covering its installation and use in Linux, but the method should be similar for Windows as well.

  1. Download the TrueCrypt package from their website: TrueCrypt.
  2. Install TrueCrypt byextracting and running the shell script.
  3. Once its finished installing, start TrueCrypt and click “Create Volume”
    Screenshot from 2013-03-29 15:55:48
  4. Select “Create an encrypted file container”
    Screenshot from 2013-03-29 15:56:03
  5. Select “Standard TrueCrypt volume”
    Screenshot from 2013-03-29 15:56:08
  6. Choose where you want to save the encrypted volume. It will appear as a single file once its created.
    Screenshot from 2013-03-29 16:26:11
  7. Choose the encryption algorithm and hash algorithm you’d like.
    Screenshot from 2013-03-29 16:32:38
  8. Choose how big you’d like the make the encrypted volume. The file will appear this big at all times, even if you leave it empty. So, be careful how big you make the volume file depending on how much space of your Dropbox account you’re willing to give up.
    Screenshot from 2013-03-29 16:32:47
  9.  Choose your password.
    Screenshot from 2013-03-29 16:32:56
  10. Choose the filesystem type you’d like to use. If you plan on using the files within the encrypted volume in Windows, you might want to select FAT rather than Ext2/3.
    Screenshot from 2013-03-29 16:33:05
  11. On the next screen you should move your mouse around a little to randomize the header and master keys, then click “Format” to start formatting and encrypting the volume. In my experience, it takes somewhere around one minute per gigabyte.
    Screenshot from 2013-03-29 16:33:24
  12. Screenshot from 2013-03-29 16:34:36Now you can mount the encrypted volume you’ve created by clicking “Select File…”, selecting the file, and clicking “Mount”.
    Screenshot from 2013-03-29 16:39:48
  13. Put in the password for the encrypted volume. You should also see a popup asking for your machine’s root password for permissions to mount the volume.
    Screenshot from 2013-03-29 16:40:00
  14. The volume is now mounted (just like a USB flash drive; you can see it on the left side).
    Screenshot from 2013-03-29 16:40:19
  15. You can put any files in the volume that you want to keep encrypted.
    Screenshot from 2013-03-29 16:41:48

To dismount the volume, you must either right-click the volume from within the TrueCrypt window and selecting “Dismount” or by clicking the “Dismount All” button. Simply unmounting the volume like you would a USB drive (such as clicking the little eject icon on the menu on the left) will not unmount the encryption, so you will be able to remount it without inputting a password. For this reason, be sure to dismount the volume via TrueCrypt.

How To Successfully Install Wine PPA In Linux Mint 14

After installing Linux Mint 14, I attempted to install Wine by adding the Wine PPA to my software sources. However, when I tried updating I got this error:

Err nadia/main Sources
404 Not Found

Notice that the word after the PPA location is “nadia”. This is the codename for Linux Mint 14, not the codename for the version of Ubuntu that it is based off of, which is what needs to go there.

To fix this, you just need to manually edit your /etc/apt/sources.list.d/ubuntu-wine-ppa-nadia.list file. My command-line editor of choice for quick edits is nano:

Screenshot from 2013-03-24 17:43:13

Replace the two “nadia” words with “quantal” (Linux Mint 14 “nadia” is based off of Ubuntu 12.10, and the codename for Ubuntu 12.10 is “quantal”).

Screenshot from 2013-03-24 17:40:44

Save and try updating again (“sudo apt-get update”) and it should update fine. You should now be able to install Wine fine.

Simple explanation of why this happens:
Normally, when adding a PPA to an Ubuntu or Ubuntu-based Linux distribution, aptitude adds the codename of the system to the line it adds in the sources.list entry so that the packages are pulled from the correct repositories (i.e. “quantal”, “precise”, etc.). It seems that the creators of Linux Mint decided to rebrand every aspect of the Ubuntu operating system to match the Linux Mint details, and in doing so changed the internal Ubuntu-based codename of the distribution to the Linux Mint codename. For this reason, aptitude tries to use the Linux Mint codename rather than the Ubuntu one and then aptitude fails when searching the Ubuntu repositories for the Linux Mint codename.

This is the first I’ve seen this problem, but I imagine its fairly common among Mint users installing packages via PPAs added via software sources.

WineHQ – Installing the latest Wine on Ubuntu.

How to print multiple files at once in Linux


So you’ve got a folder full of PDF files that you want to print. You hilight all of them and right-click, but there’s no “Print” or “Send to printer…” option. There are probably ways out there to add this option to your right-click menu, but a quick and dirty way is to use the command line using the lpr command. This is useful if you just need to print multiple files once in a blue moon. I mean, how often do you print 5 PDFs at once? Furthermore, how often do you print nowadays?

Here’s the command:

lpr *.pdf

That’s it. The lpr command sends files to your default printer for printing. In the above example, I sent all PDF files in my current folder to my printer. If you only want to send a few PDF files, or maybe multiple format files like .txt, .pdf, etc., then just do this:

  1. Once you have all the files you want to print hilighted, copy and paste them into a new empty folder.
  2. Navigate to that folder via command line/terminal.
  3. Print all the files in that folder: “lpr *”


I have only tested the lpr command with PDF files and it worked perfectly, but I suspect it should work with any file format that your system recognizes. For this reason I assume it should work for office documents, pictures, etc.

How To Disable Pidgin’s Annoying Facebook Notifications

By default, Pidgin supports Facebook Chat accounts, but, also by default, it shows desktop notifications whenever someone logs in or out. With Facebook Chat, that happens A LOT. It took me a little online searching to find out how to disable them, so I figured I’d make it easier for you:

  1. Open Pidgin plugins and scroll to “Libnotify Popups”
  2. Disable “Buddy signs on”
    Screenshot-Libnotify Popups

The plugin isn’t easy to find visually because it doesn’t use the word “notifications” at all.

%d bloggers like this: