Hacking CA system challenge *Tandberg [ NO Keys Allowed in Chat Section/s ]*

S

Stejc

Donating Member
Messages
185
Anubis_Ir said:
The 1st byte of the posted AES keys is the actual index of the key and shouldn't be used as part of the actual key.
For example if you have this key
Code: 
<Struct N="key#2" V="01XYXYXYXYXYXYXYXYXYXYXYXYXYXYXYXYD152"/>
Ignore the first byte (1st 2 characters), Then the actual AES-KEY01 would be XYXYXYXYXYXYXYXYXYXYXYXYXYXYXYXY. And you can get consecutive DCW's with it (which means the algo is correct), but without picture.


@Those who work with `CSA Rainbow tables`. Can you get working CWs of these channels lately?
Can you search these values in tables B8xFF or B8x00? 779B1CA2582FA0F7 and 0FEB5AAE7AC18AD0 for this file
_https://mega.nz/#!19AiFKQQ!xdjfQVpreWI4epkXFC-CRlSBg_Qt9pKTsWuBvAASErg
Click to expand...

Could CUDABISS be used to get a working CW on this file? I've run it through the packet TS file and get this input.txt, happy to share the work with some others though?

000000000000
FFFFFF000000
4749C5D3E6C121AA87C71B0BD93D0F5A
4749C5D187693A8E15D4B48F75DCAB2A
4749C5DFFB7AB9BAB516C0D8F5C5F148
1
1
 
A

Anubis_Ir

Registered
Messages
370
Stejc said:
Could CUDABISS be used to get a working CW on this file? I've run it through the packet TS file and get this input.txt, happy to share the work with some others though?

000000000000
FFFFFF000000
4749C5D3E6C121AA87C71B0BD93D0F5A
4749C5D187693A8E15D4B48F75DCAB2A
4749C5DFFB7AB9BAB516C0D8F5C5F148
1
1
Click to expand...
Hi, Yes. CUDABISS can be used too.
 
M

Martin.Wigston

Registered
Messages
973
Stejc said:
Could CUDABISS be used to get a working CW on this file? I've run it through the packet TS file and get this input.txt, happy to share the work with some others though?

000000000000
FFFFFF000000
4749C5D3E6C121AA87C71B0BD93D0F5A
4749C5D187693A8E15D4B48F75DCAB2A
4749C5DFFB7AB9BAB516C0D8F5C5F148
1
1
Click to expand...

I dont mind helping if others do, mine isnt the fastest GPU but not the slowest either. We just need to divide up the ranges.

EDIT: Will there be 2 keys an odd and even?
 
Last edited:
S

Stejc

Donating Member
Messages
185
Martin.Wigston said:
I dont mind helping if others do, mine isnt the fastest GPU but not the slowest either. We just need to divide up the ranges.

EDIT: Will there be 2 keys an odd and even?
Click to expand...

I've started at 000000000000. Maybe you could start at 800000 000000? Then we can split further with someone starting at 400000 000000 and then B00000 000000.

I'll leave on all night tonight and post again where I am up to in the morning.
 
M

Martin.Wigston

Registered
Messages
973
sss146 said:
BruteForce (Cudabiss) failed. I wrote about this earlier.
CSA64 or other encryption used.
Click to expand...

Stejc said:
I've started at 000000000000. Maybe you could start at 800000 000000? Then we can split further with someone starting at 400000 000000 and then B00000 000000.

I'll leave on all night tonight and post again where I am up to in the morning.
Click to expand...

Ok I think it's best we hold fire, no point wasting our time and electricity if it's already been attempted.

I dont even know if Cudabiss can find ccw with odd and even parity keys, it certainly looks that way from crypt8's
 
O

ooOO_SORGOS_OOoo

Tandberg_V1.3.1

Tandberg.mdl V1.3.1

not working 42E-10E-7E

Anubis_Ir said:
This is the new `bin\.mdl` file for vPlug (+ full source code) and supports the new nanoEC. You should copy it to vModules folder.
Notes: It requires a DES key and also an AES key (included too, in the bin folder). Without these `2 keys`, it won't work.

So ...
- Good news: we know how nanoEC works.
- Bad news: It requires 2 keys. 1 DES key and 1 of 32 AES keys which won't be transmitted by the EMMs.

Based on the posted image, AES keys start from index 01 to 20 and not 00 to 1F. Use the attached file.
Click to expand...
 
C

campag5242

That screenshot was most definately FTA or fake.

That apparently working capture with its off-by-one key index led to the confusion re 01-20. The key index runs 0x00..0x1F - there's an '& 0x1F' to extract it from the emm, so it can never be 0x20.
 
A

Anubis_Ir

Registered
Messages
370
An update and closing this thread!

ECM: 80702AEC2800000691FFEA5F07BD6131080498F850F70BD5E8E030BC5A859EE877667971D50EDD8893455D17E3
Analysis
- NanoEC, Mode: EA
- AES overencryption ((Mode & 0x20) != 0)
- No fix checksums of CW(CW 64bytes) ((Mode & 0x40) != 0)
- New Mode of descrambler/It's not the normal CSA ((Mode & 0x80) != 0)

Which means it's now something like PowerVU. PowerVU can use both DES(New Mode of descrambler) and CSA(the normal descrambler) for the final stage.
 
barney115

barney115

Donating Member
Staff member
Administrator
Messages
24,783
So really this is what we should have expected all along ??
Tandberg V3 is not so much different than PowerVU after all ,
It shows us now basically exactly same strategy
Is this not something we should be rather somewhat happy to see ?
This method has been buzzing around my head
all day yesterday and for a few days now
since Testing various AES Keys for quite a few days
and i am real glad you just came out
and just said it @ Anubis_IR ,
I admit its just another major challenge to overcome
But really we have come so very far lately and surely this is something worth fighting for ?
i think obtaining the AES keys was never the main problem to this challenge anyhow : )
 
R

roxthaworld

Donating Member
Messages
46
Gsky claiming to have added V3 support
support.png
[/url][/IMG]
 
H

harshy

Registered
Messages
746
I don’t think that’s what Anubis said, it must behave similar to powervu, maybe it’s now called TandbergVU;)
 
You must log in or register to reply here.
Top