DEV Community

Cover image for The CGS Technology Has Been Replaced, Not Delayed

The CGS Technology Has Been Replaced, Not Delayed

Recently, NMBAH proudly announced several features of the CGS-6iP Technology, a cryptographic solution called "Violent Module", which promised extreme protection. However, we hereby notify that CGS-6iP will no longer be launched. Instead, it will be replaced by another technology set to arrive too in 2025.

Reasons for the Decision:

  1. The Technology Is Not Secure Enough
    At NMBAH, we promise extreme security and explicitly refuse to deliver defective products. While delays may occur, releasing flawed systems is never an option. The technology had several issues, one of which was the "Glue Glitch". This glitch caused the encryption process to fail and rendered it irreversible, exposing parts of the code due to delayed loading and mismatched keys. This flaw made the output unreliable and left critical vulnerabilities.

  2. Insufficient Keys
    The system relied on 17 keys of 255 characters, as it was based on a 255KB architecture. However, these 17 keys were inadequate because the system generated infinite patterns that were not entirely randomized. When similar content was encrypted, such as pasting a code snippet resembling the IDE itself, it could expose logs in the browser console. This behavior was hazardous and undermined security.

  3. Nonfunctional Technology
    Although CGS-6iP worked to some extent, it encrypted data with overwhelming complexity. Simple code like print("Hi") could result in encryption exceeding 500,000 characters, rendering it impractical. Moreover, even we couldn't decrypt it afterward. Testing revealed that the encryption process looped randomly, growing until the browser could no longer handle it. This flaw compromised security and could not be resolved.


— Why Was V7 Skipped?

NMBAH planned to release two versions of CGS: one private and one public. However, neither version is viable now, as the 50,000+ lines of code have become corrupted and unusable. Fixing this would take an unreasonable amount of time, especially since the technology's inherent flaws already compromise its purpose and our users' safety.


What’s New?

The upcoming V8 (CGS-8iP) will feature innovative implementations, including AES-256 encryption. Although slightly less complex than CGS, AES-256 would still require billions of years to crack. By leveraging AES-256 as the primary encryption layer, we can add further strength through code obfuscation and scrambling. This approach addresses the primary issue: encryption. With the encryption solved, additional layers of protection can be added, such as:

Dynamic keys that update every second.

Enhanced service optimization.

The new system will be entirely private, though public documentation may be released to explain its functionality.

The End of CGS-6

CGS-6 is officially canceled and will be discarded as it violates our privacy policies, such as Directive 347:
"No product can be released unless it is fully functional and compliant."

Replacing a technology without notification would also violate our policies. The core objective of CGS is to “Gangrene the Source” making the code completely ilegible. This involves splitting user code into random chunks, scrambling their order, and encrypting them with keys that store their correct arrangement.

For a hacker to retrieve the code, they would need massive keys exceeding 255 characters, just to locate a single piece.

By integrating AES with CGS, we achieve even greater security. AES offers a reliable foundation that is further obfuscated and "gangrened" to become completely unreadable, even with keys.

The Original Vision Remains

The goal of CGS was to provide a Brutal and Unique Technology, and its essence its at our slogan:
“Gangrene the Source.”

With the new system, even if a hacker obtains your code and keys, decrypting it would involve overcoming multiple layers of encryption, obfuscation, and randomization, all while the system dynamically updates every second. This makes unauthorized access virtually impossible, even for automated systems, queued in sync with localhost.

This is what we aim to deliver, staying true to our promises. Thank you for your attention.

The CGS isn’t canceled; it is being replaced by a stronger version. The new system encrypts with AES-256, gangrenes the code, encrypts it twice, and obfuscates it every second, maintaining the high level of service you expect.

Sincerely,
Kirey Cazkdnsky

Top comments (0)