Skip to content
jsonW Paper GitHub

Versions and security

jsonW 1.4.1: the permission view applies to every command that reads values

In 1.4.0, only ver and the web server hid personal columns. 1.4.1 fixes it in every command that reads values: on the same test file, 23 of 37 checks failed before and 0 of 37 fail now.

· jsonW 1.4.1

What was wrong

A column marked +pessoal, such as a CPF, should show only to whoever holds the right scope. In 1.4.0 this rule applied to ver and to the web server, but not to the other command-line commands. Three paths let the value escape:

What 1.4.1 changes

The same view now applies to ver, para-texto, filtrar, calcular, escolher, avaliar, comparar and info. Without WJSW_ESCOPOS, the +pessoal and +escopo(x) columns come out null. A condition, a group or a score on a hidden column stops with a clear error:

coluna sem permissao: cpf (exige escopo)

The output file writes the hidden column as null. With a tenant view, the filtrar header shows only the rows the session can see, not the total of other tenants.

How it was measured

The same test file ran on both versions, on macOS arm64. 1.4.0 failed 23 of 37 checks; 1.4.1 fails 0 of 37. The whole suite also passes under AddressSanitizer and UBSan on Linux.

What stays outside the view

regravar, cifrar, decifrar, de-texto, de-json, conferir, reparar and medir do not apply the view. They are owner operations and copy the whole file. So the rule stays the same: do not hand the raw .jsw to someone who should see only part of it. Hand over the output of ver or of the web server.

Who needs to update

Whoever uses +pessoal or +escopo(x) columns. The file format did not change: 1.4.1 reads every file written by 1.4.0, 1.3.x and 1.2.1, and the package is on npm as @wortictecnologia/[email protected].

jsonW 1.4.1 (GitHub, release notes) →