![Maven Central Adds Sigstore Signature Validation](https://cdn.sanity.io/images/cgdhsj6q/production/7da3bc8a946cfb5df15d7fcf49767faedc72b483-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Maven Central Adds Sigstore Signature Validation
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
exchange-protocol
Advanced tools
Hypercore-extension that allows peers to exchange feed-descriptors
Hypercore-extension that enables two peers to exchange feed keys and descriptors.
Following extension hosts are supported:
Take a look at exchange-protocol docs page for a higher level description and sequence diagrams.
Given the following manifest:
// Header-values are allowed to contain primitive types or Buffers
// if you want to use a custom encoder/decoder
const myManifest = [
{
key: 'deadbeefdeadbeefdeadbeefdeadbeef',
headers: { seq: 1, hello: 'world' }
},
{
key: otherKey,
headers: { seq: 55, hello: 'planet', title: 'My awesome feed' }
}
]
And given the following handlers Object:
const exchangeHandlers = {
onmanifest (shared, accept) {
shared.namespace // => String - 'default'
shared.feeds // => Array<Object> - offered keys
for (const feed of feeds) { // Print the manifest contents.
console.log('Remote Shared feed:', feed.key.toString('hex'))
console.log('Headers:', feed.headers, '\n')
}
// `accept` is a Function that directly responds to a given
// manifest with `FeedRequest'
const acceptedKeys = shared.feeds.filter(...).map(f => f.key)
accept(acceptedKeys) // accept all keys
// This is a stub, you should let your replication manager
// take care of joining the other feeds into the feed stream.
acceptedKeys.forEach(key => {
coreStorage.get(key).replicate(true, { stream: myPeerStream })
})
},
onrequest (req) {
req.manifest_id // => Number - increment
req.namespace // => String - 'default'
req.keys // => Array - requested keys
// Another replication manager stub
req.keys.forEach(key => {
coreStorage.get(key).replicate(false, { stream: myPeerStream })
})
},
onerror (err) {
throw err
}
}
Using hypercore-protocol
const Protocol = require('protocol')
const stream = new Protocol(true)
const ext = exchange(stream1, exchangeHandlers)
const key = Buffer.from('deadbeefdeadbeefdeadbeefdeadbeef', 'hex')
const channel = stream.open(key, {
onopen () {
ext.sendManifest('default', myManifest, ch1, (err, acceptedKeys) => {
console.log('Remote peer selected', acceptedKeys)
})
}
})
Or using vanilla hypercore
const hypercore = require('hypercore')
const ram = require('random-access-memory')
const exchange = require('exchange-protocol')
const feed = hypercore(ram)
const ext = exchange(feed, exchangeHandlers)
feed.on('peer-open', peer => {
// Arguments: namespace, myManifest, target, callback
ext.sendManifest('default', manifest, peer, (err, acceptedKeys) => {
// Callback invoked on response from remote peer.
// The `requestedKeys` are a copy of `req` param in `onrequest`,
// they should be handeled in onrequest.
})
})
Result
In a real world scenario your peer would not be communicating with it self.
But in this example, if we were to send myManifest
to the exchangeHandlers
the log lines would produce the following output:
> Remote shared feed: deadbeefdeadbeefdeadbeefdeadbeef
> Headers: { seq: 1, hello: 'world' }
>
> Remote shared feed: 1234feed43afdeafa41efeed4124beeb
> Headers: { seq: 55, hello: 'planet', title: 'My awesome feed' }
>
GNU GPLv3
FAQs
Hypercore-extension that allows peers to exchange feed-descriptors
The npm package exchange-protocol receives a total of 2 weekly downloads. As such, exchange-protocol popularity was classified as not popular.
We found that exchange-protocol demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.
Security News
CISOs are racing to adopt AI for cybersecurity, but hurdles in budgets and governance may leave some falling behind in the fight against cyber threats.
Research
Security News
Socket researchers uncovered a backdoored typosquat of BoltDB in the Go ecosystem, exploiting Go Module Proxy caching to persist undetected for years.