specify options NOT to enforce/override via borg serve

[ThomasWaldmann]

== whitelist options determined client-side (and everything else is enforced server-side) - this avoids such security issues.

See there: #4095 (review)

---

💰 there is a bounty for this

[step21]

Hi, probably this is simple, but I want to be sure that I understand it -
edit: strike that. I am just not sure yet what is the closed and what the open part in fail close/open with regard to this. As only expected options are explicitly specified, isn't this already whitelisting?

[ThomasWaldmann]

the point is just that using a whitelist will cause limited functionality if we forget to add something to it (the new stuff won't work).

forgetting to add something to a blacklist causes a security issue though (client being able to use something they should not be able to use).

[ThomasWaldmann]

@step21 are you still working on that?

[step21]

Yes, but I somehow got sidetracked, sorry. Maybe I'll get something done till the end of the week.

[ThomasWaldmann]

@step ping :)

[ThomasWaldmann]

Looking at this right now...

[ThomasWaldmann]

Going to have a whitelist and a blacklist.

The latter will make sure known-critical stuff (which must be enforced server-side) is not accidentally whitelisted.