wibubox table

Crypt(0x00000000): 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 * Crypt(0x00000001): 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
 * Crypt(0x00000000): 6d7fa111ad3795760c7e8d5de6d01b5cdfcf145bd8
 * Crypt(0x00000001): 933da02f2096f768b3e90d28dadcfefb07af2bce34
 * Crypt(0x00000000): 6d7fa111ad3795760c7e8d5de6d01b5cdfcf145bd8
 * Crypt(0x00000001): 933da02f2096f768b3e90d28dadcfefb07af2bce34
 * Crypt(0x00000000): 8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d8d
 * Crypt(0x00000001): efefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefefef
 * ulProgramCount: 0x00000001
 * ulConfig: 0x00000000
 * usAsicBuild: 0x0f1c
 * usExtMemSize: 0x0000

i solve first pair of crypt and get valid R+L+PLAIN LEFT KEY
Problem is second pair bfox said need table emulation
can any one extract q/r
or help continue emulation
regards

you need extract q/r from your target software or usb trace log on the dongle

yes possible like,

Code:

//--------------------------------------------------------
BOOL SearchInTables(UCHAR * In, UCHAR * Out, ULONG Length)
   //--------------------------------------------------------
{
   UCHAR Out16[] = {0};
   BOOL Result = FALSE;
   int I;

   switch(Length)
   {
   case 0x08:
      for(I = 0; I < (sizeof(Q8)/sizeof(UCHAR)); I += 8)
      {
         if( MemCmp(In, Q8 + I, 8))
         {
            MemCopy(A8 + I, Out, 8);
            return TRUE;
         }
      }
      break;
   case 0x10:
      for(I = 0; I < (sizeof(Q16)/sizeof(UCHAR)); I += 16)
      {
         if( MemCmp(In, Q16 + I, 16))
         {
            MemCopy(A16 + I, Out, 16);
            return TRUE;
         }
      }
      break;
   case 0x14:
      for(I = 0; I < (sizeof(Q20)/sizeof(UCHAR)); I += 20)
      {
         if( MemCmp(In, Q20 + I, 20))
         {
            MemCopy(A20 + I, Out, 20);
            return TRUE;
         }
      }
      break;
   }

   Result = FALSE;

   return Result;
}


Ovis you can decode tracelog? 
And my wibubox 6 source can handle this q/a?

no public missing this and other features.

Johnvb wrote:Ovis you can decode tracelog? 
And my wibubox 6 source can handle this q/a?

all q/a in trace is visible. as plain text. you need open your eye's and power up your brain =)

bfox 
i will post log here and  open my eyes with your help   ?

as you wish

heyfox
this is trace log ucan check it for query and response

[You must be registered and logged in to see this link.]
you say that doesnt need decode ?

Ovis thanks very much
In source there query/answer 16 and querie/answer 20 
Which different between them?

your software use RED type q/r - just check : the dongle is present. no more

--------- Request # 57 ----[OUT]----
** Data **
14 54 4D 55 47 5A 4E 4E 54 56 4C 43 42 51 42 4F 57 51 4C 53 44

--------- Request # 64 ----[IN]----
** Data **
00 D9 D3 E7 C2 58 7B A8 50 0D 61 8E 23 3B 1C D4 2D 0C 3B DD D7

--------- Request # 73 ----[OUT]----
** Data **
14 D9 D3 E7 C2 58 7B A8 50 0D 61 8E 23 3B 1C D4 2D 0C 3B DD D7

--------- Request # 80 ----[IN]----
** Data **
00 54 4D 55 47 5A 4E 4E 54 56 4C 43 42 51 42 4F 57 51 4C 53 44

max length is 256 bytes

Yes ur right 
Those q/r must be in q/a 16 or 20 in source??
Or other thing?

the first byte of q is q/r length (01..255). try to understand your wibu-kit

RED - Random Encryption/Decryption.
first stage: wibu crypt2 q0-> a0, second stage wibu crypt2 a0 -> q1, three stage is compare q0 and q1

RID - Required Information Decryption
used in wibu-shell and data encryption/decryption