Skip to content

Latest commit

 

History

History
25 lines (15 loc) · 1.08 KB

class-notes-5-29.md

File metadata and controls

25 lines (15 loc) · 1.08 KB

OS II Class Notes

Exploration 9

Do the math to determine if this is a valid credit card number (the last digit 5 is the checksum!):

4485 0803 6191 2635

(For the record, even if it is valid, it's not real!)

4 4 8 5 0 8 0 3 6 1 9 1 2 6 3 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 <--- double every other digit starting with the rightmost digit ======= ======= ======= ===== 8 4 16 5 0 8 0 3 12 1 18 1 4 6 6 <--- sum the digits of the doubled numbers 8 4 7 5 0 8 0 3 3 1 9 1 4 6 6

The sum of the resulting digits is 65. The check digit is equal to 10 - (65 mod 10) = 10 - 5 = 5.

4485 0803 6191 2635 = 4485 0803 6191 2635 (valid!!)

Why is adding together all the bytes and then modding by 256 not a good checksum? What errors could be introduced that the checksum wouldn't catch?

This is not a good checksum because it is limited in the types of errors it can detect. For example, if two bytes are swapped the same checksum would be generated leading to an undetected error. Additionally, the checksum can't detect other forms of transposition because the sum would be the same.