Archive for Servers

Proxy List Update 24th August 2008

Hi all. Sorry it’s been so long. Here’s another great proxy list update! Long awaited :D

204.131.46.200 anonymous proxy server Aug-24, 07:39 United States
216.240.136.189 anonymous proxy server Aug-24, 06:33 United States
216.217.98.100 anonymous server Aug-24, 02:32 United States
203.82.52.210 anonymous server Aug-24, 07:45 Pakistan
83.246.88.141 anonymous proxy server Aug-24, 05:31 Germany
80.238.136.218 anonymous server Aug-24, 06:31 Switzerland
216.115.24.33 anonymous server Aug-24, 07:38 United States
165.228.71.242 anonymous proxy server Aug-24, 04:05 Australia
69.176.110.37 anonymous proxy server Aug-24, 06:07 United States
203.187.180.169 anonymous server Aug-24, 06:31 China
218.26.219.186 anonymous server Aug-24, 07:43 China
210.151.6.190 anonymous proxy server Aug-24, 07:32 Japan
62.149.67.49 high-anonymous proxy server Aug-24, 08:00 Saudi Arabia
128.163.142.21 high-anonymous server Aug-23, 23:27 United States
138.23.204.133 high-anonymous server Aug-23, 07:15 United States
165.91.83.22 high-anonymous server Aug-23, 14:17 United States
194.36.10.154 high-anonymous server Aug-24, 01:32 United Kingdom
131.175.17.9 high-anonymous proxy server Aug-23, 13:32 Italy
147.102.3.101 high-anonymous proxy server Aug-22, 22:16 Greece
133.1.74.162 high-anonymous proxy server Aug-23, 06:00 Japan
194.36.10.154 high-anonymous server Aug-24, 01:32 United Kingdom
128.112.139.97 high-anonymous server Aug-24, 01:32 United States
128.112.139.80 high-anonymous proxy server Aug-24, 01:32 United States
152.3.138.2 high-anonymous server Aug-23, 22:07 United States
128.232.103.201 high-anonymous proxy server Aug-24, 01:35 United
155.98.35.2 high-anonymous proxy server Aug-23, 16:34 United States
128.163.142.21 high-anonymous proxy server Aug-24, 00:17 United States
128.151.65.101 high-anonymous server Aug-24, 06:17 United States
169.229.50.6 high-anonymous server Aug-24, 06:17 United States
128.238.88.64 high-anonymous server Aug-24, 03:17 United States
128.31.1.11 high-anonymous proxy server Aug-24, 03:57 United States
155.225.2.72 high-anonymous proxy server Aug-24, 04:47 United States
132.239.17.224 high-anonymous server Aug-24, 03:17 United States
128.111.52.62 high-anonymous server Aug-24, 03:17 United States
155.225.2.72 high-anonymous proxy server Aug-24, 03:57 United States
129.59.88.179 high-anonymous server Aug-24, 03:18 United States
152.3.138.3 high-anonymous server Aug-23, 23:26 United States
128.252.19.21 high-anonymous proxy server Aug-24, 01:48 United States
128.113.226.236 high-anonymous server Aug-24, 01:34 United States
128.232.103.203 high-anonymous server Aug-24, 01:33 United Kingdom
124.225.65.38 high-anonymous proxy server Aug-24, 07:20 China
80.63.1.213 high-anonymous server Aug-24, 04:36 Denmark
141.24.249.129 high-anonymous proxy server Aug-22, 22:16 Germany
129.174.79.249 high-anonymous proxy server Aug-23, 18:48 United States
128.2.223.63 high-anonymous proxy server Aug-24, 00:18 United States
128.4.36.11 high-anonymous server Aug-24, 06:17 United States
165.230.49.115 high-anonymous server Aug-24, 00:12 United States
117.74.97.174 high-anonymous server Aug-24, 05:03 Australia
124.225.65.39 high-anonymous proxy server Aug-24, 07:54 China
92.54.100.45 high-anonymous server Aug-24, 07:35
141.213.4.202 high-anonymous server Aug-24, 03:17 United States
124.225.65.173 high-anonymous proxy server Aug-24, 07:54 China
12.162.0.162 high-anonymous proxy server Aug-24, 03:30 United States
221.11.172.93 high-anonymous server Aug-24, 07:53 China
72.55.191.6 high-anonymous proxy server Aug-24, 04:30 Canada
203.158.221.226 high-anonymous proxy server Aug-23, 20:48 Thailand
87.118.102.77 high-anonymous proxy server Aug-23, 14:19 Germany
216.191.142.126 high-anonymous proxy server Aug-24, 04:37 Canada
86.0.175.163 high-anonymous server Aug-23, 20:28 United Kingdom
165.91.83.22 high-anonymous server Aug-23, 21:28 United States
151.100.59.10 high-anonymous server Aug-23, 13:35 Italy
129.69.210.97 high-anonymous proxy server Aug-23, 02:02 Germany
195.130.121.204 high-anonymous server Aug-22, 22:41 Greece
151.100.59.10 high-anonymous server Aug-23, 13:31 Italy
128.223.8.111 high-anonymous proxy server Aug-23, 08:37 United States
128.112.139.71 high-anonymous proxy server Aug-23, 08:36 United States
192.33.90.66 high-anonymous proxy server Aug-22, 22:35 Switzerland
193.55.112.41 high-anonymous proxy server Aug-23, 17:13 France
208.117.131.116 high-anonymous proxy server Aug-22, 23:29 United
149.169.227.129 high-anonymous server Aug-24, 01:38 United States
61.153.145.106 high-anonymous proxy server Aug-24, 06:33 China
193.174.67.186 high-anonymous server Aug-24, 02:11 Germany
212.91.166.210 high-anonymous server Aug-24, 06:31 Bulgaria
62.189.240.130 high-anonymous proxy server Aug-24, 01:35 United
129.174.79.248 high-anonymous server Aug-23, 08:07 United States
192.42.43.23 high-anonymous proxy server Aug-24, 00:28 Switzerland
195.113.161.82 high-anonymous proxy server Aug-23, 13:33 Czech
85.13.205.154 high-anonymous proxy server Aug-23, 20:04 United Kingdom
66.244.214.230 high-anonymous server Aug-23, 18:04 Canada
221.11.172.91 high-anonymous server Aug-24, 07:48 China
128.2.223.65 high-anonymous proxy server Aug-24, 03:57 United States
128.113.226.235 high-anonymous server Aug-24, 06:16 United States
128.113.226.235 high-anonymous server Aug-24, 06:16 United States

Comments (1)

Howto: Securely tunnel via SSH to browse www websites over http

Hi guys, welcome to what you’ve been searching the internet frantically for. Say wa? A no-nonsense guide to anonymous, secure & encrypted port forwarding via SSH tunneling. I will tell you how in just 3 easy steps.

Step 1

Open putty, Goto the Connection-> SSH-> Tunnels and type in 7070 for source port (you can use any port but we use 7070 for this example). Do not enter a destination, but make sure `Dynamic` and `Auto` option buttons are selected like the picture below.
Securely tunnel via SSH to browse www websites

Right once you’ve done the above it should look like:
Securely tunnel via SSH to browse www websites over http
Notes: `Dynamic` option is set, after clicking add D7070 appears in `forwarded ports`. Thats perfect. Well done. Give yourself a pat on the back. Simple. Isn’t it?

Step 2

After how much of a breeze step 1 is, all that is left is you deciding which linux box you’d like to use to connect to via SSH. For my example I include a fictional machine mybox.reallyrocks.com with the default SSH port of 22. In order to feel special about yourself and save you doing this all again enter in a name to save the session. I’ve put “Spechial SSH tunnelz for webz and ting” just so it is darn clear whats going on there. Ok, see below.
Securely tunnel via SSH to browse www websites over http

What I didn’t tell you in this guide was howto click the Open button, because to setup an encrypted SSH-2 (SHA-2) connection that tunnels via a secure linux box is already so easy. I figured it’d be an insult mentioning it.

Step 3: Add your proxy settings in firefox and go crazy.

Now maybe i’ll get that job I’ve always wanted. *cough*. As if. I’m going to use firefox as an example on how to use this bloody tunnel you’ve just setup, you’re probably wondering. Not to worry, this is easier than clicking “Open”.

Script `kiddies` may say? wa wa wa whatcha type in though. Well I typed in 127.0.0.1 and the 7070 and selected the option socks v5. comon, simple things. So, Enjoy simplicity. Everybody else is so god damned cryptic about setting up tunnels and the truth of this is, anyone could do it. Yes, thats right now everything you do VIA the WWW is encrypted. The only thing that isnt is the DNS which is the thing that says where the server is. “what is google? google is 68.8.0.3 etc - thats what the DNS does”.
Securely tunnel via SSH to browse www websites in firefox

My oh My, Easy.

Peace,
A

Comments (2)

Using KVM or kqemu to speed up qemu ( Virtualizing server operating systems)

Have you ever wanted to play with a new distro without having to burn and then reboot into a liveCD or do an install into a spare partition that you may or may not have? QEMU has been an option for awhile but it is slow. There are several options available to run up a virtual machine, i.e. a second operating system running inside and seperate from your already running operating system. Here we will be focusing on kqemu and kvm.

If your kernel is already 2.6.20 or higher you can run kvm, if not then you will have to use kqemu.

kvm is in sid/unstable so you will have to add that to your apt sources if you’re using someting different.

Become root and edit your sources list:

nano /etc/apt/sources.list

add this:

deb http://ftp.debian.org/debian unstable

Now update by running :

apt-get update
aptitude install kvm

After kvm and associated packages are installed it would be best to edit your sources.list again and comment out the line where you added in unstable with a “#” character at the beginning of the line.

kqemu, which is technically a qemu accelerator instead of kernel level virtualization, like kvm, is available in Debian stable and therefor as easy to install as:

aptitude install kqemu

You should have noticed if it wasn’t already installed that qemu was installed regardless of whether you went with kvm or kqemu. Thats because both packages use qemu. So no worries, we need the qemu tools anyway.

If you installed kqemu then we need to load that module when we boot. Become root again and then run:

echo kqemu >> /etc/modules

For kvm you need to know something whether you have an Intel or an AMD processor. You’ll need to load a processor-specific module to take advantage of the system.

If you have an Intel processor you will need to load kvm-intel, for AMD processors you’ll need to load kvm-amd. The module can again be added to /etc/modules.

Now that we have the modules ready to load, we need to make them accessible to you as a user.

adduser $USER kvm
adduser $USER kqemu

(Only one of thse commands needs to be run; it depends which program you installed.)

Congratulations, right now you should have everything just about ready to go. The problem is, even if you modprobe the modules active right now they still wont be usable to you, they need to be loaded against the kernel when you boot, so bookmark this page and reboot your computer, I’ll wait here while you do.

OK so now we need to create a virtual drive to install our test distro to. I’ll explain the parts of it after. From here on out everything is applicable to QEMU, Kqemu, and KVM. It is done as a normal user, so no more need to be root.

qemu-img create debian.img -f qcow 5G

The first bit is self explanatory, create an image (virtual drive) named debian.img. The next bit “-f qcow” tells it to format it in an inflatable structure. The 5G means a maximum physical size of 5 gig real hard drive space. The nice thing about this format is, if your VM installed only takes up 2.5 gig, then the virtual drive only takes up 2.5 gig of space on your real hard drive.

I guess the next thing that you’ll be wanting to do is actually spin this up and try it out. I should note that I have had problems on occasion with KVM locking up during the install process, if this should happen to you drop back and use qemu with the same command line arguments. If you are using kqemu instead of kvm use qemu in the command line instead of kvm, kqemu is a module called by qemu when it starts. I’ll be using kvm for the command line, you use what works for you.

I’m not ready yet to tell you how to start. A few things first if you don’t mind. I usually make a seperate directory for my VM’s because there are usually one or two files other than just the .img file. Such as an overlay file or two, which I will cover shortly and a script that simplifies launching the VM after its made. There are tons of command line arguments that can be added to the basic ones I am using here to get you started, the script is a huge time saver.

There are two basic ways to start this off, either with an .iso image or a CD/DVD. Lets start with an .iso image, the debian net-inst image in this case. We will assume for the sake of argument that the .iso is in the same folder as the virtual drive that you created is, and that it is also our working directory.

kvm -cdrom net-inst.iso -hda debian.img -m 512 -boot d

First this calls kvm and tells it that the .iso image is actually a CD-drive, then the “-hda debian.img” is its hard drive. The “-m 512″ tells it that its a computer with 512 meg of memory. Careful here because this is the amount of physical memory that its going to block out for itself. Rule of thumb is no more than 1/2 of your actual physical memory. The final bit is -boot d, it tells it to boot from the cdrom drive.

kvm -cdrom /dev/cdrom -hda debian.img -m 512 -boot d

The only difference here is that you’re pointing it to your real cd drive here. If /dev/cdrom doesn’t work for you then you can “cat /etc/fstab” and look there to see what you cdrom drive really is.

Now I mentioned that you might have problems doing an install using kvm, if this happens you have to explicitly tell qemu to not use the kvm module in the command line like this:

qemu -no-kvm -cdrom /dev/cdrom -hda debian.img -m 512 -boot d

Lets move on with the thought that you have installed your new virtual operating system. You’re going to want to get in and play with it. The command for this is simply:

kvm -hda debian.img -m 512

With that you will be up and running in your new OS running inside your existing. However there is another trick that is really handy that will let you do whatever you want without permanently breaking this new creation, overlay files. Which basically takes a snapshot of your virtual drive and then run it from the overlay instead of the virtual drive. Really handy if you want to have several versions accessible but only have to do the install process once. Say like having a version of stable a version of testing and a version of unstable all available from the same install. To do this its as simple as:

qemu-img create -b debian.img -f qcow stable.ovl

To boot into this you just change the command line a little bit and tell it to use the overlay file you just made.

kvm -hda stable.ovl -m 512

As you can see the easy way to run multiple versions off the same install would be to do a base install of stable and then make your overlay file for it. Next you would make an overlay file named something like testing.ovl and another for unstable.ovl all from the debian.img that we made to start.

Then simply fire each up in turn via the overlay files, edit your /etc/sources.list to what ever you want and update yourself into debian nirvana.

My thanks to Scott Ruecker over at lxer.com for asking the question that started the process for this how-to. As I said though there are tons of switches that will add functionality to your virtual machine. More than I can adequately explain as I haven’t managed to figure them all out yet either. This how to was written with the whole intent to get someone armed and dangerous before kicking them out the door and isn’t intended to be all inclusive.

For more information on this topic you can start at the qemu homepage.+

Original Source of Article: Debian-Administration

Comments