Remove unnecessary services available via home

[jessysaurusrex]

At present, there is an incomplete understanding of which services are exposed in home. (e.g. local), and what capabilities they may provide to different audiences.

Before launch MN-1, a manual review of the list of services provided in home. to ensure that we have removed unexpected behaviors and potential risks for end users. For every service we expose, we should document audience and intended use.

Services that Zoe relies on were attacked directly via home.

[dckc]

At present, there is an incomplete understanding of which services are exposed in home.

We have an enumeration of home contents (home.wallet, ...) under Agoric REPL docs. But I wouldn't call it complete. In particular, note:

• sync REPL home docs with agoric deploy docs · Issue #617 · Agoric/documentation
• Make types of home available to deploy scripts #3154

I just ran into a key piece of documentation: solo/test/test-home.js with several tests along these lines:

agoric-sdk/packages/solo/test/test-home.js

Line 36 in d864c78

test.serial('home.board', async t => {

agoric-sdk/packages/solo/test/test-home.js

Line 168 in d864c78

test.serial('home.localTimerService makeRepeater', async t => {

Services that Zoe relies on were attacked directly via home.

In particluar, I suppose that refers to #4296, #4297.

[dckc]

E(home.board).ids() breaks the paying by message size rule: it returns an arbitrarily large list of strings given an O(1) input.

[arirubinstein]

To be done before solo provisioning / addressing of home by clients

[dckc]

for ref: also known as "mailbox" access (#5965)