Advertisement
Guest User

Untitled

a guest
Feb 19th, 2018
83
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.23 KB | None | 0 0
  1. Ricardo Linck 9:23am
  2. Hi Chris Fuller Chris , yes it makes sense.
  3. The problem is that that's how we generate the TR-31 block currently. And using another KSN is not guarantee that the injection is going to work. We tried with the one that is working C7E32DF7DF57F0900000 and we couldn't inject the block on the device.
  4. Chris Fuller
  5. 11:34am
  6. Ricardo Linck Ricardo , in order for KSN's with a transaction counter of 0 to work, it would require a Firmware change on our end. The way it is currently set up is based around the current standard. If this is something you would like us to investigate further to gather timelines and work load for such a change, I will work with the engineers to find out more information.
  7. Today
  8. Ricardo Linck
  9. Ricardo Linck 2:04am
  10. I'm not sure about that Chris Fuller Chris . Even if we change that part of the TR-31 block generation, we don't know if it's going to work. I'm going to investigate further about the DateCs process, because I think they have a "custom" TR-31 block. The code we use to generate the TR-31 was provided by DateCs a long time ago. What I've noticed is that the DateCs' TR-31 block is 104 characters long, whereas Virtucrypt's one is either 96 (without BO) or 120 (with BO) characters long.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement