CCcam settings

[tlj999]

Hi all,

I have been setting up my CCcam server and wanted to check a couple of things.

Firstly,
am I right in assuming that if I'm sharing with someone and I look in CCcam info and the card says hop1, then that card would be a local in that persons machine.

Secondly,
if I write an F line with the ending 3 0 0 {0:0:2} then I would be allowing him to share my card with someone else at hop2.
And if it ends 3 0 0 {0:0:1} then he would only be able to use it himself.

Thanks in advance for all your help,
Tom.

 

[B16MCC]

Hi mate. ok Question 1, yes your correct.

Question 2.

3 0 0 means you are giving that user access to your local, your hop1's, hop2's and hop3's. Thats a little excesive.

If you made it 2 0 0 you would be giving access to your local and your hop1's and hop2's.

{0:0:2} means you are giving him 1 reshare so he could let someone else have it, and to them it would be hop2.

And yess {0:0:1} means you are letting just him use your card.

 

[Burnham Beech]

Saw this elsewhere, but be warned - this stuff is very complicated so it may be true or not -

"The space between the { and the 0 and the 2 and the } is required as is the use of yes or no after the password"

 

[sonic1]

Saw this elsewhere, but be warned - this stuff is very complicated so it may be true or not -

"The space between the { and the 0 and the 2 and the } is required as is the use of yes or no after the password"

Correct, get the spacing wrong and you end up resharing your card to the max.

Should be
F: username userpass 2 0 0 { 0:0:2 } { } { } userdns-addy.org

This example will make you share stable and only the person who you gave the C line to can connect.

 

[B16MCC]

Guys, lets be clear, the use of 'yes' or 'no' if specific to a C line. You don't use it in an F line.

 

[compufunk]

F: username userpass 2 0 0 { 0:0:2 } { } { } userdns-addy.org

This is helpful for blocking a person from giving anyone else access using the Cline you provided, but bear in mind that in some cases, the person you are sharing with could be connecting from a different location than where their server lives.

In this case, you would be blocking connections from wherever their dreabox is connecting from. I have one such "friend"

 

[B16MCC]

Hi again guys. When I looked over this thread again I was interested on the comment by Burnham Beech regarding the spaces in the {0:0:2}

I never use spaces in these brackets and my reshare setting seems to work just fine. Here's a screen shot from CCcam info on my DM7025. You can see the 2 local cards I have in my DM800. In the CCcam.cfg in my DM800 I set access for my DM7025 using {0:0:2}. Note no spaces. This allows 1 reshare. I've changed it to include spaces and back again, it seems to make no difference what so ever. This is using CCcam v2.1.0.

 

[tlj999]

What would it mean, if someone sent me a Cline and after the username password no it ended with { 0:0:2 }
I thought this ending was meant for Fline.

 

[B16MCC]

If the person gives you 5 0 0 on the Fline you can still choose to take only his local by putting {0:0:1} on the end of the Cline.

The host should not be giving you that info, its up to him to apply limits on your F line. It up to you if you want that after the 'No ' on the cline.

 

[tlj999]

Another quick question,

If I was to make my DM500 my server and share my card which is in it, but made my DM800 receive shares from other people, would that pose any problems ( apart from the fact that peers would only have access to my local ).

What is CAID and what is EMM?

Regards,
Tom.

 

[B16MCC]

Right, let me get this right, your are allowing people to share you card from your 500. But you are not connecting to their cards with the 500. Instead you are using the Clines they give you in your 800 instead. If I've got that right then yes thats fine.

Alternatively, if you negiotiate 1 reshare for all your shares, you could put F and Clines all in the 500, then just connect to the 500 from the 800. You'll have all your shares in 1 config and although the 800 will see them as hop2's , the performace will not suffer as the connection is simply across your lan. This way you will only have to look after 1 config in the 500, the 800 config will never change.

EMM - Entitlement Management Message

Meaning of EMM – “Entitlement Management Message”, is an encrypted message that contains private conditional access information about the authority a viewer has to aquire reception for such services as cable or satellite television.
Scrambling and encryption are used in a Conditional Access System to prevent users from acquiring an unauthorized reception on their Satellite or Cable TV system.
An Entitlement Control Message (ECM) contains access criteria and a scrambled key called a control word.
The ECM is sent encrypted to the receiver, or Set Top Box (ST, in a customer's home. If the customer is authorized to acquire the reception, a subsystem in the receiver will decrypt the message.
An EMM generator, a component in a conditional access system, is used to is send EMMs to the receiver. The generator receives commands from a subscriber management system and creates EMMs that get sent to the viewing card or to relay messages to the cable operators. The receiver knows whether or not the customer is authorized because of the authority is contained in an EMM.


CAID = Conditional Access Identification. Its the ID of each provider around the world.
_http://en.wikipedia.org/wiki/Conditional_Access_Identification#Digital_Systems

 

[tlj999]

Hi B16MCC,

Thanks for that info.
I hadn't thought of connecting my boxes that way and I must admit organising 2 configs is becoming a pain.
Is there a list of CAID's somewhere which shows which provider is for which card ( other than which encryption is used ).

Regards,
Tom.

 

[B16MCC]

Yes there is. The easiest way to do it , is to setup Cccamphpinfo on a wamp server.

There's a provider file you can add to show you the names instead of the CAID's.

 

[tomthebomb1968]

Heres a liitle program to automate making c and f lines

Admin - Attachment removed as it seems to be carrying a viral payload.

 

[Garry Breezer]

tomthebomb1968 should be banned for posting a virus!

 

[Analoguesat]

The post with the file was from 2009 and no-one has ever reported a problem with it before despite there having been 136 views of it.

HOWEVER my anti virus software did flag up a security issue so Ive removed it.

tomthebomb1968 is a respected member of the forum so I expect it was just one of those things - hes posted a file he found to help folk.

Thread closed.