Skip to content

v0.3.0-alpha

Pre-release
Pre-release
Compare
Choose a tag to compare
@p2r3 p2r3 released this 28 Sep 00:24
· 68 commits to main since this release

This is an alpha release of spplice-cpp, hopefully eventually known as Spplice 3 or simply Spplice.

  • This is a concept release, the final product will most definitely look and function very differently.
  • Basic package list browsing and installation functionality has been implemented.
  • Stability is priority, and implementation on secondary features has not yet begun.
  • Even then, the features that do exist should not be considered stable.

The Spplice Terms of Service apply to this application. By using this alpha release, you agree to the Terms as presented, and any additions as noted here:

  • Updates to the Terms do not get announced through this application. For that, please use Spplice 2 for now.
  • Clause 3.2. (Reverse Engineering) states that the Application is not open-source. While this is not true for this experimental implementation, you are still prohibited from distributing either direct or inspired derivatives without permission.

Changelog

  • Replaced QuickJS with Duktape to reduce complexity and binary size
  • Replaced RapidJSON with built-in Qt5 JSON support
  • Replaced WinAPI web requests with libcurl on Windows
  • Implemented WebSocket client in JS environment
  • Generic bugfixes

Contents

  • SppliceCPP - Self-contained, (mostly) statically linked x86_64 Linux binary packed using UPX. It has been tested to run on a fresh out-of-the-box Debian system, as well as some Arch systems. A few assumptions are definitely made here.
  • SppliceCPP.zip - Portable Windows archive, containing the application and required DLL files. Qt5 is statically linked in the executable, and everything has been packed using UPX. Loosely tested on a fresh out-of-the-box Windows 10 system. Not all features are guaranteed to work.

⚠️ WARNING: The Windows build currently does not verify SSL certificates.

This could allow an attacker to perform a man-in-the-middle attack, and potentially even run arbitrary code on your system, as libcurl fully trusts the data received by SSL hosts. Realistically, the odds of this happening are incredibly slim, but proceed with caution.