Skip to content
vFileLock powered by VOIMARvFileLock powered by VOIMAR

Security and standards

Livewith planned items markedPlanned

The first rule: VOIMAR never decrypts

Files are locked and opened in the browser. vFileLock's servers receive locked files only, and they have no code that could decrypt one. They read just enough of a file's outer wrapping to check that it really is locked. A plain file, or a private key sent by mistake, is refused and the refusal is recorded.

The standards

Live

OpenPGP, RFC 9580

Every locked file is a standard OpenPGP message. The check that a file is locked follows RFC 9580, and RFC 4880 for older files.
Live

AES-256

Files are encrypted with a 256-bit AES key, the strongest cipher in OpenPGP's common set.
Live

Curve25519

Personal keys are elliptic-curve keys made on your device: X25519 to encrypt, Ed25519 to sign. They use the key format desktop OpenPGP tools read today.
Live

Integrity protection

Files are written in OpenPGP's integrity-protected format: SEIPD version 1, with a modification detection code. A changed file refuses to open, and desktop OpenPGP tools read the format.
Live

AES-256-GCM

The key half vFileLock keeps is sealed with AES-256-GCM, authenticated encryption bound to the share it belongs to.
Live

SHA-256

The fingerprint of every locked file, every link in the ledger's hash chain, and the fingerprint of each terms and policy version a person accepts. The key register accepts RFC 9580 (v6) keys, whose fingerprints are SHA-256.
Planned v6 keys made by default.

with a planned step

The split key

Sender’s browser
  1. Locks the file with a fresh 256-bit key
  2. Splits the key in two
AB
AIn the link, after the #

Browsers never send this part of a link to a server. Send the link any way you like.

BSealed at vFileLock

Released only when every rule passes: the right person, the code, the time, the opens left.

PersonCodeTimeOpensApproval
Recipient’s browser
  1. Proves who it is: the code, or Voimar ID
  2. Joins A and B
  3. Opens the file in the page
AB
Either half on its own says nothing about the key. VOIMAR never holds both halves.
  1. The sender's browser makes a fresh file key: 32 random bytes, 256 bits. It locks the file with OpenPGP using that key.
  2. It splits the key in two. Half A is 32 new random bytes. Half B is the key combined with half A (XOR). Either half on its own says nothing about the key.
  3. Half A goes into the link, after the #. Browsers never send that part of a link to a server, and vFileLock's pages tell the browser not to pass the address on.
  4. Half B goes to vFileLock, sealed with AES-256-GCM. vFileLock releases it only when every rule passes: the right person, the code, the time, the number of opens, the approval.
  5. The recipient's browser joins the halves, opens the file in the page, and clears both halves and the key from memory when the page closes. Half A is also removed from the address bar once the file is open.
  6. Revoke, expiry, the last allowed open and burn destroy half B. From then on every copy of the link is dead, forwarded or not.

Share numbers are 128-bit random values, so nobody can guess one. Codes come from a secure random source, are kept only as a keyed hash, and are compared in a way that leaks nothing about how close a guess was. Limits on tries and lockouts stop guessing.

What VOIMAR can see, and what it cannot

VOIMAR can see

  • The file's name, type, size, level and category
  • The SHA-256 fingerprint of the locked file
  • The owner, custodians and approvers
  • The recipient's address, to send the code (the compliance record keeps only a masked form and a keyed hash)
  • The rules, every time stamp, the IP address and device of each open
  • The locked file itself, while a share needs it

VOIMAR cannot see

  • What is inside the file
  • Half A of the key, or the whole key
  • Codes, in readable form
  • Your private key or its passphrase
  • A readable copy of anything you lock

Coming the country of each open, read from a list kept on our own servers, with no outside lookup.

Approvers and Information Officers see the same kind of details. Never the contents. No role, VOIMAR's own administrators included, gets a way to read a file through vFileLock.

The one exception is your choice. With optional key escrow and recovery under dual control Coming, VOIMAR's vault holds one recovery key for your organisation. It can be used for one file at a time, only when your recovery officers and a VOIMAR Super Admin approve together, and every step is on the record. Without escrow, VOIMAR cannot open your files at all. See Key escrow and recovery.

Where it runs

  • Hosted in South Africa, on VOIMAR's own network. No foreign cloud.
  • Sign-in through Voimar ID, VOIMAR's own sign-in service.
  • Nothing vFileLock answers is cached, and nothing is indexed by search engines.
  • Database backups hold sealed key halves until the backups rotate. A backup still opens nothing, because half A was never on our side.

A record that shows any change

Every event is chained to the one before it with SHA-256. Changing or deleting an entry breaks the chain. The newest entry of every chain is also lodged in POPIA Bridge's own record, so a removed tail shows too. Anyone who may read a ledger can check it. More on POPIA Bridge.

Open standards, no lock-in

Files are standard OpenPGP. The ledger exports as CSV and JSON with the chain proof, and the classification policy exports as JSON. Another tool can check your evidence without vFileLock.

Honest limits

  • A file cannot wipe itself on someone else's device.
  • Nobody can stop a photo of a screen or a recording of a speaker, and a browser cannot block screenshots.
  • A copy the owner allowed to be downloaded is out of reach once saved. The link still stops working.
  • A file is only as safe as the device it is opened on.

That is why sensitive files open view only, with the recipient's name on every page, and why every open is on the record.

See vFileLock with your own files and rules

Bring your Information Officer, your security officer and your IT lead. Or open vFileLock and lock your first file.