The new version of Ubuntu, code worded Feisty Fawn, is now available for download. I'm a big fan of Ubuntu, or more correctly the KDE interface variant Kubuntu, so I'm keen to try out the new version. Fesity Fawn contains a bunch of enhancements right across the range of tools and packages contained within the Ubuntu distribution.
Testing will have to wait though, because I'm still woking my way through SimpleMEPIS 6.5.
The new version of Ubuntu, code worded Feisty Fawn, is now available for download. I'm a big fan of Ubuntu, or more correctly the KDE interface variant Kubuntu, so I'm keen to try out the new version. Fesity Fawn contains a bunch of enhancements right across the range of tools and packages contained within the Ubuntu distribution.
Testing will have to wait though, because I'm still woking my way through SimpleMEPIS 6.5.
The new version of Ubuntu, code worded Feisty Fawn, is now available for download. I'm a big fan of Ubuntu, or more correctly the KDE interface variant Kubuntu, so I'm keen to try out the new version. Fesity Fawn contains a bunch of enhancements right across the range of tools and packages contained within the Ubuntu distribution.
Testing will have to wait though, because I'm still woking my way through SimpleMEPIS 6.5.
The new version of Ubuntu, code worded Feisty Fawn, is now available for download. I'm a big fan of Ubuntu, or more correctly the KDE interface variant Kubuntu, so I'm keen to try out the new version. Fesity Fawn contains a bunch of enhancements right across the range of tools and packages contained within the Ubuntu distribution.
Testing will have to wait though, because I'm still woking my way through SimpleMEPIS 6.5.
One of the steps I find myself doing a lot is distributing round an ssh key so that I can login and use different machines automatically. To help in that process I created a small function in my bash profile script (acutally for me it’s in .bash_aliases):
function setremotekey
{
OLDDIR=`pwd`
if [ -z "$1" ]
then
echo Need user@host info
fi
cd $HOME
if [ -e "./.ssh/id_rsa.pub" ]
then
cat ./.ssh/id_rsa.pub |ssh $1 'mkdir -p -m 0700 .ssh && cat >> .ssh/authorized_keys'
else
ssh-keygen -t rsa
cat ./.ssh/id_rsa.pub |ssh $1 'mkdir -p -m 0700 .ssh && cat >> .ssh/authorized_keys'
fi
cd $OLDDIR
}
To use, whenever I want to copy my public key to a remote machine I just have to specify the login and machine:
$ setremotekey mc@narcissus
Then type in my password once, and the the function does the rest.
How? Well it checks to make sure I’ve entered a user/host (or actually just a string of some kind). Then, if I haven’t created a public key before (which I might not have on a new machine), I run the ssh-keygen to create it. Once the key is in place, I output the key text and then use ssh to pipe append that to the remote authorized_keys file, creating the directory along the way if it doesn’t exist.
Short and sweet, but saves me a lot of time.
The story about a wireless hijacking, and this related piece about Two cautioned over wi-fi 'theft' is interesting, but sadly all too easy.
My wi-fi is protected, not only with encryption, but also by restricting by MAC address and deliberately hiding the wi-fi service. However, there are no less than five wifi services from other houses which are neither hidden, nor restrictive, and not one of them requires a password to connect or any type of encryption.
The story about a wireless hijacking, and this related piece about Two cautioned over wi-fi 'theft' is interesting, but sadly all too easy.
My wi-fi is protected, not only with encryption, but also by restricting by MAC address and deliberately hiding the wi-fi service. However, there are no less than five wifi services from other houses which are neither hidden, nor restrictive, and not one of them requires a password to connect or any type of encryption.
The story about a wireless hijacking, and this related piece about Two cautioned over wi-fi 'theft' is interesting, but sadly all too easy.
My wi-fi is protected, not only with encryption, but also by restricting by MAC address and deliberately hiding the wi-fi service. However, there are no less than five wifi services from other houses which are neither hidden, nor restrictive, and not one of them requires a password to connect or any type of encryption.
The story about a wireless hijacking, and this related piece about Two cautioned over wi-fi 'theft' is interesting, but sadly all too easy.
My wi-fi is protected, not only with encryption, but also by restricting by MAC address and deliberately hiding the wi-fi service. However, there are no less than five wifi services from other houses which are neither hidden, nor restrictive, and not one of them requires a password to connect or any type of encryption.
The story about a wireless hijacking, and this related piece about Two cautioned over wi-fi 'theft' is interesting, but sadly all too easy.
My wi-fi is protected, not only with encryption, but also by restricting by MAC address and deliberately hiding the wi-fi service. However, there are no less than five wifi services from other houses which are neither hidden, nor restrictive, and not one of them requires a password to connect or any type of encryption.