Good evening, we continue to collect data and investigate. We have discovered that the server with card 1810 running on Mbox does not give a black screen. While a server with a chart in OSCam gives a black screen, the same chart mounted in MBox does not emit a black screen. I repeat, the MBox emulator (so far) seems to be working fine.
Posts by Quaterback
-
-
Good, another day where the iks receivers endure without problems. Enigma2 receivers equipped with OSCam, NCam, CCcam... go black.
-
ipk files? please?
-
Display MoreDisplay More
codificado en el firmware de los receptores. Abrir un emulador como OSCam y extraer datos es muy sencillo, ya que es un sistema gratuito de "código abierto". Para abrir un firmware de un sistema IKS es necesario obtener las claves de protección del archivo, y eso es muy, muy difícil que suceda. El seguimiento de una tarjeta en un sistema de viviendas compartidas es un juego de niños para cualquier profesional. Además, los sistemas iks utilizan sus propios emuladores, desconocidos hasta ahora. Es cierto que un sistema iks puede ser inestable en determinados momentos, por la cantidad de receptores que debe alimentar y sobre todo por la ubicación del servidor y bajo qué soporte trabaja,
No dudo que es muy dificil 'atacar' a iks.... pero esta pasando: iks pt esta afectado fallas... segun la mayoria de los foros de iks
¡Salud!
PT quiebra por ruptura de Movistar en líneas de Negocio. El Sistema de Fibra Óptica y la línea telefónica de la caída roja de la empresa hoy ha estado.
Un fallo generalizado en la red de Movistar, ya solucionado, impidió a los clientes corporativos realizar o recibir llamadas desde las 11.00 a las 13.30 horas
Yo lo tengo claro... clientes corporativos (clientes empresas, grandes... no minoristas) y fue por la mañana... por la tarde iks sigue fallando ;-)
And what kind of network does an IKs system use? Friend, forget the homemade concept we have of sharing. IKS systems go big.
-
cifrado en el firmware de los receptores. Abrir un emulador como OSCam y extraer datos es muy sencillo, ya que es un sistema gratuito de "código abierto". Para abrir un firmware de un sistema IKS es necesario obtener las claves de protección del archivo, y eso es muy, muy difícil que suceda. El seguimiento de una tarjeta en un sistema de viviendas compartidas es un juego de niños para cualquier profesional. Además, los sistemas iks utilizan sus propios emuladores, desconocidos hasta ahora. Es cierto que un sistema iks puede ser inestable en determinados momentos, por la cantidad de receptores que debe alimentar y sobre todo por la ubicación del servidor y bajo qué soporte trabaja, dependiendo del país de ubicación Un servidor alojado en España que mantiene una red de fibra muy segura y estable no es lo mismo que un país de Latam cuya calidad de conexión se vuelve más inestable.
No dudo que es muy dificil 'atacar' a iks.... pero esta pasando: iks pt esta sufriendo fallas... segun la mayoria de los foros de iks
¡Salud!
PT quiebra por ruptura de Movistar en líneas de Negocio. El Sistema de Fibra Óptica y la línea telefónica de la red de la empresa hoy ha estado caída.
Un fallo generalizado en la red de Movistar, ya solucionado, impidió a los clientes corporativos realizar o recibir llamadas desde las 11.00 a las 13.30 horas
-
si mediante la inyección de paquetes de QoS intentaran retrasar el envío del ECM, el emulador marcaría un "timeout" ya que venció el tiempo y no encontró la respuesta a tiempo. Por lo que hemos estudiado, el problema viene por 2 frentes. 1- Versiones R100 que distribuyen falsificaciones a través de su caché. (Ataque interesado por los creadores de multiCS R100 para vender su versión de pago) 2- Tarjetas en modo penalización. (Ataque de Movistar para penalizar el compartir) L
Mi apuesta es que Movistar está poniendo las tarjetas en una especie de 'modo de penalización'... tienen que saber cuántas 'solicitudes' se realizan por cada tarjeta x canal pID... ¡muchos servidores grandes han sido muy codiciosos! ;-)
Pero no descarto algunos hosts/direcciones 'ataques' DDOS 'directos' a servidores grandes.... hoy .xyz parece correr sin problemas ¿raro?If so, we would solve it with a cache-only supported vidiation.
-
if through injecting QoS packets they tried to delay the sending of the ECM, the emulator would mark a "timeout" since the time expired and it did not find the response in time. From what we have studied, the problem comes from 2 fronts. 1- R100 versions distributing fakes through their cache. (Attack interested by the creators of multiCS R100 to sell its paid version) 2- Cards in penalty mode. (Movistar attack to penalize sharing) L
-
It is difficult for IKS to fall. The cards in the iks systems are protected by encryption in the firmware of the receivers. Opening an emulator like OSCam and extracting data is very simple, since it is a free "open source" system. To open a firmware of an IKS system it is necessary to obtain the protection keys of the file, and that is very, very difficult to happen. Tracking a card in a home sharing system is child's play for any professional. In addition, iks systems use their own emulators, unknown until now. It is true that an iks system can be unstable at certain times, due to the number of receivers it must feed and especially due to the location of the server and under which support it works, depending on the country of location A server hosted in Spain that maintains a very secure and stable fiber network is not the same as a country in Latam whose connection quality becomes more unstable.
-
Y porque no hacen el ataque constante? Y solo lo hacen en el futbol ? Si es así, está muy trabajado ese ataque y saben cómo funcionan muy bien las emuladoras. Buen trabajo por parte de Movistar
The attack on sporting events is carried out by Laliga. That's why he attacks only in matches. Movistar applied the same protocol to its movie, series and other channels, but they only implement it randomly on alternate days. They cannot use a long duration or very repetitive attack because it would give time to analyze how they do it. Therefore, use small intervals and specific days to attack by surprise. It seems that they are compiling a new emulator that would work against this measure, since it is gradually being implemented in most privacy
-
Apparently the ones in charge of identifying the cards that are shared is the company Tarlogic, they work for LaLiga and Movistar.
-
Dude, for the traffic to be fully tunnelled, there must be an end-to-end VPN network. You can hide your Server by masking the IP and adding layers. But your Client receives the data from your ecm in his deco, at home, with his public IP that his provider can sniff. One thing is to protect your server and another thing is to protect the power line. If you pass me a line from your server and I use a sniffer to analyze the data, I can get your subscriber number. Remember that before the subscription number appeared on TV. That number travels with the ECM that serve your card. With the subscriber number, they already have your name, address and public IP.
-
really the traffic that circulates between emulators is not recorded. The internet provider can sniff the network and identify outgoing and incoming traffic. A VPN network is only good for hiding the server, but it cannot hide the data when the client receives it on his deco. If that client is not using VPN, the provider can find the sender and trace the path. There is already a law in Spain against audiovisual fraud that grants the owners of the rights to implement any means to defend their property. In the past it was not possible to sniff the traffic, currently yes, as long as the intention is defensive, never attack the user. Therefore, they cannot report users who share, they can only defend themselves by penalizing their card. They attack from 2 flanks. 1- Penalization cards in sharing, snifan red, get subscription number and mark your card. Card sends fake ecm (ecm similar to correct with bit deficiency) 2- Bot issuing Cache Peer between MultiCS. They poison the network and spread. Today, we have a very difficult task. Our emulators cannot fight against this technique. We need to stop and analyze how to deal with the problem. They are winning.
-
Has anyone noticed the epg? they are sending prid, shid and msrid. what does this mean?
alguien se ha fijado en la epg? ellos están enviando prid, shid y msrid. que significa esto?
What does this mean?
-
At the moment we cannot stop the problem. They have even knocked down the entire grill at times. I can't identify where they attack me. I have tunneled my traffic between server and client and they still detect sharing. We have no solution. This is over.
-
Good morning, r11704 r798 has many problems with the movistar caid 1810. We have detected that it swallows a lot of fake traffic, and that it blocks when the ECM cycle is not correct. We have tried different configs. but the behavior does not change. In Spain they are damaging us in an unknown way, with fake cw, but apart from that, OSCam blocks without being able to detect the fault. I've never really seen this emulator suffer so much.
-
In order to avoid the input of the cws fakes blocks, we must limit the viewing, filtering our reader with the command "caid = 0100" and assigning priority in the .dvbapi "P: 0100:004106" Movistar+ Remember the importance of closing cache, for some it can be a problem, but we must all avoid spreading the poison or we will never finish this. Comment that receivers with "iks" system do not suffer from these problems. Many of you ask why IKS works. The explanation lies in the fact that the IKS network is closed, all its cards are in the same group, and nothing is shared with anyone. This way they manage to protect their network, and not receive unknown traffic.
-
There are several virtual machines with R100 versions managed by bots, in charge of poisoning the network with Cw fakes blocks. These blocks are propagated through the exchange of Cache and spread from server to server, without the owners of the servers realizing who is sending them the poison. After the studies carried out, we ruled out the Cak7 system, there is no registration in OSCam and, furthermore, it does not affect the SD channel block. There are also no marked cards, all local cards work fine as long as they are not supported by caching. This is tested on several occasions. At the moment, to enjoy a correct viewing, you have to use the caid 0100 of the Seca card and view in SD, blocking the sid that cause problems in the caid 1810, we can do this in the oscam.dvbapi Fellow Atary could edit a good config for this. For the moment we must wait, close the cache swaps and take advantage of the old Seca. We will continue working and I assure you that we will break the problem of black screens. Blessings 🙏
-
because I have researched this topic for a long time and came to the conclusion that someone is trying to profit from your servers, because it is a pay server and wants to mess up other's servers by poisoning the cache. everything comes from the cache and unfortunately it is difficult to control it sometimes they send the same fake CW block used before and send it again for x minutes, then they stop the attack again in games that aren't big they do it once or twice, but in big events they keep doing it the whole game I have and I will not comment publicly, because I know you are looking at all the threads on this topic and you know you are doing well so far
-
Buenas, no consigo ver a mis clientes conectados!! No se que estoy haciendo mal!!
(client) encrypted cccam-client 144.91.87.225 rejected (invalid access)
2022/01/18 00:56:47 5853AD42 c (cccam) account ' Skert7' not found!
2022/01/18 00:56:47 5853AD42 c (client) anonymous disconnected from 144.91.87.225
2022/01/18 00:57:00 230A6E01 c (client) encrypted cccam-client 144.91.87.225 rejected (invalid access)
2022/01/18 00:57:00 230A6E01 c (cccam) account ' Skert7' not found!
El cliente creado Skert7 es el mismo que el que intenta conectarse con la IP 144.91.87.225.
No entiendo nada,!!!
-
if this card running nagra merlin then game over later
cwpk y nuid? Cak7 program?
