The Files page described marking without saying where it stops.
A level decides who can open a file. It does not decide where a file can be put: somebody who can read something can still file it somewhere less protected. The page now says so rather than leaving the word to do the work.
Part of ios#65 / android#15, which asks for the honest version now and a trusted downgrade later. Checked first whether anything already claimed Bell-LaPadula: nothing does, on any page or in any doc, so there was no claim to retract.
Tests: 697, 0 failures.
The Files page described marking without saying where it stops.
A level decides who can open a file. It does not decide where a file can be put: somebody who can read something can still file it somewhere less protected. The page now says so rather than leaving the word to do the work.
Part of ios#65 / android#15, which asks for the honest version now and a trusted downgrade later. Checked first whether anything already claimed Bell-LaPadula: nothing does, on any page or in any doc, so there was no claim to retract.
Tests: 697, 0 failures.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The Files page described marking without saying where it stops.
A level decides who can open a file. It does not decide where a file can be put: somebody who can read something can still file it somewhere less protected. The page now says so rather than leaving the word to do the work.
Part of ios#65 / android#15, which asks for the honest version now and a trusted downgrade later. Checked first whether anything already claimed Bell-LaPadula: nothing does, on any page or in any doc, so there was no claim to retract.
Tests: 697, 0 failures.
mentioned in commit
541f9606af