Plan of Action / ToDo List

[Neo-Desktop]

In light of the recent exponential interest in this project @Endermanch and I have been working closely to help determine the best plan of action going forward.

My intention for this repository is to be a bit of a shared code base (if not eventually a shared library) that will do a significant part of the "heavy-lifting" for generating keys.

The components of which will be as followed:

• Accurate PID generation based on product family (see: Use dpcdll.dll to get site codes/channel IDs #15 )
• ECDLP Signing from extracted and calculated keys [1] (see: ECDLP Signing Key Generation #2 )
• A (somewhat) standardized method for storing the above values (keys.json)
• Transition to using CMake

---

An additional project related to this is the Telephone Activation utility which will ultimately be included in this repository: (See #1 )

• A port of the Telephone Activation utility to the command line (eventually as a library) for platform agnostic use - thanks @WitherOrNot ! add confirmation ID generator, fix server.cpp #14
• An extension of the above utility to handle the various products (typically in the retail branch) that require activation
  • Develop a method to pragmatically extract constants from the products that require activation (see: Product Activation Constants #17 )
• A ground up rework of the existing confid.cpp

---

• CLI Refactor to use a new style keys.json file
• Have compile-time options to generate a shared or static library for the project
  • One export for all of UMSKT called libumskt / umskt.dll
• Docker-based environment for easy static and cross compiled builds (see: Add Dockerfile for easy compilation #29 - thanks @brakmic! )
• Full releases (meaning one that includes a resource compiled keys.json)
• Research possibility of compiling with DJGPP (and even automating builds via GitHub actions)
• Add Windows 32bit compilation
• Add DOS DPMI compilation
• Research possibility of emscripten builds
• Transition from OpenSSL to Crypto++
• Improve documentation of activation mechanisms

---

One of my personal requirements for this code is to take a Linux first approach, we start small and work our way up, if platform specific needs arise, we will handle them one at a time.

Thank you for your patience with us as we sort though everything and compare notes on our projects, we'll get things going shortly, the warm and positive repose from the community is all very overwhelming.

---

Update: 2023/06/11

In doing research to the extent of which products use PIDGEN/DPCDLL/LICDLL (and derivatives) I think its a wise decision to use some type of database to manage all this information.

I've started using an sqlite 3 db and intend to write a script that generate a keys.json file from it in the near future.

A SQL file (db dump) that can populate the database will be provided in the repo

---

[1] NB: One of my personal gripes with how we're handling keys is that private keys must be recalculated from the inverse (-K_y) of the public key or it is currently unusable to us. And while with modern machines this is more or less trivial to do, it doesn't feel right to me. There is a better way that is currently used by another keygen called mskey4in1 and I find it imperative that I replicate whatever algorithm the programmer there used first.

Edit: 2023/05/31 - figured it out! progress!

The problem (and main blocker) here is that collectively those currently involved with this project are somewhat novices at Elliptic Cryptography, both your patience is requested and anyone with hints/tips/tricks that may be of assistance is more than welcome to get in touch with us.

[thepwrtank18]

The last checkbox needs to be updated, we got the constants