Oscam is an Open Source Conditional Access Module software used for descrambling DVB transmissions using smart cards. It's both a server and a client.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

39 lines
2.2 KiB

  1. <!--- Provide a general summary of your changes in the Title above -->
  2. [linuxserverurl]: https://linuxserver.io
  3. [![linuxserver.io](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver_medium.png)][linuxserverurl]
  4. <!--- Before submitting a pull request please check the following -->
  5. <!--- If this is a fix for a typo in code or documentation in the README please file an issue and let us sort it out we do not need a PR -->
  6. <!--- Ask yourself if this modification is something the whole userbase will benefit from, if this is a specific change for corner case functionality or plugins please look at making a Docker Mod or local script https://blog.linuxserver.io/2019/09/14/customizing-our-containers/ -->
  7. <!--- That if the PR is addressing an existing issue include, closes #<issue number> , in the body of the PR commit message -->
  8. <!--- You have included links to any files / patches etc your PR may be using in the body of the PR commit message -->
  9. <!--- We maintain a changelog of major revisions to the container at the end of readme-vars.yml in the root of this repository, please add your changes there if appropriate -->
  10. <!--- Coding guidelines: -->
  11. <!--- 1. Installed packages in the Dockerfiles should be in alphabetical order -->
  12. <!--- 2. Changes to Dockerfile should be replicated in Dockerfile.armhf and Dockerfile.aarch64 if applicable -->
  13. <!--- 3. Indentation style (tabs vs 4 spaces vs 1 space) should match the rest of the document -->
  14. <!--- 4. Readme is auto generated from readme-vars.yml, make your changes there -->
  15. ------------------------------
  16. We welcome all PR’s though this doesn’t guarantee it will be accepted.
  17. ## Description:
  18. <!--- Describe your changes in detail -->
  19. ## Benefits of this PR and context:
  20. <!--- Please explain why we should accept this PR. If this fixes an outstanding bug, please reference the issue # -->
  21. ## How Has This Been Tested?
  22. <!--- Please describe in detail how you tested your changes. -->
  23. <!--- Include details of your testing environment, and the tests you ran to -->
  24. <!--- see how your change affects other areas of the code, etc. -->
  25. ## Source / References:
  26. <!--- Please include any forum posts/github links relevant to the PR -->