To get the Samsung Galaxy S working with the Android SDK in Ubuntu, some setup is needed, else you'll be getting errors like this:

? adb devices
List of devices attached
????????????	no permissions

I did these on a Ubuntu Lucid Lynx, but this should work for other versions/distro of Linux too I think.

1)
Change to root

? sudo -

2)
Create the needed file. 04e8 refers to the Vendor ID for the Samsung manufacturer.

# echo 'SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"' >> /etc/udev/rules.d/51-android.rules

3)
Restart the udev service

# /etc/init.d/udev restart

4)
Plug in the phone (make sure debugging mode is already enabled), and run adb as needed

? adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[device-id]    device

Hope this helps whoever needs this.

You need to install the geoip-bin package in Ubuntu/Debian's APT system:

sudo apt-get install geoip-bin

Then after which, lookups can be done as simply as:

$ geoiplookup 8.8.8.8
GeoIP Country Edition: US, United States

Note that the lookups are based on the GeoLite Country database.  For more detailed geoip lookups you will need to buy the better databases.

Taking a search through Ubuntu's APT system, to see whether any IDN related tools are available...

$ apt-cache search punycode

libidn11 - GNU Libidn library, implementation of IETF IDN specifications
libidn11-dev - Development files for GNU Libidn, an IDN library
idn - Command line and Emacs interface to GNU Libidn
libidn11-java - Java port of the GNU Libidn library, an IDN implementation
libidna-punycode-perl - encodes Unicode string in Punycode

There's the idn package!  Which allows encoding of IDNs in punycode in the command line...

Doing an install...

$ sudo apt-get install idn -y

And trying it out!

$ idn правительство.рф

libidn 1.15
Copyright 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Simon Josefsson.
GNU Libidn comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of GNU Libidn under the terms of
the GNU Lesser General Public License.  For more information
about these matters, see the file named COPYING.LIB.
xn--80aealotwbjpid2k.xn--p1ai

And resolving the domain...

$ nslookup xn--80aealotwbjpid2k.xn--p1ai

Non-authoritative answer:
Name:	xn--80aealotwbjpid2k.xn--p1ai
Address: 95.173.135.62

Note that resolving the domain directly results in rubbish!

$ nslookup правительство.рф

Non-authoritative answer:
Name:	\208\191\209\128\208\176\208\178\208\184\209\130\208\181\208\187\209\140\209\129\209\130\208\178\208\190.\209\128\209\132
Address: 67.215.65.132

So, basically from this we understand that applications will need to use the punycode encoded version of the IDN, NOT the original IDN, when resolving.  And there're tools out there already can do that for us.

Since Ubuntu has these packages, Debian would also have the corresponding packages available too.

It's basically an Ubuntu 8.04 server on a VMware 6.5 image, running plenty of old and vulnerable services.  Yummy!

It is available to Metasploit Express customers from the Customer Center, and for the rest of us peeps, it's freely available for download via Bittorrent. (a bit slow, but I'll try to seed this for as long as possible when I managed to get it entirely)

More info at the blog post.

[via Metasploit Blog]

Apparently it can be done on any linux terminal, as long as you have the correct version of apt or aptitude installed, so give it a try and enjoy!

The commands that can be run are:

• apt-get moo
• aptitude moo
• aptitude moo -v
• aptitude moo -vv
• aptitude moo -vvv
• aptitude moo -vvvv
• aptitude moo -vvvvv
• aptitude moo -vvvvvv

I wanted to run the victim machines in VirtualBox instead of VMware Player, and after some experimentation and Googling around with the crashing issue, here're the instructions on how to get things up and running.

Host OS: Ubuntu 9.10
VirtualBox 3.1.2
Guest OS: Ubuntu 7.04 Server

Steps:

1. Get only the server ISO, not the virtual machine. http://old-releases.ubuntu.com/releases/feisty/ubuntu-7.04-server-i386.iso

2. Add it into the list of CD/DVD images within the Virtual Media Manager in VirtualBox.

3. Create a new virtual machine with the following settings:
Name: (up to you)
Operation System: Linux
Version: Ubuntu
Base Memory Size: (up to you, the defaults of 384MB was ok for me)
Boot Hard Disk: (up to you, create new or select pre-existing one)

4. Select the new virtual machine, then click on Settings to edit the settings for this virtual machine (duh).

5. Goto System > Processor. Check the box labelled "Enable PAE/NX". This is needed for this to work.

6. Goto the Storage section, select the "Empty" CD/DVD item, then select the 7.04 ISO you added earlier in step 1. This will be needed for your install...

7. Goto the Network section. Adapter 1 should be enabled for you already, change "Attached to" from "NAT" to "Host-only Adapter". I do this since we want a vulnerable server and not get the latest updates. If you have different needs set this option accordingly.

8. Edit any other hardware options as you wish and then press "Ok".

9. Start the virtual machine, it should boot up to the CD ISO. Follow the steps for installing the ISO into the virtual disk. If you're using "Host-only Adapter" as shown in step 7, it will prompt a bit with regards to empty route, no nameservers and no proxy. This is normal, leave as blank and continue.

10. There! I (hopefully) can haz vulnerable server!

Do leave a comment if this has helped, or if you have any other questions which I'll answer if I can, heh.

--------------------------------

References:

1. Offensive Security's walkthrough on Metasploit: Metasploit Unleashed > 02 Required Materials > Ubuntu 7.04

2. Ubuntu 7.04 Server Crashes when booting: ... do a default install of Ububtu 7.04 Server. When install is complete, immediately after booting Ubuntu crashes: Int 14: CR2 c1000000 err 00000002 EIP c03f3c3e CS 00000060 flags 00000006 Stack: 373c0046 00000000 ffffffff c0490000 00001400 00000080 00400000 ffffff80

apt-get install

or

aptitude install

command, and you get

WARNING: The following packages cannot be authenticated!

running

sudo aptitude reinstall ubuntu-keyring

might do the trick~

[via Fool's Wisdom]

ovpn-openvpn[3552]: /etc/openvpn/update-resolv-conf tun0 1500 1542 x.x.x.x x.x.x.x init
ovpn-openvpn[3552]: script failed: external program exited with error status: 1

A quick trace of the update-resolv-conf script shows that the problem's with resolvconf:

resolvconf: Error: /etc/resolv.conf must be a symlink

And the fix for that based on another solution:

sudo rm /etc/resolv.conf
sudo ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf