Softcam configuration discussion for USA region

There are 18 replies in this Thread which was already clicked 6,559 times. The last Post () by EnoSat.

  • This is a carry over from Softcam.Key Enigma2 for American Satellites

    After getting into this hobby for several years. Many informative topics have been discussed.
    Some discussions are rather "programmer-ese" or taken for granted that a person is well versed in the various software and plugin in and outs.
    I am trying to understand the configuration parameters of all of the individual files for oscam-emu.
    Also trying to learn what schemes are "cardless" because none are used here.
    I am currently using an Edision Os Mio 4k receiver. Several years ago oscam-emu had just a few readers in the oscam.server file.

    Today. There are many. Covering the different cards used in the European and perhaps more region. Again. "Here". Those readers that use the card slot are not needed.
    I may be mistaken. Here is a list from the oscam I'm currently using from Live Log>Files>oscam.version.
    What is confusing is that PV, biss, TB (Director) is not listed.....but they work. What readers listed are actual cardless?


    Reader support: yes


    Nagra: yes

    Nagra Merlin: yes

    Irdeto: yes

    Conax: yes

    Cryptoworks: yes

    Seca: yes

    Viaccess: yes

    NDS Videoguard: yes

    DRE Crypt: yes

    TONGFANG: yes

    Bulcrypt: yes

    Griffin: yes

    DGCrypt: yes

    If I were able to learn building a configuration file set from the ground up. Starting out with the bare minimum for PV, biss. At the very minimum.
    And leaving out every single bit of information for systems that are not used. The reason for all of the confusing lines of entries in he config. file set.

    I know 0E00 is for pv. 2600 is for biss. After that? Who knows.


    Streamboard and git just gives sometimes vague explanations with no actual usable samples in "programmer-ese".
    I recently performed a fresh flash of OpenVix and followed it with an install of oscam-emu from Mohamed. Who by the way never has let me down.
    I kept the as-installed configurations. Placed my softcam.keys file in the config directory.
    And turned off every reader except emulator. Which he had linked to his own Internet keys file.
    Confusion? His Internet link was to handle AFN keys update. My emulator section handled my own softcam.keys file. His resided in the volatile /tmp/.oscam directory.

    Whatever the reason. PV clearing was terrible. I placed my backup config files in place of his. And still the same thing. Poor performance. Not saying anything negative about him.
    I eventually swapped just the binary of an older version of oscam. And everything worked as before. Curious, I put his configuration files back. Not a very happy camper after that.
    So. There you have it. IKS here is simply not a good idea. Offshore subscriptions will eventually get you a very nasty "knock on the door". You may ask my friend about that.

    There is oscam-emu, revcam, icam, ncam......A-Z cam for chrissakes. The colors, you choose. Folks have asked which is the best one to use. And replies of "This is what I use".

    But vague to no explanation to why. What makes one better than the other. For cardless systems.

    Could we start a discussion on this?

    A sample. Or guide for. "The very bare minimum skin-and-bones configuration for power vu that will absolutely work". And "If something is not working as expected. Here is what to look for and possible add to the configuraton lines".
    Then perhaps a section for biss. And on and on.


    Make sense? Hope so.

  • For BISS (CAID-2600) or CCW (CAID-XXXX) two protocols can be used:

    emu - https://github.com/oscam-emu/o…1-and-BISS2-mode-1-config

    constantcw - https://wiki.streamboard.tv/wi…onfig/oscam.server#device


    For PV (CAID-0E00) or Tandberg/Director (CAID-1010) only the emu protocol can be used.
    https://github.com/oscam-emu/o…d-old/wiki/PowerVU-config

    Director config
    Open Source Cam Emulator. Contribute to oscam-emu/oscam-patched-old development by creating an account on GitHub.
    github.com


    The list of supported readers is not essential, but it should contain:

    Emulator support: yes

    Built-in SoftCam.Key:

    Edited 4 times, last by EnoSat ().

  • So. If a person were to understand correctly. Reader refers to an actual card to be inserted in the CA slot.
    And emulator (the emu part of oscam-emu) are for cardless protocols.
    PV, biss, tandberg. What are the others? I see keys in the softcam.keys file that include other protocols.

    If a person were to "start from the beginning" to learn the mechanism of oscam and use only biss. Or use only pv. Or use both only.
    With a stripped to the bones configuration. How you they make sense of it?
    Let's take this. And it may not be pertinent to any of the above. Or might.
    [reader]

    label = emulator

    protocol = emu

    device = emulator

    services = powervu,tandberg,biss

    disablecrccws_only_for = 0E00:000000

    caid = 0500,0604,0D00,0E00,1010,1801,2600,2602,2610

    detect = cd

    ident = 0500:020A00,021110;0604:000000;0D00:0000C0;0E00:000000;1010:000000;1801:000000,001101,002111,007301;2600:000000;2602:000000;2610:000000

    group = 1

    emmcache = 2,1,2,1

    emu_auproviders = 0604:010200;0E00:000000;1010:000000;2610:000000


    caid, ident, emu_auproviders is not really covered in the guides. And if it is. There seems to be way more contained in lines that might be actually necessary.

    And that's just in oscam.server. In oscam.conf. The section disablecrccws_only_for.
    What is the bare minumum needed to make everybody play together?

    Remember. Because I used a new install of oscam-emu that wrote the /etc/tuxbox/config directory. And the only thing changed at the moment was to add my softcam.keys file. Some pv channels cleared. Some said no reader available. And for some strange reason there were different caid listed in live log.

    Once my backup configs were replaced. Things went back to normal.

    Leaves a person asking. What gives?

  • All systems could work without cards if Algo was implemented.
    Only old versions of systems are currently working in Emu.
    CRC checks that you can eliminate in Oscam as a protection against unauthorized income.
    The fact that in the LiveLog they appear fake Caid cause files with keys (or set in oscam.dvbapi).

    [reader]

    label = emulator

    protocol = emu

    device = emulator

    services = powervu,tandberg,biss

    disablecrccws_only_for = 0E00:000000

    caid = 0500,0604,0D00,0E00,1010,1801,2600,2602,2610

    detect = cd

    ident = 0500:020A00,021110;0604:000000;0D00:0000C0;0E00:000000;1010:000000;1801:000000,001101,002111,007301;2600:000000;2602:000000;2610:000000

    group = 1

    emmcache = 2,1,2,1

    emu_auproviders = 0604:010200;0E00:000000;1010:000000;2610:000000

    0604 in Europe is already using higher protection
    0D00 in Europe no longer broadcast
    1801 in Europe via satellite no longer broadcast
    2602 and 2610 there are no tools to get keys
    020a00 is not Public in Europe
    The situation on the American continent is relatively unknown to us.

    [reader]

    label = EMU US

    protocol = emu

    device = emulator

    disablecrccws_only_for = 0E00:000000

    caid = 0E00,1010,2600

    detect = cd

    ident = 0E00:000000;1010:000000;2600:000000

    group = 1

    emmcache = 2,1,2,1

    emu_auproviders = 0E00:000000;1010:000000

    Edited 5 times, last by EnoSat ().

  • This is what I have here in NA, and is working for PV, Tandberg/director (1010) & biss (2600, 2610).

    My guess is that some of other key types (Irdeto, nagra2, via...) posted in softcam.key, are used in card shearing via cccam, witch (I guess again!), is legal in EU, but not here. I may be wrong, but we (in NA) have to ignore them, & look for PV, Tandberg/director & some biss keys only.

    NIHIL SINE DEO !

    Edited once, last by lme ().

  • Here is one for you. A recent encryption change for a channel has me stumped.
    It was clearing with biss. Then recently changed to cryptoguardAB as shown using the last drakkar logger.
    There are hints in oscam live log of biss. But 4AEa is shown also.
    I'm taking it that cryptoguard is a card-only system. Correct? Is there any reason that I am seeing 2600 in live log?
    P: 2600:000000:0002:1FFF:0000
    Included below is the text from live log as well as 30k of logged ECM's from drakkar with CryptoGuard as the system selection.
    Mind you. I'm not that versed in using the program. Except for logging for pv to use with pvhe.


    2025/02/25 16:47:58 7EC7595B c (dvbapi) PMT mode 6: Connecting to enigma CA PMT listen socket...

    2025/02/25 16:47:58 7EC7595B c (dvbapi) PMT mode 6: Successfully connected to CA PMT server (fd 9)

    2025/02/25 16:48:19 7EC7595B c (dvbapi) Demuxer 0 ecmpid 0 CAID: 4AEA ECM_PID: 0D22 PROVID: 000000

    2025/02/25 16:48:19 7EC7595B c (dvbapi) Demuxer 0 found 1 ECM pids and 3 STREAM pids in CA PMT

    2025/02/25 16:48:19 7EC7595B c (dvbapi) Demuxer 0 ecmpid 1 CAID: 2600 ECM_PID: 1FFF PROVID: 000000 (fake ecm pid)

    2025/02/25 16:48:19 7EC7595B c (dvbapi) Demuxer 0 trying to descramble PID 1 CAID 2600 PROVID 000000 ECMPID 1FFF ANY CHID PMTPID 0028 VPID 0000

    2025/02/25 16:48:19 7EC7595B c (ecm) get cw for ecm:

    2025/02/25 16:48:19 7EC7595B c (ecm) 80 00 12 00 02 00 28 00 26 00 27 00 3E 00 01 00

    2025/02/25 16:48:19 7EC7595B c (ecm) 01 A9 7D 0F B1

    2025/02/25 16:48:19 7EC7595B c (ecm) Client dvbapiau ECM dump P: 2600:000000:0002:1FFF:0000: #ECM_L:15 #CW=00000000000000000000000000000000 HOP:00

    2025/02/25 16:48:19 7EC7595B c (ecm) 80 00 12 00 02 00 28 00 26 00 27 00 3E 00 01 00

    2025/02/25 16:48:19 7EC7595B c (ecm) 01 A9 7D 0F B1

    2025/02/25 16:48:19 58554269 r (emu) Key found: F D2371A3E 00000000

    2025/02/25 16:48:19 7EC7595B c (ecm) Client dvbapiau cw 04EF01F474EA026004EF01F474EA0260 rc 0 P: 2600:000000:0002:1FFF:0000: #ECM_L:15 #CW=04EF01F474EA026004EF01F474EA0260 HOP:00

    2025/02/25 16:48:19 7EC7595B c (ecm) dvbapiau (P: 2600:000000:0002:1FFF:0000: #ECM_L:15 #CW=04EF01F474EA026004EF01F474EA0260 HOP:00): found (1 ms) by emulator - CONCERT CHANNEL

    2025/02/25 16:48:19 7EC7595B c (ecm) cw:

    2025/02/25 16:48:19 7EC7595B c (ecm) 04 EF 01 F4 74 EA 02 60 04 EF 01 F4 74 EA 02 60

    2025/02/25 16:49:09 7EC7595B c (reader) emulator [emu] EMM: reader_caid 0000 != emmpid caid 4AEA -> SKIP!

    2025/02/25 16:51:09 7EC7595B c (-) -- Skipped 3 duplicated log lines --


    Concert117.txt

  • In your oscam settings, you have defined that a fake (virtual) CAID 2600 is created. - (fake ecm pid)
    You can verify the actual CAID from PMT using dvbsnoop

    e.g. channel with BISS

    e.g. channel without BISS

    Edited once, last by EnoSat ().

  • In your oscam settings, you have defined that a fake (virtual) CAID 2600 is created. - (fake ecm pid)
    You can verify the actual CAID from PMT using dvbsnoop

    e.g. channel with BISS

    e.g. channel without BISS

    Oh. Eno. Believe me. I did not create a fake anything. It's how the file comes when oscam is installed or my old backups are moved to the config directory.

    There are situations where I can correct a channel name in srvid2. My skills are limited and to be honest. There are just too many strings of characters in the different files to figure out the purpose and function of. Which goes back to the bare minimum to use oscam-emu with cardless systems. And exactly which ones use no cards.

  • 2025/02/25 16:48:19 7EC7595B c (dvbapi) Demuxer 0 found 1 ECM pids and 3 STREAM pids in CA PMT

    2025/02/25 16:48:19 7EC7595B c (dvbapi) Demuxer 0 ecmpid 1 CAID: 2600 ECM_PID: 1FFF PROVID: 000000 (fake ecm pid)

    2025/02/25 16:48:19 7EC7595B c (dvbapi) Demuxer 0 trying to descramble PID 1 CAID 2600 PROVID 000000 ECMPID 1FFF ANY CHID PMTPID 0028 VPID 0000

    This line in oscam.dvbapi creates a fake 2600 for PMT 0x0028

    Code
    A: ::0028 2600:000000:1FFF ;ERT 1 HD

    Do not use oscam.dvbapi designed for European satellites in your region !!!

  • 2025/02/25 16:48:19 7EC7595B c (dvbapi) Demuxer 0 found 1 ECM pids and 3 STREAM pids in CA PMT

    2025/02/25 16:48:19 7EC7595B c (dvbapi) Demuxer 0 ecmpid 1 CAID: 2600 ECM_PID: 1FFF PROVID: 000000 (fake ecm pid)

    2025/02/25 16:48:19 7EC7595B c (dvbapi) Demuxer 0 trying to descramble PID 1 CAID 2600 PROVID 000000 ECMPID 1FFF ANY CHID PMTPID 0028 VPID 0000

    This line in oscam.dvbapi creates a fake 2600 for PMT 0x0028

    Code
    A: ::0028 2600:000000:1FFF ;ERT 1 HD

    Do not use oscam.dvbapi designed for European satellites in your region !!!

    I'm afraid that I do not understand "fake" or why I would want it, or not.
    All configurations are for European satellites. That is what I have been trying to stress.

    So adding or deleting anything in the extensive lines of text in the various files in the config directory are very, very confusing.

    Of course a backup of several of the different config directories are kept for the different oscam versions I've used over the years.

    And the full image backups. When extracted. Provide last state file access.

  • Here's one. 131W 4100H
    Is it biss? Is it PV?
    It was PV. Now won't clear. Drakar says 0x0e00.
    And there goes that "fake" thing.


    (dvbapi) PMT mode 6: Connecting to enigma CA PMT listen socket...

    (dvbapi) PMT mode 6: Successfully connected to CA PMT server (fd 9)

    (dvbapi) Demuxer 0 ecmpid 0 CAID: 0E00 ECM_PID: 177E PROVID: 000000

    (dvbapi) Demuxer 0 found 1 ECM pids and 4 STREAM pids in CA PMT

    (dvbapi) Demuxer 0 ecmpid 1 CAID: 2600 ECM_PID: 1FFF PROVID: 000000 (fake ecm pid)

    (dvbapi) Demuxer 0 no suitable readers found that can be used for decoding!

    (dvbapi) Demuxer 0 ecmpid 0 CAID: 0E00 ECM_PID: 177E PROVID: 000000

    (dvbapi) Demuxer 0 found 1 ECM pids and 4 STREAM pids in PMT

    (dvbapi) Demuxer 0 ecmpid 1 CAID: 2600 ECM_PID: 1FFF PROVID: 000000 (fake ecm pid)

    (dvbapi) Demuxer 0 impossible to descramble PID 0 CAID 0E00 PROVID 000000 ECMPID 177E PMTPID 138A (NO MATCHING READER)

    (dvbapi) Demuxer 0 trying to descramble PID 1 CAID 2600 PROVID 000000 ECMPID 1FFF ANY CHID PMTPID 138A VPID 0000(ecm) get cw for ecm:

    (ecm) 80 00 14 00 02 13 8A 00 C8 00 D2 00 D3 00 FA 00

    (ecm) 65 0A BC A8 F1 00 00

    (ecm) Client dvbapiau cw 00000000000000000000000000000000 rc 4 P: 2600:000000:0002:1FFF:0000: #ECM_L:17 #CW=00000000000000000000000000000000 HOP:00

    (ecm) dvbapiau (P: 2600:000000:0002:1FFF:0000: #ECM_L:17 #CW=00000000000000000000000000000000 HOP:00): rejected group (1 ms) - MHC SD (no matching reader)

    (ecm) cw:

    (ecm) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

  • (dvbapi) Demuxer 0 ecmpid 1 CAID: 2600 ECM_PID: 1FFF PROVID: 000000 (fake ecm pid)

    remove European data (satellites) from oscam.dvbapi !!!

    Basically, you don't even need an oscam.dvbapi file

  • Very cool. Kind of. I edited the oscam.dvbapi file from your suggestion in #14 without looking at the previous one you illustrated in #12.

    What I ended up is in oscam.dvbapi1. The unedited file is named as it is. Of course for explanation the edited version here is appended with 1

    And the channel cleared.


    oscam.dvbapi.txt


    oscam.dvbapi1.txt


    Then. I found another version in a different config directory from a backup.


    oscam.dvbapi2.txt

    It is difficult to grasp. You mention the file is not even needed for the US. Trying to learn which cardless systems can be used. We have 2602. I thought although cardless, it has not been solved. And 0101. I do get a few cleared channels with that.

    There is also na**a listed in the keys files. I do 'have a friend' who delved into i*s for pay satellites. Never a good idea. Spies, lets say. Satscams website. Look.


    And I see different cards on eBay. Nothing I'm really interested in. I thought that was what the emulator in oscam-emu does. Yes/No?

    Lyngsat, Tvrosat.com (the site I check for updated tp changes). Lists the different schemes.
    It seems like the config. files are known by a tight knit group. "Secret Handshake" folks like the Masons. You know. I hope.

    X-Crypt, Irdeto, etc. And different configuration file edits to enable. Like for pv & biss. Probably more.

    PV can update keys automatically. How about biss? Sometimes? Never, ever?


    And then I found this. If I look at, read, digest, and try to learn. What in the oscam.dvbapi file I was using "killed" the channel. And better yet, how?

    Good questions and stuff?


    NAME

    oscam.dvbapi - DVB API configuration file for OSCam


    SYNOPSIS

    DVBAPI settings, first match - first used


    DESCRIPTIONS

    P: [CAID]:[provider ID]:[service ID]:[ECM PID]:[CHID] [force]:[PIDx] priority

    set priority, continue = 1: proceed with priority, recommended for

    pay-per-view services / EMMs (use carefully), although local SCs

    will be prioritised higher, default:none


    I: [CAID]:[provider ID]:[service ID]:[ECM PID]:[CHID] [PIDx] ignore

    set ignore


    J: [CAID]:[provider ID]:[service ID]:[ECM PID] joined CAID:joined provider ID:joined ECM PID

    join to another ECM PID


    A: ::service ID:[PMT PID] :[provider ID][:][ECM PID]

    set a dummy ECM request with CAID FFFF for services with a constant CW shown as unencrypted service (for STBs with PMT

    PID support only)


    A: ::service ID:[video PID] :[provider ID][:][ECM PID]

    set a dummy ECM request with CAID FFFF for services with a constant CW shown as unencrypted service (for STBs without

    PMT PID support only)


    X: [CAID]:[provider ID]:[service ID]:[ECM PID]

    add decoding on an extra demux index on the same CA device (Multi ECM) (not support on all STBs)


    D: [CAID]:[provider ID]:[service ID]:[ECM PID] delay

    set delay in milli-seconds writing CWs


    M: [CAID]:[provider ID]:[service ID]:[ECM PID] target CAID[:][target provider ID]

    mapping


    S: [device] [PMT file name]

    set DVB API device name and PMT file name (valid for STAPI only)


    L: [CAID]:[provider ID]:[service ID]:[ECM PID] length

    set ECM length in hexadecimal


    ANNONTATIONS

    Please use Unix text file format only.


    EXAMPLES

    P: 0100:123456 # prioritise CAID 0100 with provider 123456


    P: :1234 # prioritise ECM with provider ID 1234 on

    # on any CAID and service


    P: 0200 # prioritise CAID 0200


    P: 0300::9ABC # prioritise CAID 0300 on service 9ABC only


    P: 0400 1 # prioritise CAID 0400 for pay-per-view services


    P: : 1 # prioritise for EMMs


    M: 0500 0600:123456 # map CAID 0500 to provider ID 123456 with

    # CAID 0600


    D: 0700 200 # wait 200 ms before writing CW for CAID 0700


    I: :654321 # ignore provider ID 654321 for every CAID and

    # service


    I: 0 # ignore every CAID that was not handled before


    L: 0800 8e # ECM length for CAID 0800 to 8e (hexadecimal)


    SEE ALSO

    list_smargo(1), oscam(1), oscam.ac(5), oscam.cacheex(5), oscam.cert(5), oscam.conf(5), oscam.fakecws(5), oscam.guess(5),

    oscam.ird(5), oscam.provid(5), oscam.ratelimit(5), oscam.server(5), oscam.services(5), oscam.srvid(5), oscam.srvid2(5),

    oscam.user(5), oscam.whitelist(5)

  • It is difficult to grasp. You mention the file is not even needed for the US. Trying to learn which cardless systems can be used. We have 2602. I thought although cardless, it has not been solved. And 0101. I do get a few cleared channels with that.

    BISS 2602 - no tools or public keys = CAID unnecessary in oscam.dvbapi
    0101 - I have no idea what system it is, probably just a typo

Forum USA LinuxSat