A classic card sharing setup consist of three parts: card reader, server and a client. In order to be connected to a similar system and to be able to exchange decryption keys a communication protocol is also required. CCcam is a tool that include all this components and therefore is a all in one tool for card sharing. CCcam uses custom communication protocol named CCcam protocol.
Configuration method 1
This is the configuration how CCcam was intended to be used. CCcam read the card, send the data to the server who shares the keys with the internal client or through the internet with the partner server. The partner server has similar configuration and is able to exchange keys (from his own reader) an also to reshare to different clients that understand CCcam protocol (MGcamd, Scam, FlyCCcam, etc).
Configuration method 2
If a card is not recognized by CCcam, then external reader can be used to access the card: NewCS, OScam, Sbox, etc.
Important: the communication between external reader and CCcam is done using NewCAMD protocol (N-lines). Only version 2.1.3 or lower show this kind of connection as Local card (hop0).
Abuse method 1
Since CCcam 2.13 or lower show a N-line as Local card, many people abuse this and are using remote N-lines to fake their local card. External readers (like NewCS, OScam, Sbox, etc) are creating unlimited number of N-lines from one original card so unlimited number of Fake Cards can be created.
Abuse method 2
Using OScam, the process of faking cards go one step further. OScam convert C-line to N-lines so situation described in Abuse method 1 section can occur. This method is also named card stealing.