Well, when you press a key on your keyboard, the keyboard microcontroller sends the key code (the scan code) to the PIC which generates an interrupt (irq) to the microprocessor and tells it a key is ready. The BIOS (real mode) or the OS (protected mode) then converts that keycode to an ASCII value, which is readily processed by normal applications. That's how if you have a keyboard with extended ASCII values, that still generates the same scan code as it's native PC/AT counterpart, the OS knows whether or not to use the extended ASCII value or the normal ASCII values based on the keyboard layout loaded. You could change the scan code -> ASCII code lookup table to mess with someones head. If they would press the letter x (keycode 0x22, ASCII 0x78) and you map keycode 0x22 to ASCII 0x79, the letter "y" would appear.
So, those could be scan codes (doubt it), ASCII codes, or something else. I doubt it would be either as scan code 1 is the F9 key & ASCII value 1 is SOH (start of header). Both these are non-readable (as in displayable) characters that would be used for the password.
1. What context is this password in?
2. Where did you arrive with those "key" values?
3. How can verify the validity of those key values?