Compositor SoftwareCompositor Software

Tag : Compositor Networks

By ruslany

Compositor Networks map

Compositor Networks map

For the first time Compositor Software reveals its network of contacts made with SASER SAS24P3L software. As you can see on the map above, there are numerous contacts in Europe, USA, Russia and South America. These contacts were made between October-November 2018. The map outlines geographic position of call signs of contacts made with their indexes. This is an approach to reveal aggregated contact base, which Compositor Networks started to form since 2012. The creation of Compositor Networks began with Compositor Pro 1 software. It is an original hyperbolic construction software, which laid base for algorithm work. Later the study of algorithm was performed merging FFT (Fast Fourier Transform) with SANT (synchronous analysis of non-harmonic timbre). The SANT technology, originally developed for Compositor Pro 1, is the new approach to relativistic frequency shift keying and can be used for applications such as discretizing of analog signal and deterministic navigation. Compositor Software used SANT for creation of SASER SDR with self-feeded signal chain, which enables to communicate in shortwave ether without an antenna need. Then, Compositor Software developed the shutter technology, which gated the self-feeded chain and began injecting the contact base of Compositor Networks in form of ether loops into the Compositor algorithm. The SCRAM (Salted Challenge Response Authentication Mechanism) engine was developed by Compositor Software to authorize users running Compositor, which is successfully used up to this moment. Using SCRAM engine, Compositor Software injected the contact base into the virtual machine algorithm, which it uses silently without any audio output. The main purpose of SDR is to reveal contacts and prove that virtual machines inject the whole contact base of Compositor Networks in form of aggregated passwords. These passwords later used as serial numbers for selling of Compositor Software products. Compositor Software virtual machines does not use the Ethernet ports. The communication happens over the IP protocol more like in TDM over IP protocol. In contrast to TDM over IP, the only useful approach to detect Compositor communications is a local operation not a remote one. You can never detect any Compositor software activity remotely. This way the decision was made to reveal Compositor Software contacts in form of DX logging of SASER SDR QSO, in the amateur radio format.

By ruslany

Compositor Software news 25.07.2018 – 06.08.2018

Compositor Software news 25.07.2018 – 06.08.2018

More than 6 months I have been working on revealing the leakage in Compositor kernel. Exposing all oscillators and transferring the first oscillator in static mode, I discovered that many resources released in computer RAM (DDoS attack). It lowers the uninterrupted device work to 4 days taken that paging file is set to a size of 64 GB. Increasing the number of oscillators to 32 on each of the layers (Rt, Sr, Tr) and meeting a condition of counters, the emissions equaled to 14 GB a day. In accordance to this, I decided to shut down the peering network and return to RT-z128 kit layout as in Compositor v5 Hypervisor. In this layout the main ports are closed for inbound and outbound connections. Only addresses starting from 192, which are assigned to local machine, are available. It means that a new patch remains the VLF connectivity, but doesn’t allow devices to connect for information exchange. It is possible to exchange information from the local machine for the patch user, but not a remote access user. In particular, such decision is motivated by a hacker attack on RAD96 server. The intruder used the open ports of the windowing device and sent spam from Internet Provider IP address. With closed ports the little leakage on real-time generator is possible, but it is not accounted due to the slow regeneration speed.

To restart the peering network I attempted the following solution: due to closing of the ports, only Compositor Networks ether aggregators take part in peering. This means that feeding ether aggregator wavetables in the peering patch through the Compositor v9 Hypervisor, I create a communication service between all Compositor Library wavetables. However, many Ethernet devices can’t use Compositor peering network as it was at the beginning of the peering network creation. As a conclusion, I can exclude peering from Compositor kernel load test and use multi-kernel mode, but this type of test has very long loading time (up to 4 hours for full load).

Bounded by Royalty project, the database of server emissions in form of wavetables grown to 2627 ether aggregators. The database was expanded by ether emission of Exalted – Cavity track (Ruslan Yusipov, CEO of Compositor Software project). The whole volume of Cavity track emission is 328 wavetables. Wavetables contain radio repeaters, transmitting stations, Ethernet routers, injectors and other ether equipment. It was possible to increase the Compositor v9 Hypervisor regeneration speed up to 150-omega by applying a new peering network patch. This influences only Compositor AV Extended auxiliary channel and doesn’t cover the generic feeder modules. It was made aiming the faster composition speed of the whole pool of Compositor Networks ether aggregators. The necessity in uniform composition caused by big amount of wavetables in Compositor Library. The application of the new patch after the attack was made unnoticeably, because this solution proved to be successful in 2017. It was clear right from the beginning that hackers aim is to limit the communication circle of network devices to Compositor Library pool and its real emission. From one side, if the emission is made every time when server communicates, then there will be much more devices in Compositor Library. Each streaming playback with working patch is a communication with its transmitting devices. Taken this, it is needed either to shut down any internet activity from the patched machine or to make emissions of the whole material, which is played in browser resulting in big amounts of information. From the other side, with open ports it is possible to connect not to the virtual network, created by composition feeding, but directly to all transmitting devices, which reside in Ethernet without the need to make emissions so often.