View Full Version : Where to get keys?
oregon
29-05-2009, 09:16 AM
Can someone please let me know where I can find keys for the azbox? Are all key.bin files the same? Or do I need a file specifically for the azbox?
Thanks for your help.
radioboy
29-05-2009, 10:56 AM
Hi,
The keys are in the keys section on this site...
hxxp://www.satpimps.co.uk/forumdisplay.php?f=378
But
hxxp://www.satpimps.co.uk/showthread.php?p=624895#post62489 5
Might be of interest for you.
Then to edit go into plugins
opencas
Camd Setup
MultiCAS
Edit and Covert keys
down to Nagra
and then edit the one you want to change...
Radioboy
oregon
29-05-2009, 11:03 AM
Thanks Radioboy
If I want to FTP keys to the box, which files do I need to transfer?
FME_fta
29-05-2009, 12:08 PM
MGcamd works with the file SoftCam.Key, so this is the file you need to update/edit.
(it also uses AutoRoll.Key)
I don't know about others EMU, but you can always try to open the files from that EMU with the notepad or wordpad and see which one have k€ys.
Regards.
oregon
29-05-2009, 12:47 PM
Thanks for the info FME.
Which providers does MGCamd open? Is it only digitv??
FME_fta
29-05-2009, 12:57 PM
AFAIK it open all the providers as long as the k€ys are known and public.
(this is using k€ys)
EDIT: If Mgcamd is using the CS network of g80x or other server (newcamd, radegast) it can open much more things.
oregon
29-05-2009, 01:37 PM
AFAIK it open all the providers as long as the k€ys are known and public.
(this is using k€ys)
EDIT: If Mgcamd is using the CS network of g80x or other server (newcamd, radegast) it can open much more things.
Is Mgcamd already setup to use CS? Or do we have to make some sort of change ourselves?
Thanks.
FME_fta
29-05-2009, 01:57 PM
MGcamd at least in the dreambox it uses the file mg_cfg for configuration.
It uses the file peer.cfg which is a copy of the file cwshare.cfg used with the real g80x.
(MGcamd can only be client of g80x)
It uses the file newcamd.list to connect to newcamd servers.
MGcamd is a great updater for cards in newcamd servers.
All this files can be edited with notepad, wordpad or other.
You need to edit mg_cfg to see its configuration, it might be or not configured to use newcamd servers or g80x.
EDIT:
this is the main thing to edit for CS in mg_cfg:
# network mode, use summ for several clients
# 00 no network (default)
# 01 newcamd netclient
# 02 radegast netclient
# 04 camd3 netclient
# 08 g80x netclient
G: { 09 }
And AFAIK its all.
oregon
29-05-2009, 04:38 PM
MGcamd at least in the dreambox it uses the file mg_cfg for configuration.
It uses the file peer.cfg which is a copy of the file cwshare.cfg used with the real g80x.
(MGcamd can only be client of g80x)
It uses the file newcamd.list to connect to newcamd servers.
MGcamd is a great updater for cards in newcamd servers.
All this files can be edited with notepad, wordpad or other.
You need to edit mg_cfg to see its configuration, it might be or not configured to use newcamd servers or g80x.
EDIT:
this is the main thing to edit for CS in mg_cfg:
# network mode, use summ for several clients
# 00 no network (default)
# 01 newcamd netclient
# 02 radegast netclient
# 04 camd3 netclient
# 08 g80x netclient
G: { 09 }
And AFAIK its all.
FME - This is what my mg_cfg file has in it:
# network mode, use summ for several clients
# 00 no network (default)
# 01 newcamd netclient
# 02 radegast netclient
# 04 camd3 netclient
# 08 gbox netclient
#G: { 00 }
G: { 01 }
And this is the newcamd.list:
################################# ################################# ##############
#------------------------------------------------------------------------------#
# priority.list * _www.satandream.com/wbb3/index.php?page=Board&boardID=652 #
#------------------------------------------------------------------------------#
################################# ################################# ##############
#------------------------------------------------------------------------------#
#------------------------------- provider:-------------------------------------#
#------------------------------------------------------------------------------#
# *** SKY Italia (13.0E) ***
#
X: { 09 19 }
#------------------------------------------------------------------------------#
# *** Viasat Baltic/Nordic (4.8E) ***
#
X: { 09 0F }
#------------------------------------------------------------------------------#
# *** *** VIEW/XXX (13.0E) ***
#
V: { 03 20 00 }
V: { 02 44 00 }
#------------------------------------------------------------------------------#
# *** NTV+ (36.0E) ***
#
V: { 02 37 00 }
#------------------------------------------------------------------------------#
#-------------------------- use this CaID first: ------------------------------#
#------------------------------------------------------------------------------#
# *** Nagravision-2 "KD Home", "DigiTV" (23.5E) (1.0W)
#
X: { 18 01 }
#------------------------------------------------------------------------------#
################################# ################################# ##############
Can you see if anything is wrong in any of that? Sorry for all these questions, I have never done any of this before..
Many thanks
FME_fta
29-05-2009, 06:10 PM
(...) Sorry for all these questions (...)
No problem.
But newcamd.list is not the priority.list
What you quote is the priority.list
newcamd.list is only for newcamd connections and its configuration.
Your mg_cfg is configured to be client of newcamd servers only, if you want to be also client of g80x you have to use:
G: { 09 }
which is option 01 + 08
If you want to connect to a newcamd server, you need to "find" a newcamd server and put its configuration in newcamd.list.
If you want to be a client of g80x, you have to configure peer.cfg and "find" g80x peers.
The how to configure peer.cfg is the same way as cwshare.cfg from g80x, you can find better explanation in g80x manuals.
Regards.
oregon
29-05-2009, 06:25 PM
No problem.
But newcamd.list is not the priority.list
What you quote is the priority.list
newcamd.list is only for newcamd connections and its configuration.
Your mg_cfg is configured to be client of newcamd servers only, if you want to be also client of g80x you have to use:
G: { 09 }
which is option 01 + 08
If you want to connect to a newcamd server, you need to "find" a newcamd server and put its configuration in newcamd.list.
If you want to be a client of g80x, you have to configure peer.cfg and "find" g80x peers.
The how to configure peer.cfg is the same way as cwshare.cfg from g80x, you can find better explanation in g80x manuals.
Regards.
OK, thanks I pasted from the wrong file. This is the newcamd.list:
################################# ################################# ##############
#------------------------------------------------------------------------------#
# newcamd.list *_www.satandream.com/wbb3/index.php?page=Board&boardID=652 #
#------------------------------------------------------------------------------#
################################# ################################# ##############
#------------------------------------------------------------------------------#
CWS_KEEPALIVE = 600
CWS_INCOMING_PORT = 21000
#------------------------------------------------------------------------------#
# *** Lower Cardslot (enabled, port 34000 = port 34000 in newcs.xml file):
#
CWS = 127.0.0.1 34000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 lan newcs
#------------------------------------------------------------------------------#
# *** Upper Cardslot (enabled, port 34001 = port 34001 in newcs.xml file):
#
CWS = 127.0.0.1 34001 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 lan newcs
#------------------------------------------------------------------------------#
Is that okay? This is the the rest of the mg_cfg file:
################################# ################################# ##############
#------------------------------------------------------------------------------#
# mg_cfg * _www.satandream.com/wbb3/index.php?page=Board&boardID=652 #
#------------------------------------------------------------------------------#
################################# ################################# ##############
#------------------------------------------------------------------------------#
# EMM messages
# 00 don't show any EMMs (default)
# 01 show only valid EMMs
# 02 show valid and bad EMMs with complete data display
#M: { 01 }
M: { 00 }
#------------------------------------------------------------------------------#
# ECM messages
# 00 don't show anything about ecm
# 01 normal mode, show pids processed, decoded ecm and cw
# 02 verbose mode, show valid and bad ECMs with data
C: { 01 }
#------------------------------------------------------------------------------#
# AU
# 00 disable, no emm pids processed
# 01 enable, emm pids always processed for soft-au and shared cards
# 02 auto, emm started only if channel cant be decoded
# 03 process emm pids for network cards update only
#A: { 01 }
A: { 00 }
#------------------------------------------------------------------------------#
# key update (sum 01 or 02 with 04)
# 01 update only new keys, default setting
# 02 update all keys (used for valid PMK checking)
# 04 enable TPS au
U: { 01 }
#------------------------------------------------------------------------------#
# config files folder (softcam, autoroll, ignore/priority)
# 00 files in /var/keys
# 01 files in /tmp
T: { 00 }
#------------------------------------------------------------------------------#
# network mode, use summ for several clients
# 00 no network (default)
# 01 newcamd netclient
# 02 radegast netclient
# 04 camd3 netclient
# 08 gbox netclient
#G: { 00 }
G: { 01 }
#------------------------------------------------------------------------------#
# network retry, use summ for several options
# 00 disable
# 01 retry every new ecm
# 02 try to connect to offline shares every Q: seconds
# 04 try to detect and fast reconnect to lost (and not used atm) server
# + XX messages number and YY seconds to reconnect
# mg will reconnect to server, if no answer to last XX ecm/keepalive or
# if no answer for last ecm or keepalive sent for YY seconds
# set to 0 to disable
#N: { 07 } 5 30
N: { 03 }
#------------------------------------------------------------------------------#
# network ecm timeout in seconds
K: { 05 }
#------------------------------------------------------------------------------#
# newcamd dead routes connect retry, sec
Q: { 600 }
#------------------------------------------------------------------------------#
# network shares priority
# 00 gbox, newcamd, radegast, camd3 (default)
# 01 camd3, radegast, newcamd, gbox
# 02 newcamd, camd3, gbox, radegast
#P: { 00 }
P: { 02 }
#------------------------------------------------------------------------------#
# on screen display type
# 00 No OSD (default)
# 01 neutrino
# 02 enigma
# 03 relook
# + user password for http auth
O: { 00 }
#------------------------------------------------------------------------------#
# on screen display Options, summ of:
# 01 show emu ecm
# 02 show network shares messages
# 04 show decoding failed / fta
# 08 show emm keys update
# + web port to use for osd
S: { 03 }
#------------------------------------------------------------------------------#
# Log option, summ of:
# 00 off
# 01 network udp log
# 02 log to console
# 04 file, appended ! delete it by yourself, before it eat all your hdd
# + IP udp-port log-file-name
#L: { 00 } 192.168.2.105 514 /tmp/mgcamd.log
L: { 01 } 192.168.2.105 514
#------------------------------------------------------------------------------#
# keep ecm cache, seconds
# every cache entry takes 28 bytes, so 24h cache will take *only* 240-400kb of memory,
# for openbox/elanvision users with remote shares make sense to set it higher than default value,
# to not hammer cards while timeshifting or playing crypted recordings.
E: { 15 }
#------------------------------------------------------------------------------#
# cache option, summ of:
# 00 Off (default)
# 01 Ecm pids cache, store pids used to decode in /tmp/ca_cache.list at exit, load at startup, same syntax as restore.list
# 02 Ecm data cache, remember CW for (E:) time
# 04 Emm cache for network cards, do not resend the same emm twice, cache not cleared until restart
#H: { 07 }
H: { 00 }
#------------------------------------------------------------------------------#
# reread files, summ of:
# 00 No (default)
# 01 reread config file on channel change (including priority and ignore, but not replace/cache)
# 02 reread SoftCam.Key on channel change
# 04 reread SoftCam.Key if file changed
#R: { 00 }
R: { 04 }
#------------------------------------------------------------------------------#
# debug, summ of
# 00 off (default)
# 01 debug ecm
# 02 debug emm
# 04 debug network ecm
# 08 debug network emm
# 16 debug network login
# 32 show mem/cpu stats every 1 min
# 64 add timestamp to log messages
D: { 01 }
#------------------------------------------------------------------------------#
# box type
# 00 autodetect, change only if you think wrong type detected.
# 01 dbox2
# 02 dreambox
# 03 triple-dragon
# 04 relook
# 05 openbox
# 06 DM-7025, DM-800
B: { 00 }
#
# ! for DM-800S with older MGcamd-1.28 you need to set:
#B: { 06 }
#------------------------------------------------------------------------------#
################################# ################################# ##############
many many thanks
FME_fta
29-05-2009, 06:41 PM
I think everything is fine.
In newcamd.list, the lines:
CWS = 127.0.0.1 34000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 lan newcs
CWS = 127.0.0.1 34001 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 lan newcs
are 2 examples of a newcamd connection, in this case is 2 connections to newCS (which creates the newcamd server) and is running in the same STB linux and reading your cards.
Your lines to connect to any newcamd server will be simmilar.
If you have problems connecting to newcamd servers, you can try to change mg_cfg the option "N: { 03 }" to "N: { 07 } 5 30".
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.