Changeset 50 for trunk/README.txt


Ignore:
Timestamp:
10/26/10 14:25:07 (13 years ago)
Author:
bowman
Message:

Preparations for 0.9.1 RC, misc fixes and cleanup.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/README.txt

    r46 r50  
    1 Cardservproxy 0.9.1
    2 -------------------
     1Cardservproxy 0.9.1 (See README.0.9.0.txt for features/changes specific to 0.9.x versions)
     2------------------------------------------------------------------------------------------
    33
    44First, in order to avoid the usual confusion about the proxy:
     
    9393
    9494- Define ca-profiles, one for each provider/vendor/card-type (yes if two providers happen to use the same ca-system, two
    95   separate profiles are still required). Ca-profiles can be thought of as virtual cardservers, and will seem to the
     95  separate profiles may still be required). Ca-profiles can be thought of as virtual cardservers, and will seem to the
    9696  clients like single cards (with a potentially infinite capacity). If you have an enigma1 services file (dreambox)
    9797  you can fetch that and place it where the proxy can read it and point it out in the profile definition. This will
     
    102102  only one port is required per profile (or two if you need both newcamd and radegast listeners), but it is now
    103103  possible to have an arbitrary number of listen ports for the same profile, complete with their own accept/deny lists
    104   and other protocol-specific settings.
     104  and other protocol-specific settings. If it is a satellite setup for mgcamd clients alone, you can create profiles
     105  without ports and use the combined extended-newcamd listen port (top of the generated config) to access all profiles.
    105106
    106107- Define cws-connectors for each cardserver that the proxy should connect to. Use one newcamd-connector or
Note: See TracChangeset for help on using the changeset viewer.