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
{{ message }}
This repository has been archived by the owner on Dec 28, 2022. It is now read-only.
Wondering if hypercore can or thinking about supporting middleware for use cases like auth. For example, a hook that checks a signature before accepting a mutation or returning a value.
This is great if you had a node that tries to mutate logs, kv, etc without the permission to do so. Other nodes on the network should be able to check signatures in those messages before accepting.
Blacklisting peers would also be a nice feature for repeat offenders.
The text was updated successfully, but these errors were encountered:
maurerbot
changed the title
FEAT > Middleware DI for custom hook in the system
FEAT > Middleware DI for custom hooks/handlers
Dec 24, 2021
The problem I'm trying to solve is attributing a static keypair to a set of keys in hyperbee KV so that only the holder of the keypair can access specific keys.
For example, a daap discovers and connects to hypercore peers and the daap user "logs in" using their wallet. They should only be able to access (read and write) content they own.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Wondering if hypercore can or thinking about supporting middleware for use cases like auth. For example, a hook that checks a signature before accepting a mutation or returning a value.
This is great if you had a node that tries to mutate logs, kv, etc without the permission to do so. Other nodes on the network should be able to check signatures in those messages before accepting.
Blacklisting peers would also be a nice feature for repeat offenders.
The text was updated successfully, but these errors were encountered: