Powered by Twitter Tools.
Powered by Twitter Tools.
Powered by Twitter Tools.
You need to run a list of commands on a list of servers and record the output of each command.
Create a perl script using Net::SSH::Perl ( a ssh client written as a perl module ). This script will read a list of commands from a file, a list of servers form another file, will connect to each server, execute each command in in the commands file then go to the next server and do the same.
Installation
Download the script: [download#8]
install Net::SSH::Perl
Now you can decompress the script and configure it
put the commands in commands.txt ( one command per line )
put the servers in servers.txt (one per line ) in this format: user@hostname:port,password
Now you can test the script: run ./ssh_batch.pl and look at the output in log.txt
Yeah it can do that if you're not carefull about what commands you tell it to run and you log in with a user with too much permissions. So make sure you know what you are doing before you run it on production servers.
You transfer files over scp or sftp to a server and there you have a script that processes the new files. you want the script to only start processing the files once they are completely transferred.
There's no way of knowing when the files have been fully transferred, both sftp and scp would create the files as soon as the transfer begins and will close then when it finishes. So between the time it creates them and until it closes them the files are incomplete.
There's an easy solution: upload a lock file before you start uploading the real files and remove the lock file after the upload is finished. Modify your processing program/script to look for a lock file and only start processing if the lock file does not exist. This is good if you can modify the upload and processing scripts/programs but that's not always the case.
The harder solution involves modification to openssh source code. I created a patch that modifies scp and the sftp server so that for every file received the server will actually put the contents in a temporary file and only move the file in the real destination when/if the upload is complete. The move operation ( rename ) is atomic only when moving the files in the same filesystem but that's not a big problem cause we can configure the tmp location to be on the same filesystem.
Both scp and sftp server were modified so you get similar functionality by using any of them.
This patch was tested with openssh 4.6.p1. It may work with newer versions but first you should try with the same version so download the source code for 4.6p1 and decompress it.
Download my patch: [download#7]
Apply the patch:
Then run configure with whatever parameters you want, make and install it.
By default scp and sftp-server will use /tmp as the temporary location where they save files till the upload is complete.
If /tmp is not on the same filesystem and the actual file destination then you have to specify a different temporary location in order to make this really atomic.
For sftp-server you can do it by adding another parameter to the Subsystem line in sshd_config
It normally looks like this (on gentoo x86_64) :
Subsystem sftp /usr/lib64/misc/sftp-server
or ( on ubuntu 9.04 )
Subsystem sftp /usr/lib/openssh/sftp-server
You have to add " -t /new/tmp/location " to that line ( without the quotes )
/new/tmp/location should be on the same filesystem as the real destination.
For example if you have /home mounted on a separate partition and you upload in /home/user you should create a temporary folder in /home and set that as the folder to be used by sftp-server.
And the configuration line should be something like :
Subsystem sftp /usr/lib/openssh/sftp-server -t /home/tmp
Scp also needs special configuration if you want to set a different temporary location but in this case we could not just pass a special parameter to it because the scp client would not allow that so I had to make a wrapper for the scp program on the server.
The wrapper would just pass the custom temporary location in a environment variable then call the actual ( patched ) scp program.
I had scp in /usr/bin/scp so I moved that in /usr/bin/scp.bin
and I created a script named /usr/bin/scp with the following content:
all that's left to do is:
That's it! Now you have atomic uploads for scp and sftp.
Powered by Twitter Tools.
This is a quick patch I did to php's source code to implement some special syntax. Basically I wanted to be able to define an array like this:
Get the patch here:Â [download#5]
To get this behavior download php's source code, extract it put my patch in the source directory and do this:
( This will only compile but not install - in case you want that just type make install at the end )
And here's a test script :
Save this script as test.php then run sapi/cli/php test.php
This was tested on php 5.2.6 and 5.2.9. I think this is probably useless for most people but it was fun to write so why not share it 🙂
Last week I was contacted by David Melnichuk to offer me a partnership/affiliate account for his ebook "The Hacker's underground Handbook". I said to David that I would prefer to see what's it all about before I would promote anything, but I would be willing to write a review and maybe promote it if he sends me a copy. He did that so here is my review ...
I recently created the eBook: The Hacker’s Underground Handbook. It is targeted more towards people that are new to the hacking/security scene and still don’t know where to start. Although it is mainly targeted towards newbies, it also has content that will be valuable for intermediate skill levels. The product is completely legal. Once the product is purchased, the user will be taught to not abuse the knowledge gained, and the penalties if he/she chooses too.
After looking over the book briefly I completely agree that this is an ebook for newbies.
Also the phrase "learn what it takes to crack even the most secure systems" from the cover, over estimates the content. You would most likely not be able to crack the most secure systems only with the information in this book, but the author advices the reader to learn more and not rely only on the information in the book and even provides some links to more resources.
I think the term hacker applies more to someone like Richard Stallman, Alan Cox, Linus Torvalds, etc then to someone like Kevin Mitnik. So in my opinion the book is more about cracking then hacking, but most people(newbies) don't know the difference so I'm not going to insist on this.
The book covers topics from installing a linux distribution (with screenshots a la howtoforge ) and password cracking to packet sniffing, using exploits, web site cracking, wifi cracking and social engineering ( which IMO is not really cracking but just a nerdier/l33t word for "lying" )
I like the fact that the book also offers some advices / countermeasures even if in some cases it doesn't present the most secure or all options.
If you're into cracking and you already know how to do a lot of stuff I would not recommend the book as there are no advanced techniques in the book but if you're new to this or you would just like to know how some things are done and how you can prevent some security incidents then the book offers a good collection of common cracking techniques.
The ebook comes with a bonus ebook named "1000 Hacking Tutorials Leaked", so for the price of $18.89 is probably a very good deal.
Click here to get the ebook ( yeah that's my affiliate link )
Have you read this book? I'd love to read your impressions about it in the comments.
Powered by Twitter Tools.