Repository navigation
Releases
KryptoCore Rescue 0.1.0-preview.4
KryptoCore Rescue 0.1.0-preview.4
Windows x64. Extract the ZIP and run KryptoCore-Rescue.exe. No separate .NET installation is needed.
- Authenticate KCV1 through KCV4 and export Vault logins to a new JSON file. Use the matching password or configured emergency credential. The input stays intact.
- Existing KCC extraction and optional sender verification remain available. Use a protected destination for plaintext and retain encrypted backups.
- The ZIP and its EXE match both Windows builds from this Actions run. The source commit and both build records identify the tested binaries. The ZIP has a detached publisher signature. Windows Authenticode and independent audit are pending.
KryptoCore Rescue 0.1.0-preview.3
KryptoCore Rescue 0.1.0-preview.3
- Verify shared KryptoCore
.kcsigsender signatures for ordinary and wrapped KCC files with a separately trustedKCP1:public code. - Hash the same stream being decrypted, including the executable wrapper/footer. Invalid requested signatures block both scanning and publication.
- Add optional local ClamAV scanning before export, including Vault JSON. Detection, scanner errors, timeout and unsupported bounds block output.
- Bound KCC plaintext to 400 MiB when scanning is requested; scan limits are 100 MiB per file and 400 MiB total.
- Display content authentication, selected-key signature verification and scan state separately. No automatic opening or execution.
KCV1/KCV2 and KCC bytes remain unchanged. Sources and existing destinations
are preserved. Vault password/recovery exports continue to work. Output is
plaintext; choose a protected destination and retain backups. MSG recovery
remains unimplemented. The app is unsigned and independently unaudited.
Scanner process-control tests use deterministic surrogates and do not measure
real ClamAV detection efficacy. ClamAV and its current database are external.
The recorded source revision is publicly accessible. This preview was built in a local Windows workspace. Independent binary reproducibility has yet to be established.
KryptoCore Rescue 0.1.0-preview.2
KryptoCore Rescue 0.1.0-preview.2
First downloadable recovery preview, extending the earlier marker-only prototype.
- Authenticate KCV1/KCV2 Vaults and export validated records to a new JSON file.
- Use the original password or an existing KCV2 recovery slot without resetting the source password.
- Extract ordinary and executable-wrapped KCC containers using the existing stream reader.
- Require plaintext-output confirmation and a fresh destination; clear credential input after use.
- Keep diagnostic reports metadata-only and clearly unauthenticated.
The output is unencrypted. Existing files and directories are not overwritten.
MSG files can only be recognized; MSG decryption and recovery are not implemented.
No sender-signature verification or malware scan is performed. The executable
is unsigned; independent review is pending. Use copies and retain backups.
SHA256SUMS.txt identifies the published bytes. RELEASE_MANIFEST.json records
the private source revision, toolchain and test scope. Checksums are not a
substitute for obtaining software and expected hashes through a trusted route.