Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
@rsksmart/rif-communications-pubsub-bootnode
Advanced tools
Simple bootnode for RIF Communications PubSub
Simple boot node for RIF Communications PubSub
The aim to provide a libp2p node which serves as bootstrap node for projects which use rif-commmunications-pubsub
.
This can be also used for local development where you can define the list of Rooms that will be listened on and messages printed out to STDOUT.
Example of usage:
npm start
Spawns a new libp2p node with new PeerId listening to TCP connections on port 6030.
NODE_ENV=develop npm start
Spawns a new libp2p node with PeerId QmbQJ4FyVBAar7rLwc1jjeJ6Nba6w2ddqczamJL6vTDrwm
listening to websocket connections on port 6030 and joins rooms 0xtestroom
and 0xtestroom2
. Any peers joining and leaving the room will be logged as well as any messages in th following format:
<roomName>: peer <peerId> joined
<roomName>: peer <peerId> left
<roomName>: message {from: <peerId>, data: <content of the message>}
<roomName>: message {from: <peerId>, data: <content of the message>, to: <peerId>} // Only for direct messages
In ./config
. You can switch between configurations by setting NODE_ENV
variable. Local configuration is good to put to local.json5
file. For configuration mechanism please visit the node-config page.
// Libp2p config
libp2p: {},
// Peer ID in a JSON format
peerId: {},
// Rooms to subscribe to, strings
rooms: []
RIFC_ROOMS
(json/array): same as rooms
optionRIFC_LISTEN_ADDR
(json/array): same as libp2p.address.listen
RIFC_PEER_ID
(json): Peer ID JSON like specified in `js-peer-idThis project can be deployed with Dockerfile bundled with this repo. Ports 6666 and 6667 have to be published. Also if this is deployed on production level stable PeerId should be used. If PeerId is not defined than over restarts it will change, which should not happen for production boot nodes.
You can generate one using npm run generate-peerid
and then set that either with config file or RIFC_PEER_ID
env. variable (set the variable as the whole generated JSON).
$ PEER_ID=$(npm run generate-peerid) // This should be stored in some file somewhere
$ docker build -t rif-comunication-bootnode .
$ docker run -e RIFC_PEER_ID="$PEER_ID" -p 6666 -p 6667 -it rif-comunication-bootnode
FAQs
Simple bootnode for RIF Communications PubSub
The npm package @rsksmart/rif-communications-pubsub-bootnode receives a total of 0 weekly downloads. As such, @rsksmart/rif-communications-pubsub-bootnode popularity was classified as not popular.
We found that @rsksmart/rif-communications-pubsub-bootnode 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.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.