Question:
1) what algorithm use for master key? Why input 2 block 64 char (64 bytes)
, but result is 8 char hex (4 bytes)
2) Similar for Pin working key? Why input 32 char, but result is 8 char
3) How to extract pin block cipher ? how to they do?
Thank and regards
-----
----Cheer :drunk: ---
mail: queo...@gmail.com
Yahoo: queo1987
--
View this message in context: http://old.nabble.com/PIN-Master-Key%2C-and-PIN-Working-KEY-at-ATM-tp27070509p27070509.html
Sent from the jPOS - Users mailing list archive at Nabble.com.
--
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to jpos-...@googlegroups.com
To unsubscribe, send email to jpos-users+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/jpos-users
Iso Format 0 (ISO 9564-1)
PAN = 1234 5678 9012 3456
PIN = 1234
Get of this from PAN A = 4 5678 9012 345 FFF (wrong) ==> A = 0000 5678
9012 3456
And re-format PIN B = 0000 1234 FFFF FFFF (wrong) ==> B = 0412 34FF
FFFF FFFF
Get Final PIN block = A XOR B
That is my mind.
Thank and regard.
>> jpos-users+...@googlegroups.com<jpos-users%2Bunsu...@googlegroups.com>
>> For more options, visit this group at
>> http://groups.google.com/group/jpos-users
>>
>
> --
> You received this message because you are subscribed to the "jPOS Users"
> group.
> Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
> To post to this group, send email to jpos-...@googlegroups.com
> To unsubscribe, send email to jpos-users+...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/jpos-users
>
-----
----Cheer :drunk: ---
mail: queo...@gmail.com
Yahoo: queo1987
--
View this message in context: http://old.nabble.com/PIN-Master-Key%2C-and-PIN-Working-KEY-at-ATM-tp27070509p27071845.html
For testing, no problem. When I say testing that means, test ATM, test
HSM (or software), test plastics, test money and test keys too.
Cryptography performed outside of a secure environment in a production
environment is just bad and must be avoided at all costs - a companies
reputation and financial standing would be placed at risk.
Although a security audit would find it and *fail* the system, the
'chance' of an audit should never be a consideration...
... Production Data == HSM.
--
Mark