Виж само едно мнение
  #2  
Стар 09-11-2009
Аватара на ТИНТИН
ТИНТИН ТИНТИН не е на линия
Модератор
 

Дата на присъединяване: Mar 2009
Мнения: 4,148
Благодари: 362
Получил благодарност:
2,431 пъти в 1,521 поста
Сваляния: 71
Ъплоуди: 0
По подразбиране

) # Carta from our server
C: (cabo hiszpan.dyndns.info 10,015 roberto england 12000 01 02 03 04 05 06 07 08 09 10
11 12 13 14) # card from a friend in spain
And finally type in your cwshare.cfg:
M: (serwer.dyndns.info 1234ABCD ())
D: (peer1.no-ip.info (2233 4455 (3412CDAB (3 3))))
D: (195.354.123.23 (2233 1111 (0123BCDE (A3 A3))))
D: (192.168.0.5 (2233 3322 (FE32BCA6 (A1 A1))))
# Cs2gbox
D: (192.168.0.2 (2233 2230 (DCCB6554 (1 1))))
It is important that the script first started taking off emu or NewCS server, then
cs2gbox and at the end Gbox
It is recommended that you disable the reader, who receives Emu Gbox NewCS and do it in the gbox_cfg
line V:
In cs2gbox we have the opportunity a few settings using the parameter Q:
Q: (01 00 01 00 01 01 01 30 05 3600 05 360 360 1)
where:
00 - does not write information and errors
01 - writes information and error
00 - do not write connections to the server
01 - by connection to the server
00 - not by ECM
01 - by ECM
00 - not by CW
01 - by CW
01 - immediately try to reconnect after losing connection
01 - write on the screen
01 - write in debug.txt
30 - corresponds again after 30 seconds
05 - if you are not successful try after 5 seconds (try only once)
3600 - attempt to connect to the server, not combined every hour (3600 seconds)
05 - the minimum interval between the time attempting to log on
360 - keep the Internet at life through 360 seconds
360 - Ping to cardserwera after 360 seconds after the last ac****ty to keep him
Online
1 - end connection
In cs2gbox providers can also be ignored
whole for all systems except ********:
I: (01 00 00 68) - inactive provider Digits
or individual packages in ********:
I: (05 02 0A 10) - HRT Basic package
Gbox sharing on the use of season'a:
According to the author is Possible Gbox sharing protocol using season'a. (Pure
theory - not proven)
To accomplish this should change the parameter: the gbox_conf
In: (01) XX
Where:
XX - COM port to which is attached Season
Server can be both your computer and dbox, dreambox.
This may be a bad alternative for HDTV with a sort of universal module, because
Those on Linux somehow can not wait to release their ...
With this theme waiting for the season to see this in practice, as the desire to include in
the next update of this FAQ ...
Softcam.cfg
Save data EMM
# 00 does not save anything
# 01 writes processed Emm (/ var / tmp / emmproc.bin)
# 02 saves rejected Emm (/ var / tmp / emmblock.bin)
# 03 saves two EMMY
L: (00)
Checking additional frequencies OSC! dbox only!
# 00 does not check
#> 0 Check on in KHz, example 8MHz = 08,000
F: (0000)
Checking for additional Baurate ATR! only for dbox2!
# 00 does not check
#> 0 Check on in bit / s, for example 81,861
B: (0000)
Enable Support TPScrypt
# * 0 TPScrypt off
# * 1 TPScrypt included
# 1 * not used the PTS on ******** cards
# 2 * not be used on cards Cryptoworks PTS
# 3 * not be used for the PTS ******** and Cryptoworks cards
Y: (01)
RS232 buffer before writing
# 00 do not delete
# 01 delete buffer
E: (01)
SoftCam Blocker in Gbox
#
I: (00 00 00) ****** All SA UA
V: (00 00 00) Via - SA UA
S: (00 00 00) Seca - SA UA
N: (00 00 00) Nagra All SA UA
C: (00 00 00) Crypto All SA UA
A: (00 00 00) ***** - SA UA
D: (00 00 00) *** All SA UA
namely:
00 - block EMM off going to the card
01 - block EMM included going to the card
and an example card irdetto:
I: (All SA UA)
where:
ALL - blocking all card
SA - are passed EMM-y, which go to the group to which we must be cards
UA - are passed EMM-y, which go to the serial number
To enable the blocker to the card Seca should edit the parameter S: (00 01 01)
Definitions Timeout (waiting time)
T: (00 02 01) ATR timeout on the card (normal * X), time to wait for INS
(normal * X)
com1/com2 delays, all the delay serve a preliminary decimal (DEC)!
All synchronization should be 0, change only if we have a
concern.
T: (01 00000 000) ******: bytes delay (1e-6 s), instruction delay (1e-3 s)
T: (02 00000 000) Seca
T: (03 00000 000) ********
T: (04 00000 000) Nagra
T: (05 00000 000) Cryptoworks
T: (06 00000 000) Geldkarte
T: (07 00000 000) *****
T: (08 00000 000) ***
T: (09 00500 000) Dreamcrypt / Firecrypt
When the problem of firing Cyfrowy Polsat cards should change the parameter of delay for
Nagry on:
T: (04 00000 010) Nagra
Use of a bug in Cryptoworks cards to decode any CW, regardless of chid
(chanel ident)
Cxxx configuration (enabled only for the provider, whose line is present in the configuration)
(use of ECM in order to obtain the cw Cxxx)
# Digiturk
8: (C1) A4 4C 00 00 31 28 00 2E 83 01 C1 8C 03 89 19 19 8E 02 00 00 8F 01 A9 91 01 55
DB 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 DF 08 00 00 00 00 00 00 00 00
where:
C1 - provider
19 19 - chid who is currently on the card this provider
Keys constant that is based on constant CW
# 0: (00 00 01 62 (00 11 22 33 44 55 66 77 88 99 AA BB CC DD EE FF)
where:
00 00 This caid
01 62 a sid
00 11 22 33 44 55 66 77 is cw0
88 99 AA BB CC DD EE FF is CW1
Also in this form write keys biss coded system, which benefit from
two identical solid cw
Sample key for SCT Extra
0: (05 00 36 B3 (9D B6, C9-1C 9C E1 D3 50 45 E3 15 3D 36 2E 35 99)
Emulation card - use it only when we have access to private
keys, we can not give them but want to somehow divide them
Sample simulation 007C00 card in slot 1, if you have private keys for that
Platforms
M: (01 (05 00 7C 00))
Simulation of the 4801 card slot 12 (com2, slot2) if you have private keys for that
Platforms
M: (0C (18 01 48 01))
Keys to Gbox:
Crypto (0DXX):
Cryptoworks keys system are saved in a file and share the Crypto Key, OP, RSA
modular System:
OP key save in the form:
K: (0D CE AN ID XX YY (ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ))
Where:
0D XX - provider
CE AA - type of key
ID - ID provider
YY - key number
ZZ - the key consisting of 16 bytes
Distinguished by 4 types of key:
TYPE: CE20 ECM Key
TYPE: CE21 EMM-S Key
TYPE: CE30 EMM-G Key
TYPE: CE20 EMM-C Key
Example:
Keys which have such a provision SoftCam.Key:
In 0D03C0 00 02A2ED9B9E14776D87ECBF3BFE66278F - ECM key 00
In 0D03C0 01 B741ED569EA549478BA4740FC633272B - ECM 01 key
In 0D03C0 80 B752C3BE0BDEEB8A32A3E73E6358F044 - EMM-G 00 Key
In 0D03C0 81 28E3AF36BBC2BC92407DAAC238D12ADF - EMM-G 01 Key
The file is written in the form of crypto:
K: (0D 03 CE 20 C0 00 (02 A2 ED 9B 9E 14 77 6D 87 EC BF 3B FE 66 27 8F))
K: (0D 03 CE 20 C0 01 (B7 41 ED 56 9E A5 49 47 8B A4 74 0F C6 33 27 2B))
K: (0D 03 CE 30 C0 00 (B7 52 C3 BE 0B ED EB 8A 32 A3 E7 3E 63 58 F0 44))
K: (0D 03 CE 30 C0 01 (28 E3 AF C2 BB 36 CB 92 40 7D AA C2 38 D1 2A DF))
RSA is written in modular form:
R: ((ID 0D XX ZZ ZZ ZZ ZZ ...))
Where:
0D XX - provider
ID - ID provider
ZZ - RSA modular, consisting of 64 bytes
Example:
Keys which have such a provision SoftCam.Key:
In 0D03C0 B0 39FA13 ... ... ...
The file is written in the form of crypto:
R: (0D 03 C0 (39 FA 13 ... ...))
The system key is written in the form:
S: 0D XX ((ID ID ID ID (ZZ ZZ ZZ ZZ ZZ ZZ)))
Where:
0D XX - provider
ID - ID of the provider (here Seby not repeat all the key type
IDs as they are known to scratch or leave
ZZ - the key system consisting of 6 bytes
Example:
Keys, which in May SoftCam.Key the words:
In 0D01E4 06 C23FFA9219AB
In 0D01E8 06 C23FFA9219AB
In Crypto save file:
S: (0D 01 (E4 E8 00 00 (C2 3F FA 92 19 AB)))
Nagra (1800, 1801):
Boxkey:
As one of many security system will record a, the evaporation of the tuner card via
boxkey'a. In order to make the card run Nagra, unfortunately we have to try to pull some data
the tuner.
The letter is identified Boxkey B: and write it to a file recorded in the following form:
B (ir ir ir ir (bk bk bk bk bk bk bk bk))
Where:
ir - IRD card, it can be read from the card by inserting the card into the reader, having run
Gbox emulator of entry: AU: 0x IR IR IR IR
bk - boxkey
So for example:
Cam ident: AU: 0x3C529FAE
B: (3C 52 9F AE (82 F3 8C E4 AC BA C0 21))
More secure identification cards still require the RSA consists of 64
bytes that enter the brackets:
B (ir ir ir ir (bk bk bk bk bk bk bk bk)) RS RS RS RS .........
So for example:
B: (3C 52 9F AE (82 F3 8C E4 AC BA C0 21))
16B4AE7892FF3E2782947482927363838264AE7892FF3E2716 B4AE7892FF3E2716B4AE7
892FF3E2716B4AE7892FF3E2716B4AE7892FF3E2716B4AE789 2FF3E27
Nagra 1 (1800):
System keys are identified Nagra 1 The letter N: and are recorded in the following
Format:
N: ((XX YY ZZ ZZ ZZ ... ...))
Where:
XX - the provider
YY - key number
ZZ - the key consisting of 8 bytes
Example:
N: (48 01 00 (ca 26 3c c0 60 a4 50 d0)) - a key 00 for TV Cabo
N: (70 01 01 (4 de 2e 51 c1 f4 67 8b)) - a key 01 for Polsat Cyfrowy
Nagra 2 (1801):
The keys of Nagra 2 to version 2.1c The letter was identified in 2: and were saved in
the following format:
# 2: ((YY XX YY ... ... ... (ZZ ZZ ZZ ... ...)))
Where:
XX - the provider
YY - ideakey consisting of 16 bytes
ZZ - rsakey consisting of 64 bytes
Example:
2: (41 01 (F5 36 55 68 F5 46 63 32 52 EE D5 00 88 1E 5A 37 (D9 1F B4 82 F5 4C 45 35
62 1D 84 5F 7E C4 AB 4D C9 30 9D ED 26 B5 40 30 84 8E B6 39 68 97 75 29 FE 8F F1 86
13 27 61 71 E5 7B DA 8A 47 AC 99 37 03 CC E2 A1 CB 07 19 98 EC CB 32 7E F6 3C CE
A7))) - the key for Digital +
From version 2.20 of Nagra 2 keys have the AU on this coding system, but had
change of notation keys, which are now being identified literkami:
I - IDEA ECM key
P: - ECM key
M: - EMM key
Key IDEA ECM key is saved in the following format:
And: ((XX YY ZZ ZZ ZZ ... ...))
Where:
XX - the provider
YY - key number
ZZ - IDEA ECM key consisting of 16 bytes
Example:
I: (71 01 00 (0C CF 87 9B FE 90 A4 FF C6 64 A7 EB 51 54 F5 D9)) - a key 00 for
Cyfrowy Polsat
Key ECM key is saved in the following format:
P: (XX (YY YY YY YY ... ...))
Where:
XX - the provider
YY - ECM RSA key consists of 64 bytes
Example:
R: (71 01 (AB C5 7C FA 14 C4 14 A8 4C 3E B1 96 9F 5F 99 93 62 19 B4 85 E9 B9 6A 20
C3 31 95 63 C8 0D 13 74 3C CD DE DF 67 1B BE DC 9C 5D 31 EB A5 BA E2 60 42 39 C6
E7 07 29 E9 99 91 71 BD 0F FE 37 5F BA)) - RSA ECM for Polsat Cyfrowy
These two keys are sufficient to receive the provider.
If your provider has to be decoded automatically record key is needed to EMM,
that looks like this:
M: ((XX YY YY YY ... ... (ZZ ZZ ZZ ZZ ... ...)))
Where:
XX - the provider
YY - EMM IDEA key consisting of 16 bytes
ZZ - RSA EMM consists of 96 bytes
Example:
M: (71 01 (57 68 58 58 ED 62 82 07 76 9D B8 18 82 AD 75 B1 (4F CE 0C 37 E3 F5 08 C4
78 2B 16 E9 57 E2 13 89 8F DA 71 74 DF 5A 73 8A 9A 25 AE 7F 0D 84 84 94 4B 96 13 CF
F2 F6 70 1A 76 5C 36 B2 04 1D D9 18 F3 D8 D5 DA 47 74 B5 46 39 A6 64 E7 2B 36 CC 53
F8 1E C0 2F E1 8A 00 98 AE 17 83 DC C1 32 A7 AC B9 81 38 6A AB C1 D3 4C EF AB 27
A3 A6 8F 53 AE))) - for key EMM Cyfrowy Polsat
Seca (0100):
Seca keys in the system are saved in the format:
S: ((XX YY ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ))
Where:
XX - the provider
YY - key number
ZZ - the key consisting of 8 bytes
Example:
S: (00 65 0C (5A BC 23 DE 34 9B CA 5F)) - 0C key for Cyfra +
The system seca key 0E is the key and the system is stable, is to switch
between key 0C and 0D.
Keys 0C and 0D are key operational and serve to decode the ECM-s. Are changed in
monthly cycle of changes.
Gbox to automatically retrieve the keys need for an active couple consisting of PPUA and
MK1 key (key MasterKey1), which is written in the format:
M: (XX XX YY YY YY YY KK (ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ))
Where:
XX - the provider
YY - PPUA
KK - MK1 key number for the Primary is a value of 01, for the Secondary has a value 11
ZZ - MasterKey1
Example:
M: (00 65 00 06 15 21 01 (F0 01 C3 28 4E CC 32 07)) Cyfra + primary MK1
Via (05XX)
Viaccess1 keys in the system are saved in the format:
V: (00 (XX YY ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ))
Where:
00 - ending a system of identifying viaccess1 500
XX - the provider
YY - key number
ZZ - the key consisting of 8 bytes
Example:
V: (00 94 00 08 (23 ED 5A BC 34 9B CA 5F)) - a key 08 for SRG Swiss
Gbox to automatically retrieve the keys need for an active couple consisting of PPUA and
MK key (key masterkey), which is written in the format:
M: (00 XX XX YY YY YY YY KK (ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ))
Where:
00 - ending a system of identifying viaccess1 500
XX - the provider
YY - PPUA
KK - MK key number, in this case it may be the key 00, 01 or 04 (dependent on
Operator)
ZZ - masterkey
Example:
M: (00 94 00 00 C2 8D F0 67 00 (8B 09 62 03 A1 67 49 AA)) - SRG SSR
M: (00 94 00 00 C2 8D F0 67 01 (EB 6C 07 44 4B 32 B4 FE)) - SRG SSR
M: (00 94 00 00 C2 8D F0 67 04 (57 4B 23 9F FA 14 FB E2)) - SRG SSR
Viaccess2 keys in the system are saved in the format:
In: (01 (XX YY ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ))
Where:
01 - ending a system of identifying viaccess2 501
XX - provider
YY - key number
ZZ - the key consisting of 16 bytes
Example:
In: (01 94 10 08 (BE E9 EE 68 7D 6C 03 97 87 49 A4 FE 32 B5 67 D2)) - the key to the NTV
TPScrypt keys in the system are saved in the format:
T: (00 (XX ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ ZZ))
Where:
00 - ending a system of identifying viaccess1 500
XX - provider
ZZ - AES key consists of 16 bytes
Example:
T: (00 7C 00 (39 DF BD 8C 95 E0 C9 E5 49 99 82 47 24 D8 12 33)) - the key for TPS
Отговори с цитат
Следните потребители (7) благодарят на ТИНТИН за този полезен пост
heracle (09-11-2009), rumen (09-11-2009), thunderstorm6 (09-11-2009), Джак (09-11-2009), Крал Артур (09-11-2009), Ники (09-11-2009), Чавдар (01-01-2010)