Floola is a freeware application to efficiently manage your iPod or your Motorola mobile phone (any model supporting iTunes). It’s a standalone application that can be run directly from your iPod and needs no installation under Linux, Mac OS X and Windows (Windows Vista is supported).
Step 1. Get it from:
http://www.floola.com/modules/wiwimod/index.php?page=download_linux
Step 2. Before running make sure to install c++ standard library:
sudo apt-get install libstdc++5
Step 3. DONE!
add these two in /etc/apt/sources.list
deb http://ppa.launchpad.net/awn-core/ubuntu/ hardy main
deb-src http://ppa.launchpad.net/awn-core/ubuntu/ hardy main
sudo apt-get update
sudo apt-get install awn-manager-trunk awn-extras-applets-trunk
1. Add “deb http://archive.canonical.com/ubuntu feisty-commercial main” to /etc/apt/source.list
2. sudo apt-get update
3. sudo apt-get install opera
Make sure to have only one “auto” interface, as it will be the main one
If you have “auto eth0″ as well, then once “eth0″ is unplugged “eth1″ will be also unreachable
edit network interfaces configuration:
vi /etc/network/interfaces
here is what to put in:
auto eth1 iface eth1 inet dhcp wireless-essid YourESSIDName wireless-channel 10 wireless-key ##########################
to make it get a static IP, do this instead of the above:
# The primary network interface # connect to wirless network on startup auto eth1 # eth1 Interface iface eth1 inet static address 10.7.1.99 netmask 255.255.255.0 network 10.7.1.0 broadcast 10.7.1.255 gateway 10.7.1.1 wireless-essid YourESSIDName wireless-channel 10 wireless-key ##########################
Have you ever tried to communicate with somebody/something through any kind of technology? Most of the time “those” people/systems like privacy, in a way that they like their communication with everybody including you to be private. Hence once you want to communicate with them they give you something called a “public key” ( or “public-key certificate” ) and ask you to give them yours. Usually when you talk to different sources, nobody would guide you through on how to create that “public key” of yours, “they” would just want it, but you would be left alone to figure out how you should generate it.
Hence this little guide will show you one of many ways on how to generate a pair of X.509 public/private keys, and how to access this magic pair to get that “public key”, so it can be given to anyone who needs it.
First, let us throw a couple of sentences on how these keys are used. It is actually very simple – there is “YOU” and “THEY”:
Now when YOU and THEY have each others public keys and their own private keys communication may begin:
Told you it is very simple!
Now let’s see how to do the magic – how to generate a pair of YOUR public and private keys.
There are number of ways – tools/libraries/code snippets/etc.. I would show you one of the simplest ways how this can be archived using a tool called… any guess? Yes – a “keytool” – make sense, right?
“keytool” is a java tool that has a great manual, and since its java – it’ll work on any OS that has JVM. In order to get/download a keytool, you just have to install Java (JRE) on your system (95% that you already have it installed, hence you can go ahead and use “keytool” without needing to install/download anything else).
Examples here are run on Linux (Ubuntu), but as long as you have Java installed, it does not really matter what OS you have to get the job done.
So, fire up the terminal (Windows’ “cmd”) and let’s generate a pair of public/private keys now:
$ keytool -genkey -alias otherguy -keypass p@ssw0rd -keystore our.keystore Enter key store password: ksp@ssw0rd You are about to enter information that will be incorporated into your certificate request. This information is what is called a Distinguished Name or DN. There are quite a few fields but you can use supplied default values, displayed between brackets, by just hitting <Enter>, or blank the field by entering the <.> character before hitting <Enter>. Common Name (hostname, IP, or your name): myname Organization Name (company) [The Sample Company]: my company Organizational Unit Name (department, division): department of departments Locality Name (city, district) [Sydney]: gorodok State or Province Name (full name) [NSW]: state of new noisy Country Name (2 letter code) [AU]: zz
As you might figured already, a keystore is a small database, that we just created, that would hold all the keys (private/public) for many systems – right now we only have one pair, but later we can add more keys to the keystore. So let’s look at this keystore that we just generated:
$ ls -l total 4 -rw-r--r-- 1 user group 1641 2008-04-22 20:46 our.keystore
But now you need to be able to access this “database” to get a public key, so you can share it with others. It is done by exporting this public key – again, very simple:
$ keytool -export -rfc -alias otherguy -file us-to-otherguy.cer -keystore our.keystore Enter key store password: ksp@ssw0rd
let’s see what files we have now:
$ ls -l total 8 -rw-r--r-- 1 user group 1641 2008-04-22 20:46 our.keystore -rw-r--r-- 1 user group 1189 2008-04-22 20:48 us-to-otherguy.cer
And here it is (!) your public key certificate – “us-to-otherguy.cer”. Let’s see what’s inside:
$ cat us-to-otherguy.cer -----BEGIN CERTIFICATE----- MIIDQjCCAwGgAwIBAAIBATAJBgcqhkjOOAQDMIGGMQ8wDQYDVQQDDAZteW5hbWUxEzARBgNVBAoM Cm15IGNvbXBhbnkxIjAgBgNVBAsMGWRlcGFydG1lbnQgb2YgZGVwYXJ0bWVudHMxEDAOBgNVBAcM B2dvcm9kb2sxGzAZBgNVBAgMEnN0YXRlIG9mIG5ldyBub2lzeTELMAkGA1UEBgwCenowHhcNMDgw NDIzMDA0NjM4WhcNMDgwNzIyMDA0NjM4WjCBhjEPMA0GA1UEAwwGbXluYW1lMRMwEQYDVQQKDApt eSBjb21wYW55MSIwIAYDVQQLDBlkZXBhcnRtZW50IG9mIGRlcGFydG1lbnRzMRAwDgYDVQQHDAdn b3JvZG9rMRswGQYDVQQIDBJzdGF0ZSBvZiBuZXcgbm9pc3kxCzAJBgNVBAYMAnp6MIIBuDCCASwG ByqGSM44BAEwggEfAoGBAP1/U4EddRIpUt9KnC7s5Of2EbdSPO9EAMMeP4C2USZpRV1AIlH7WT2N WPq/xfW6MPbLm1Vs14E7gB00b/JmYLdrmVClpJ+f6AR7ECLCT7up1/63xhv4O1fnxqimFQ8E+4P2 08UewwI1VBNaFpEy9nXzrith1yrv8iIDGZ3RSAHHAhUAl2BQjxUjC8yykrmCouuEC/BYHPUCgYEA 9+GghdabPd7LvKtcNrhXuXmUr7v6OuqC+VdMCz0HgmdRWVeOutRZT+ZxBxCBgLRJFnEj6EwoFhO3 zwkyjMim4TwWeotUfI0o4KOuHiuzpnWRbqN/C/ohNWLx+2J6ASQ7zKTxvqhRkImog9/hWuWfBpKL Zl6Ae1UlZAFMO/7PSSoDgYUAAoGBAPDA5E5GVGzMBw3IWldpyGBs8Dwr7ArYdNRIPH7veELcENhO 7jNdBinJ/JUCcY0XoIhNVXVNkyABpGsBISfGPwgv1meyLcs0DK6ndEDBYGH0Cwoahhtb7EBhcqWQ kqojyVtPRdNTPd8cyPDjbOOapv65+8Xe0FQoCtJXWiwF8Z17MAkGByqGSM44BAMDMAAwLQIVAJHL 9Syzc8LIEp6uNjVI+f/ox4dhAhQOug96d7B5V/rGytlAJiml9f8Qqg== -----END CERTIFICATE-----
that is exactly what you send to everybody else to encrypt their secret messages!
The last thing that I want to show you is how to see what’s inside the keytore database:
$ keytool -list -v -keystore our.keystore Enter key store password: ksp@ssw0rd Key store type: gkr Key store provider: GNU-CRYPTO Key store contains 1 entry(ies) Alias name: otherguy Creation timestamp: Tuesday April 22, 2008 AD - 8:46:38;616 o`clock PM EDT Entry type: key-entry Certificate chain length: 1 Certificate[1]: Owner: CN=myname,O=my company,OU=department of departments,L=gorodok,ST=state of new noisy,C=zz Issuer: CN=myname,O=my company,OU=department of departments,L=gorodok,ST=state of new noisy,C=zz Serial number: 1 Valid from: Wednesday April 23, 2008 AD - 1:46:59;989 o`clock AM EDT until: Tuesday July 22, 2008 AD - 1:46:59;990 o`clock AM EDT Certificate fingerprints MD5: BB:35:C0:6B:D0:B2:67:26:BF:AB:AD:5A:87:51:AA:32 SHA-160: 19:67:F9:8B:DF:52:24:4A:61:4D:76:1C:79:2E:4B:5B:8E:A8:AA:E1 *******************************************
Here you can see that a public certificate that we exported is ” Valid from: Wednesday April 23, 2008 until: Tuesday July 22, 2008″, hence 90 days. That means it will need to be changed in 90 days, which would also, of course mean you would have to issue a new certificate to all your contacts in 90 days. In order to change this time frame, when generating a keystore, just add a “-validity <number of days>”when generating keys:
$ keytool -genkey -alias otherguy -keypass p@ssw0rd -keystore our.keystore -validity 3600
that would create a pair valid for 3600 days from the current date.
What if somebody wants to share secret with you? Well, now you are ready! 
Microsoft Windows (any flavor) is known to be very secretive and dishonest when it comes to telling its user/client/owner what is taking up sooo much system resources, and answer the question “why is my Windows so slow?“.
If you take a closer look at your Windows system you will notice that many CPU cycles and megabytes of RAM belongs to the process with very non-descriptive name “svchost.exe“. You can go to windows task manager by pressing “Ctrl+Alt+Del” and choosing task manager (if it does not come up by itself), or by running “taskmgr” command in your run window “Start -> Run” (more about the second approach in this arcticle “Windows Commands: Think You Know It All !?“). So here is an example of a Windows Task Manager:
(click on “Processes” tab to get to the same view)
This is a snapshot of a “clean” Windows that has just started with NO custom applications running (well besides “mspaint.exe” to get a snapshot, which is ultra small). And already you can see there are 6(!) “svchost.exe” processes that take up RAM and will take up a lot of CPU when you start your Internet Browser, e-mail client, MS Office, Games, etc…
But if you ask what these “svchost.exe” processes responsible for, who started them, and who is their owner, Windows will say: “You are an average Windows user, we exposed everything you need through window managers, if you are unhappy, well.. tough luck”. And that happens to most of people who use Windows, because most people who are technical enough will use something like Linux or if budget allows people would go for Mac.
So here is a simple howto, for all people who are still on Windows, on identifying and disabling owners of “svchost.exe”.
To see the owners follow these two simple steps:
)You should see something similar to the picture below:
Now you can actually see the “services” that are hidden behind this meaningless name “svchost.exe”. Well, that is one step forward, but now what?
Now you can go to Windows Service manager and read about each service that is using “svchost.exe”. Let’s do together:
After you press “Enter”, you should see windows services manager:
Browsing through the services you can read their description and decide whether or not you want the service to run.
There is another quicker way to enable/disable services, but without their descriptions:
After pressing “Enter”, you should see “System Configuration Utility”:
Click on “services” tab to get the above view. As you can see you can “check/uncheck” desired services to change their state from “Running” to “Stopped”. But if you unfamiliar with a particular service, read its description first in “windows services manager”, or google it, if it is not there.
Keep up a “clean” and fast Windows system, and good luck!
Here is how to configure X11 forwarding with ssh.
Takes under a minute to configure:
1. On the SERVER: set “X11Forwarding yes” in your
/etc/ssh/sshd_config
2. On the SERVER in the USER’s home dir:
sudo rm -f .Xauth*
3. On the client:
ssh -2 -4 -C -X -v USER@SERVER
4. Once logged in to the SERVER run “xclock” to confirm
done
# [ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo “You live”
* You either live or …. rm -rf /
Lately it has become a very painful experience for many people (according to forums/articles/open tickets) to add new launchers to Avant Window Navigator. I have taken a look at it and figured out a rather hacky approach to make it work.
First I will manually create a "desktop" launcher.
( If you already have one, open it with any text editor (vi, gedit, etc..) and make sure it follows the structure of my "desktop" launcher )
In order to create the launcher, I have to know two things:
– the path to the file we would like to launch
– the path to the icon we would like to use
In this example, I am going to create a launcher to some program called Aptana, in your case it may be any other program. I know that Aptana executable file is located here: "/opt/aptana/Aptana". I also found an icon I would like to use for it, and put it here: "/home/user/icons/aptana_48x48.png".
Now by knowing two these things, I can open my favorite text editor (vi, gedit, your favorite.. ) and type the following:
[Desktop Entry] Encoding=UTF-8 Version=1.0 Type=Application Terminal=false Name[en_US]=aptana Exec=/opt/aptana/Aptana Comment[en_US]=+ RadRails Icon[en_US]=/home/user/icons/aptana_48x48.png Name=aptana Comment=+ RadRails Icon=/home/user/icons/aptana_48x48.png
Notice the Exec and Icon parameters are populated with those two things. Name and Comment can be whichever you’d like them to be, in this case I just like them to make sense.
Now I will save the file (you can save it on your desktop, or anywhere you want your launchers to live) as "aptana.desktop" (permissions could be "-rw-r–r–", or you can make it less restrictive if you like).
And.. I am ready for the final step "drag & drop" (!). For this I go to the directory where I saved the "aptana.desktop" file using Nautilus/Konqueror/Other GUI browser, click on the file, drag it to Avant’s launcher bar, and drop it there. Tam tam tam – it is there -> I am done! So do you!
Make sure your "desktop" file is the format shown above, since it is tested and works.
According to Ubuntu once Ubuntu 7.10 (Gutsy Gibbon) is out, there will be plenty to celebrate, whether you were directly involved in the release process or just rejoice because the next iteration of the best distribution is finally out.
Thursday, 18th of October ’2007 is the tentative date for Ubuntu 7.10. Many parties will be on this date, or you can pick your own date! Go ahead and put down your favorite pub, park or cafe and celebrate getting Gutsy Gibbon out of the door!
get it while its hot
Come and join Ubuntu parties all over the Globe! The schedule of already "Confirmed Parties" are here.
picture’s source
