Home
Forums
New posts
Search forums
What's new
New posts
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Home
Forums
CARDING & HACKING
Hacking Tools
TheJerm Best Software + Tutorial For...
Message
<blockquote data-quote="Prime" data-source="post: 937" data-attributes="member: 18"><p>* LED Test</p><p></p><p>This is pretty self-explanatory. Use these buttons to test all the lights on the MSR206.</p><p></p><p>* Batch File Format</p><p></p><p>This lets you configure the program to read your batch text files. The "Example" box shows you how your text files should be formatted so they can be read correctly.</p><p></p><p></p><p><strong>"License/ID" Tab</strong></p><p>________________</p><p></p><p>Fill in all the information of your license or ID and click the "Generate Tracks" button and it will build three tracks and put them in the track boxes on the "Actions" tab so you can write them to a card. The "Import Data" button does the opposite. It will pick out ID data from the track boxes on the "Actions" tab and fill in all the personal information fields on the "License/ID" tab.</p><p></p><p>All the information for encoding license/ID tracks was obtained from the "AAMVA National Standard for the Driver License/Identification Card" document.</p><p></p><p>I didn't include every state on my list. I only put down the states that I have the Issuer Identification Number (IIN) for. That's a six digit number that starts with "636" that identifies the state and is the first entry on track 2. I'm not sure if all the states I included even follow the AAMVA standard.</p><p></p><p>Since I only had the AAMVA document to go by I can't guarantee that the encodings will be 100% accurate. As I get more scans of real ID's I'll be able to determine the format better and I'll make improvements to the program.</p><p></p><p></p><p>"Bank Card" Tab</p><p>_______________</p><p></p><p>When you read a bank card the program automatically gathers and formats all the available data and displays it in the text fields on the "Bank Card" tab. Customer name, account number and expiration date are read directly from the tracks. If the account number prefix matches any of the prefixes in the included database file ("bins.txt") the bank name will also be displayed. The account number is also run through the "Mod 10" formula to see if it's a valid number. The "Check Bank & Mod 10" button lets you check a manually typed in account number for the bank name and validity. </p><p></p><p></p><p>"Reconstruct" Tab</p><p>_________________</p><p></p><p>This feature is useful for recovering some or all of the data from damaged magstripes. When you read a card, all tracks that have errors are automatically sent to this tab.</p><p></p><p>* Track</p><p></p><p>Use these buttons to select which track you want to display and edit. When you select a track number the "Bits Per Character" button currently chosen for that track will automatically be selected and there will be a number of gray textboxes below equal to the number of bits per character. Each textbox should fill with a different variation of the track data and they should all be about the same length. Look at each textbox and try to determine where the valid data is. It may all be in one box or it may be spread out between two or more boxes depending on the type of damage to the magstripe. You can copy the valid data from the gray textboxes and paste it into the white textbox at the bottom and then copy it from there back to the textbox for that track on the "Actions" tab.</p><p></p><p>I'll try to explain the idea behind this function and how it works. First, when you read a card, the program tells the MSR206 to send back only a raw binary dump of the tracks; no formatting is done to it at all. Then the program itself formats the binary data by dividing groups of bits into separate bytes. The MSR206 has four settings for the number of bits used to represent each character: 4, 5, 6 and 7. There are actually only two different character sets: a 4 bits per character set (16 characters) which contains only numbers and a few symbols, and a 6-bit set (64 characters) which has the entire alphabet, numbers, symbols and punctuation. The 5 and 7 bit sets are just the 4 and 6 bit sets with a parity bit added to each byte for error detection.</p><p></p><p>When a magstripe is damaged some of the bits become unreadable. So if your original data was: "111111 000000 101010 111000" and two of the bits got damaged, so it's now: "111111 000??0 101010 111000" the MSR206 may interpret the numbers following the damaged bits as if they were the missing bits and now everything is shifted over two bits like this: "111111 000010 101011 1000..." and every byte after the damaged spot is incorrect. If you add two bits to the beginning of the data it will shift all the bits after the damaged spot back into the right place so they can be read correctly, but now all the bits before the damaged spot are shifted out of place.</p><p></p><p>There's no way for the computer to determine which bits are shifted out of place because it doesn't know where the damage is and doesn't have the intelligence to identify the valid data. So, the program displays all possible variations of the tracks, each one shifted one bit more than the previous, and relies on the user to distinguish the valid data from the garbage and reconstruct the track.</p><p></p><p>* Bits Per Character</p><p></p><p>These buttons let you select how the binary data is divided into bytes, from 4 bits per byte to 7. If you can't find anything that looks like valid data try changing the number of bits per character and see if anything shows up.</p></blockquote><p></p>
[QUOTE="Prime, post: 937, member: 18"] * LED Test This is pretty self-explanatory. Use these buttons to test all the lights on the MSR206. * Batch File Format This lets you configure the program to read your batch text files. The "Example" box shows you how your text files should be formatted so they can be read correctly. [b]"License/ID" Tab[/b] ________________ Fill in all the information of your license or ID and click the "Generate Tracks" button and it will build three tracks and put them in the track boxes on the "Actions" tab so you can write them to a card. The "Import Data" button does the opposite. It will pick out ID data from the track boxes on the "Actions" tab and fill in all the personal information fields on the "License/ID" tab. All the information for encoding license/ID tracks was obtained from the "AAMVA National Standard for the Driver License/Identification Card" document. I didn't include every state on my list. I only put down the states that I have the Issuer Identification Number (IIN) for. That's a six digit number that starts with "636" that identifies the state and is the first entry on track 2. I'm not sure if all the states I included even follow the AAMVA standard. Since I only had the AAMVA document to go by I can't guarantee that the encodings will be 100% accurate. As I get more scans of real ID's I'll be able to determine the format better and I'll make improvements to the program. "Bank Card" Tab _______________ When you read a bank card the program automatically gathers and formats all the available data and displays it in the text fields on the "Bank Card" tab. Customer name, account number and expiration date are read directly from the tracks. If the account number prefix matches any of the prefixes in the included database file ("bins.txt") the bank name will also be displayed. The account number is also run through the "Mod 10" formula to see if it's a valid number. The "Check Bank & Mod 10" button lets you check a manually typed in account number for the bank name and validity. "Reconstruct" Tab _________________ This feature is useful for recovering some or all of the data from damaged magstripes. When you read a card, all tracks that have errors are automatically sent to this tab. * Track Use these buttons to select which track you want to display and edit. When you select a track number the "Bits Per Character" button currently chosen for that track will automatically be selected and there will be a number of gray textboxes below equal to the number of bits per character. Each textbox should fill with a different variation of the track data and they should all be about the same length. Look at each textbox and try to determine where the valid data is. It may all be in one box or it may be spread out between two or more boxes depending on the type of damage to the magstripe. You can copy the valid data from the gray textboxes and paste it into the white textbox at the bottom and then copy it from there back to the textbox for that track on the "Actions" tab. I'll try to explain the idea behind this function and how it works. First, when you read a card, the program tells the MSR206 to send back only a raw binary dump of the tracks; no formatting is done to it at all. Then the program itself formats the binary data by dividing groups of bits into separate bytes. The MSR206 has four settings for the number of bits used to represent each character: 4, 5, 6 and 7. There are actually only two different character sets: a 4 bits per character set (16 characters) which contains only numbers and a few symbols, and a 6-bit set (64 characters) which has the entire alphabet, numbers, symbols and punctuation. The 5 and 7 bit sets are just the 4 and 6 bit sets with a parity bit added to each byte for error detection. When a magstripe is damaged some of the bits become unreadable. So if your original data was: "111111 000000 101010 111000" and two of the bits got damaged, so it's now: "111111 000??0 101010 111000" the MSR206 may interpret the numbers following the damaged bits as if they were the missing bits and now everything is shifted over two bits like this: "111111 000010 101011 1000..." and every byte after the damaged spot is incorrect. If you add two bits to the beginning of the data it will shift all the bits after the damaged spot back into the right place so they can be read correctly, but now all the bits before the damaged spot are shifted out of place. There's no way for the computer to determine which bits are shifted out of place because it doesn't know where the damage is and doesn't have the intelligence to identify the valid data. So, the program displays all possible variations of the tracks, each one shifted one bit more than the previous, and relies on the user to distinguish the valid data from the garbage and reconstruct the track. * Bits Per Character These buttons let you select how the binary data is divided into bytes, from 4 bits per byte to 7. If you can't find anything that looks like valid data try changing the number of bits per character and see if anything shows up. [/QUOTE]
Name
Verification
Post reply
Home
Forums
CARDING & HACKING
Hacking Tools
TheJerm Best Software + Tutorial For...
Top