begood

RFIDIOt is an open source python library for exploring RFID devices. It's called "RFIDIOt" for two reasons: 1. I like puns. This one stands for "RFID IO tools" 2. Since I haven't done any serious programming for a long time, I felt like an idiot having to learn a whole new language and the code probably looks like it's written by an idiot. However, python rocks, so it was worth it! What does it do? It currently drives a range of RFID readers made by ACG, called the HF Dual ISO and HF Multi ISO, which are both 13.56MHz devices, and the LF MultiTag which is 125/134.2kHz. Frosch Hitag reader/writers are also now supported. There's no reason it couldn't work with others, these are just the first ones I got my hands on, and since they present themselves to the O/S as standard serial devices without having to install any drivers, it made interfacing very simple (but see the Technical Note section below as I've had some issues recently). I have written some example programs to read/write tags and have started on the library routines to handle the data structures of specific tags like MIFARE®. It is far from complete but I thought I'd follow the "publish early, publish often" philosophy on this one... PC/SC (MUSCLE) devices, such as the Omnikey CardMan are also supported. I am curently testing with a CardMan 5321. RFIDIOt.org - RFID IO tools

Contents 1. How to make cracking your app a little bit harder... [upd:24-Feb-2k] 2. More tips you might take into consideration... [upd:24-Feb-2k] 3. Advanced tips given by Assembler freaks... [upd:06-Aug-99] 4. Special on Delphi reverse engineering... 5. Some notes on registration numbers... [upd:06-Aug-99] 6. Some notes on timebombs... [new:14-Jan-2k] 7. How to find cracks for your apps... [new:21-Apr-2k] 8. What to do if you found a crack for your app... [upd:19-Aug-99] 9. Facts and Myths about Software pirating... 10. Thoughts and letters from crackers [upd:24-Sep-2k] 11. Links of interest... [upd:16-Aug-2k] 12. Visitor comments... [upd:22-Apr-2007] Finding out that the program on which you worked for months or years has been cracked can really hurt and demotivate. For me as a Shareware programmer, the reason has never been that I've lost a few cents (I don't want to do propability calculations here, it might hurt even more..), no, it was simply that I've always tried to hold my programs as cheap as possible to make them affordable for everyone, even for students or freeware programmers. Somehow I can understand the fascination of cracking programs (if you are absolutely intolerant about software crackers and hackers, please excuse, but one of my educations is Psychotherapy, and I'm always searching for psychological reasons...) - cracking a restricted software program must be like solving a (sometimes very tricky) riddle, and you might get addicted to the feeling of solving them (I've found that when I saw my grandmother doing crossword puzzles all over the time for some months). The problem is (but at the latest, now we come to the undoubtedly illegal part of the "game"): it doesn't really satisfy the cracker if he is the the only one who knows about his "genius"...thus, he has to spread the news. He has to publish his "crack" (just see most crack packages: in most cases they just consist of: 1. the cracking utility 2. a short description 3. a big text file or even animation containing claims that the producers are nothing less than the most brilliant individuals on Earth and that the cracked program is another one which could not stop them due to "its lame protection scheme".) But now the fun is completely over: by giving out this (let's try to be fair: "study of feasibility") to other people, by spreading it via Websites, newsgroups, mailing lists, anonymous FTP, CDROM "abonnements" and whatever, they clearly damage the business of everyone who puts time and energy in their software product. Even if we assume that typical crackers wouldn't have bought your product under normal circumstances: spreading the "crack" IS criminal and no one could claim that none of the receivers or downloaders would never have bought it. It's just like if someone hands out copies of the key to your car on the marketplace - and it doesn't really matter if he does that for money or not. In earlier days, I have never put real energy in protecting my programs against cracking, but after finding several cracks for them around, I thought to myself: why make it too easy? As a programmer, of course I know that no - really: NO! - program can ever be crack-safe, and I know that of every interesting program sooner or later cracks (or at least pirated or illegally copied versions) will be around, but at least I could try to avoid the worst mistakes. Crackers are not super-geniuses .. they are simple programmers who have learned some techniques to counteract common protection schemes - and if you know where and how crackers are searching, you can make them lose *much* time! And that's what it is about: there is no bullet-proof way to protect your programs, but you can dance on the nerves of those people until they decide for an easier target to "get the feeling"... or even go outside to enjoy the nature instead of sitting in front of the monitor the whole day. ;-) Most of the typical 'high language' programmers don't know Assembler anymore, so the 'protection ideas' they use are in most cases quite weak. I don't know much about Assembler myself, so I decided to open my eyes and started to collect anti-crack protection tips wherever I found them. Also I did my best to "learn from the other side" .. many of the tips you can find here I've found by studying the typical cracking techniques, the various "cracking guides" around the web and by reading protection tips given even by professional crackers themselves (some of them generously give us tips to increase their challenge). Well, I hope I've learned my lessons well enough, but also want to share my experiences with you on this page. Some rules given here were already stated in various essays on other sites, but are listed here for completeness. Many of these apply especially to Windoze, but can be "ported" to other OS'es or anywhere else. PLEASE: * This FAQ is just as good as the experiences that are webbed into it. If you think that I've missed some points or useful tips a typical developer could easily add to his/her programs to improve protection, please let me know. If you allow, then I'll add it here, otherwise I'll inform you about my experiences with it. * Don't ask me questions - might be that I'm simply too overburden to answer. 1) as mentioned, I don't have much knowledge of the low-level stuff. 2) I can't send you demo sources, since I don't have anything ready for a publication. If I have something, you will read it here. 3) finally, I will not provide anyone with any of the URLs where I've found (or found out) some of these tips. Please understand, but this is a site dedicated to programming, but not to provide "step-in's" to available cracks or even to generic "Cracker hunting". But finally, here is.. more : Richey's DELPHI-BOX

e la categoria news ... cine se ocupa de acea pagina si de ce ?

Untitled Document wtf is this ? http://i44.tinypic.com/2925is7.png

Virustotal. MD5: 84365ed2382d3addc9de677c857e4f2a Suspicious.Insight Trojan.Dropper-25545 Trojan.Win32.Malware.1 trojan dropper. Trojan/Agent.cikm Anubis - Analysis Report Performs File Modification and Destruction: The executable modifies and destructs files which are not temporary. Performs Registry Activities: The executable reads and modifies registry values. It may also create and monitor registry keys. @dragosdydy daca nu raspunzi in 24 ore, vei avea ban permanent. nu vad pentru ce ai facut installer. posteaza programul fara setup.

nu-i vorba ca nu esti bine venit, ci pur si simplu nu avem ce comenta, pe noi, nu ne ajuta cu nimic acel program, ne place, probabil ai lucrat enorm la el, respect, altceva ce ai vrea sa iti spunem ? pe scurt nu prezinta interes aici. posteaza pe Hackpedia - Index page SkullBox - Totul despre programare si sisteme de operare astea sunt forumuri de programare. pe al doilea sigur vei primi feedback-ul mult visat. bafta !

tu n-ai umblat in magazine de cand te-ai nascut ? e plin de ele, in toate supermarket-urile. mai ales de genul asta : http://i39.tinypic.com/2agnvxe.jpg pe carti, electrocasnice mici ... tot ce prinzi mai de valoare are cate un RFID tag de genul.

Sunt curios ce rol joaca faptul ca esti singur la parinti sau ba, in inclinatiile spre blackhat / securitate. nota: in poll nu se va afisa nick-ul vostru.

asta l-ai facut pentru fanii tai ? cam...sters

neme are doi de s...

@Fitty nu mai pune cifre, ca n-ai facut tu statistici la nivel national.

da, este.

bashed.ro ?

putin timp.

intro How to block/kill RFID chips In this Instructable I will describe different ways to block or kill RFID tags. RFID stands for Radio Frequency Identification. If you do not know about this technology yet, you should definitely start familiarizing yourself with it, because the number of different devices that utilize these types of tags is growing exponentially. RFID chips are very similar to barcodes in the sense that a certain amount of data is contained within them, and then transmitted to a reading device which then processes and utilizes the information. The major difference is that barcodes have to be physically visible to the reading device, which is usually only able to scan them at a distance of a 12 inches or less. RFID tags, on the other hand, do not have to be visible to the reading device. They can be scanned through clothes, wallets, and even cars. The distance from which they can be read is also much greater than that of a barcode. At DEFCON an RFID tag was scanned at a distance of 69 feet, and that was back in 2005, the possible reading distance now is probably much greater than that. There are a few different categories of RFID tags, but the most common ones, and the ones we will be dealing with in this instructable, are the "passive" type. Passive RFID chips contain no internal power supply. They contain an antenna which is able to have a current induced in it when within range of the RFID reader. The tag then uses that electricity to power the internal chip, which bounces its data back out through the antenna, where it will be picked up by the reader. For more information on RFID tags check out the wikipedia entry. step 1 Reasons for blocking / destroying RFID chips The main reason someone would want to block or destroy RFID chips would be to maintain privacy. In the last step I explained that RFID tags can be read from very long distances. The potential for abuse of this technology grows as more and more products and devices are being created with these tags built in. Companies are getting consumers to blindly accept many RFID tagged products with the promise of convenience; however, most of the devices that contain RFID tags don't really need them. The tags may save a few seconds, but sacrifice an enormous amount of privacy and security. It is now possible for someone, with relatively simple equipment, to walk down a busy sidewalk and pickup the personal information of people carrying RFID tagged devices, without them even knowing. Being able to block or destroy these chips allows people to decide what type of information they are willing to sacrifice for convenience. Reasons for blocking / destroying RFID chips step 2 Where can RFID chips be found As RFID chips become cheaper, the number of devices that include them grows. Currently there are RFID tags in: - US passports: The RFID tag contains all the information that is written in the passport, along with a digital picture - Transportation payments: Things like New York's EZ Pass, Florida's Sun Pass, and California's Fast Trak are all RFID based toll payment systems. - Access control: Many buildings and schools require RFID tagged cards to be used for entry. - Credit cards: Chase, and a few other banks, now issue credit cards embedded with RFID chips, called "blink". They are able to convince people it is an added convenience, but in reality it is a huge security risk. There are many other devices which contain RFID tags; however, the ones listed are the most common and offer the greatest security risk. step 3 How to block a RFID tag Luckily RFID tag signals can easily be blocked. This means that you will have the option to use the tag whenever you want, and prevent others from being able to read it. The signal sent out by a RFID tag is easily blocked by metal. This means that placing the RFID tag inside of a Faraday cage will prevent the information from being read. There are already two Instructables on how to build RFID blocking containers: RFID Secure Wallet Make a RFID Shielding Pouch Out of Trash Or if you would rather spend money on something you could build, head over to Think Geek for their RFID blocking wallet and RFID blocking Passport Holder . step 4 How to kill your RFID chip In this step I will describe a few ways to permanently disable or kill an RFID chip. Most products that you own that contain RFID tags belong to you, so you have the right to destroy them; however, tampering with a US passport is a federal offense. Luckily there are ways to kill an RFID tag without leaving any evidence, so as long as you are careful, it would be pretty hard to prove that you did anything illegal. -The easiest way to kill an RFID, and be sure that it is dead, is to throw it in the microwave for 5 seconds. Doing this will literally melt the chip and antenna making it impossible for the chip to ever be read again. Unfortunately this method has a certain fire risk associated with it. Killing an RFID chip this way will also leave visible evidence that it has been tampered with, making it an unsuitable method for killing the RFID tag in passports. Doing this to a credit card will probably also screw with the magnetic strip on the back making it un-swipeable. -The second, slightly more convert and less damaging, way to kill an RFID tag is by piercing the chip with a knife or other sharp object. This can only be done if you know exactly where the chip is located within the tag. This method also leaves visible evidence of intentional damage done to the chip, so it is unsuitable for passports. -The third method is cutting the antenna very close to the chip. By doing this the chip will have no way of receiving electricity, or transmitting its signal back to the reader. This technique also leaves minimal signs of damage, so it would probably not be a good idea to use this on a passport. -The last (and most covert) method for destroying a RFID tag is to hit it with a hammer. Just pick up any ordinary hammer and give the chip a few swift hard whacks. This will destroy the chip, and leave no evidence that the tag has been tampered with. This method is suitable for destroying the tags in passports, because there will be no proof that you intentionally destroyed the chip. How to kill your RFID chip

@pax e destul sa facem rt's pentru dublu md5, ca apoi poti sparge orice hash simplu si dublu cu acele tabele NTLM inca se cere pentru vista si windows 7 ;-)

Presupun ca prima varianta de tabele (cele de 4TB) vor fi gratuite, inca nu ne-am gandit. Cea de-a doua si a treia vor fi pe bani. A doua va avea in jur de 20TB, iar a treia peste 60TB. Asta daca tinem probabilitatea de succes la 100%. Daca le facem de 99.9% atunci cele de 20TB vor putea incape in 6 TB. Vedem.

Am inceput un proiect gigantic alaturi de inca 2 programatori. (Sc00bz si Bitweasil) Despre ce e vorba : rainbow tables cu probabilitatea de succes de 100% Pentru inceput tabelele vor avea dimensiunea de aproximativ 4 TB. Acestea vor putea sparge urmatoarele tipuri de parole : * - 95 caractere: A-Z, a-z, 0-9, simboluri (32), spatiu M - 62 caractere: A-Z, a-z si 0-9 m - 52 caractere: A-Z si a-z n - 36 caractere: a-z si 0-9 a - 26 caractere: a-z 0 - 10 caractere: 0-9 * ** *** **** ***** MMMMMM Mnnnnnn maaaaaaa 00000000 000000000 0000000000 maaa0000 maaaa000 maaaaa00 maaaaaa0 maaaa0000 Algoritmurile hash suportate : MD5 si NTLM (ne mai gandim daca sa facem pentru md5 dublu care va suporta si MD5 simplu) Niste cifre : -serverul va costa pe putin 4000$, Sc00bz se ocupa de asta. -pentru inceput 4 TB HDD + un SSD de cel putin 18 GB pentru a injumatati timpul de acces al discului. -timp procesare : (16 ms timp acces disc + 8 ms timp procesare) / hash single threaded. expect us !

PenTBox is a Security Suite that packs security and stability testing oriented tools for networks and systems. Programmed in Ruby and oriented to GNU/Linux systems, but compatible with Windows, MacOS and every systems where Ruby works. It is free, licensed under GNU/GPLv3. PenTBox Contains Cryptography tools * Base64 Encoder & Decoder * Multi-Digest (MD5, SHA1, SHA256, SHA384, SHA512) * Hash Password Cracker (MD5, SHA1, SHA256, SHA384, SHA512) * Secure Password Generator * Files en/decryptor Rijndael (AES) 256 bits – GOST – ARC4 Network tools * TCP Flood DoSer * TCP Flood AutoDoSer * Spoofed SYN Flood DoSer [nmap - hping3] * Port scanner * Honeypot * PenTBox Secure Instant Messaging Extra * L33t Sp3@k Converter * Fuzzer An updated list of tools can be found here. You can download PenTBox v1.3.2 here: Windows version (Ruby included) – pentbox_1.3.2_win.zip Linux version – pentbox_1.3.2.tar Or read more here. darknet.org.uk

Security researchers on Friday unveiled an open-source device that captures the traffic of a wide variety of wireless devices, including keyboards, medical devices, and remote controls. Keykeriki version 2 captures the entire data stream sent between wireless devices using a popular series of chips made by Norway-based Nordic Semiconductor. That includes the device addresses and the raw payload being sent between them. The open-source package was developed by researchers of Switzerland-based Dreamlab Technologies and includes complete software, firmware, and schematics for building the $100 sniffer. Keykeriki not only allows researchers or attackers to capture the entire layer 2 frames, it also allows them to send their own unauthorized payloads. That means devices that don't encrypt communications - or don't encrypt them properly - can be forced to cough up sensitive communications or be forced to execute rogue commands. At the CanSecWest conference in Vancouver, Dreamlab Senior Security Expert Thorsten Schroder demonstrated how Keykeriki could be used to attack wireless keyboards sold by Microsoft. The exploit worked because communications in the devices are protected by a weak form of encryption known as xor, which is trivial to break. As a result, he was able to intercept keyboard strokes as they were typed and to remotely send input that executed commands on the attached computer. "Microsoft made it easy for us because they used their own proprietary crypto," Schroder said. "Xor is not a very proper way to secure data." Even when devices employ strong cryptography, Schroder said Keykeriki may still be able to remotely send unauthorized commands using a technique known as a replay attack, in which commands sent previously are recorded and then sent again. The device can also be used to spot weaknesses in cryptographic communications by comparing keystrokes to corresponding ciphertext. His analysis shows wireless keyboards made by Logitech most likely use 128-bit AES encryption. But even so, it may still be possible to decipher the contents by exploiting the way the secret key is exchanged. "We still didn't figure out how to crack that one, but I think it's just a matter of time," he said. Keykeriki, which is the German equivalent of "cock-a-doodle-do," is available here. theregister.co.uk

pwnat, pronounced “poe-nat”, is a tool that allows any number of clients behind NATs to communicate with a server behind a separate NAT with *no* port forwarding and *no* DMZ setup on any routers in order to directly communicate with each other. The server does not need to know anything about the clients trying to connect. Simply put, this is a proxy server that works behind a NAT, even when the client is behind a NAT, without any 3rd party. There is no middle man, no proxy, no 3rd party, no UPnP/STUN/ICE required, no spoofing, and no DNS tricks. More importantly, the client can then connect to any host or port on any remote host or to a fixed host and port decided by the server. pwnat is based off of the UDP tunneling software by Daniel Meekins, udptunnel, and my original chownat. pwnat will work on most *nix operating systems. Tested on Linux and OS X. You can download pwnat v0.2-beta here: pwnat-0.2-beta.tgz Or read more here. darknet.org.uk

imi place

si totusi, din pura curiozitate, la ce foloseai winpcap ?

ce alegeti ? sex sau internet, ce faceti daca aveti voie sa alegeti unu pe viata? //sondajul evident se va adresa celor cu maru in gat, hermafroditii sunt exclusi.

heezor, bine ai venit, cam complicat acel program, unde inveti tu (lic, oras)? si cum de esti atat de pasionat de AI?