This repository has been archived on 2026-10-15. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
Paul Hitt 3820b08bea The wire layer, recovery codes, share links, and a command-line client
Everything between the engine and an app: server discovery, the account
service, the file API, and a session that ties them together.

Recovery codes and share links move into the engine, and both agree with
the browser character for character — the vectors file now carries codes
generated by the JavaScript implementation, including one containing a Q,
because folding Q is the mistake that once corrupted a third of all codes.
BigInteger drops leading zero bytes, so decoding left-pads rather than
trusting the length; there is a test for exactly that.

`X25519.publicFromPrivate` recovers the public half by agreeing with the
basepoint. JCA hands back a public key only from a freshly generated pair,
and a session that unlocked a stored record has just the scalar — storing a
second copy would only create something that could disagree with itself.

`filesctl` exists so the cryptography can be exercised without an app, an
emulator, or a person tapping. Verified against the iOS engine as well:
one uploads, the other downloads, and the digests match.

MIT, matching the server. CI runs the suite on a plain JDK image, which is
the point of keeping this out of an Android module.
2026-08-21 18:17:30 -04:00

11 lines
284 B
YAML

# The engine and client are plain JVM libraries precisely so this needs no
# Android SDK and no emulator. A suite that needs a device is a suite that
# runs rarely.
default:
tags: [vps]
test:
image: gradle:8.10-jdk21
script:
- gradle :engine:test :client:build --no-daemon