You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement the internal route restriction to whitelisted forger(s) : it is implemented on 2.6 branch so you might have a look (search for isForgerAuthorized).
On 3.0 this would need to be done as a plugin (like packages/core-p2p/src/socket-server/plugins/accept-peer.ts for example, you would plug the plugin on the same onPreHandler hook).
Basically all incoming requests for internal routes (see packages/core-p2p/src/socket-server/routes/internal.ts) should be only allowed to whitelisted forger (we whitelist forger using remoteAccess config parameter, see packages/core-p2p/src/defaults.ts)
The text was updated successfully, but these errors were encountered:
Implement the
internal
route restriction to whitelisted forger(s) : it is implemented on 2.6 branch so you might have a look (search forisForgerAuthorized
).On 3.0 this would need to be done as a plugin (like
packages/core-p2p/src/socket-server/plugins/accept-peer.ts
for example, you would plug the plugin on the sameonPreHandler
hook).Basically all incoming requests for internal routes (see
packages/core-p2p/src/socket-server/routes/internal.ts
) should be only allowed to whitelisted forger (we whitelist forger usingremoteAccess
config parameter, seepackages/core-p2p/src/defaults.ts
)The text was updated successfully, but these errors were encountered: