Skip to content

History / Updates

Revisions

  • docs(wiki): the non-exportable login key and the fail-closed updater - Updates: an update is offered only for an .msi from this project's releases with a published SHA-256; it downloads into a fresh temp folder and the digest is checked again right before the Windows Installer opens the file, including the administrator retry (#58, #59). - An Basetool senden, Datenschutz: the stored login holds the token and only the name of a non-exportable key kept in the Windows key store (TPM where present), so a copied entry is useless elsewhere; members of 2.9.1 and older sign in once after updating (#58). - Deinstallation: disconnecting also deletes the key from the Windows key store. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>

    @greluc greluc committed Sep 22, 2026
  • docs(wiki): align every page with v2.9.1 and the web tool as it ships - Sending to the Basetool needs version 2.9.1: since the identity move of 2026-09-14 older builds fail with "unrecognized_name". - The release file is Basetool.SC.Extractor-<version>.msi; size and the VirusTotal result are re-measured. - The app does store settings: config.json in %APPDATA% holds the last channel folder and the send consent, written by the first successful Blueprint run. - The three messages that block sending, the REFINERY SYSTEM C47.02 terminal look, and the real manual-import paths in the web tool (Raffinerieverwaltung -> Neuer Auftrag, and Meine Blueprints -> JSON importieren). - The owner's handle in the data-format example is a placeholder now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>

    @greluc greluc committed Sep 22, 2026
  • docs(wiki): the Defender false positive, and how to verify a download Members meet Microsoft Defender before they ever open the app, and the handbook had nothing to say about it - the answer lived only in the English README. New page `Virenwarnung-und-Echtheit`: why an unsigned MSI with no reputation and a self-updating installer reads as `Trojan:Script/Wacatac.H!ml` to an ML classifier, and the three ways to check the file instead of trusting the claim - the VirusTotal report linked from every release, the SHA-256 via Get-FileHash, and the signed SLSA provenance attestation via `gh attestation verify`. Linked from Home, the sidebar, Installation, Updates and Fehlerbehebung. Also documented the three send failures that were missing, all of which a retry cannot fix, so the page has to say what would: - The system clock outside the narrow window a signed request is accepted in, with the way to synchronise it. This is the live failure mode of the DPoP binding and it presents as "sign-in is broken". - "Nur von freigegebenen Programmen" - a fork with a changed client id, refused permanently by the server-side allowlist. - The DPoP nonce handshake this build deliberately does not implement, which needs a new release rather than a second attempt. Datenschutz now explains why the remembered sign-in sits in one record with a private key: the token is bound to it, so a copy of the token alone is worthless. Corrected sizes that had not moved since the OCR models and the ONNX runtime were bundled: the MSI is ~110 MB, not ~60 MB, and the installed program is ~185 MB across ~220 files, not ~515 files. Signed-off-by: Lucas Greuloch (greluc) <lucas.greuloch@gmail.com>

    @greluc greluc committed Sep 1, 2026
  • docs(wiki): App startet nach dem Update automatisch neu Updates-Seite an das neue Verhalten angepasst: Der Installer-Helfer startet die installierte App nach dem Einspielen (bzw. Rollback) selbst wieder; manueller Start nur noch als Fallback. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

    @greluc greluc committed Jul 5, 2026
  • docs(wiki): Error 1926 (Config.Msi / non-system-drive) beim Update dokumentieren Neuer Fehler-Eintrag zu "Could not set file security for file …\Config.Msi\ ….rbf. Error: 5" (endlose Schleife auf D:/E:), Beschreibung des neuen Dialogs "Als Administrator erneut versuchen?" in Updates, und C:-Empfehlung bei der Ordnerauswahl in Installation. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

    @greluc greluc committed Jul 5, 2026
  • docs(wiki): deutsches Benutzerhandbuch Vollständiges deutschsprachiges Wiki als Handbuch: Installation, Updates, Deinstallation, Bedienungsgrundlagen, beide Workflows (Blueprints, Refinery), Ollama-/Hardware-Einrichtung, Screenshot-Leitfaden, Review & Auffälligkeiten, "An Basetool senden", Datenschutz, JSON-Datenformat und Fehlerbehebung/FAQ. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

    @greluc greluc committed Jun 28, 2026