
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
multilevel2-http
Advanced tools
Access a leveldb instance from multiple processes over HTTP under secure credentials.
A limitation of LevelDB is that only one process is allowed access to the underlying data. multilevel2-http exports a LevelDB instance over http. Furthermore, it also allows your LevelDB instance to be exposed with credentials to allow operations under logged in user.
Credits go to the original project. The project is updated to work with latest version of Level and NodeJS with a few minor tweaks.
Note: Project was renamed to publish under npm registry with an easy to remember name.
npm install multilevel2-http
Server:
var multilevel2 = require('multilevel2-http/lib/server')
// db = levelup instance or path to db
// opts.username = (Optional) Username who will be allowed to login to this server using multilevel2 client. Username will default to user as returned by process.env.USER
// opts.password = (Optional) Password for user who will be allowed to login to this server using multilevel2 client. Password will default to process.env.PASS if specified or if not available it will be 'test'
var server = multilevel2(db, opts)
server.listen(3000)
Client:
// On node client
var multilevel2 = require('multilevel2-http/lib/client')
// Use opts to pass options to underlying multilevel2 server
// opts.username = Specify username to login to multilevel2 server
// opts.password = Specify password to login to multilevel2 server
var db = multilevel2('http://localhost:3000/', [opts])
// opts can be also specified with username, password when opening the client to connect to multilevel2 server
db.open([opts])
// now you have the complete levelUP api!
// ...except for events - for those consider level and level-live-stream
// Separating database into sections - or sublevels works too
// Use opts to specify keyEncoding, valueEncoding as appropriate for your leveldb
var sub = require('subleveldown')
const test1 = sub(db('http://127.0.0.1:9000/'), opts, 'test1')
test1.open([opts])
// -or-
var sub = require('level-sublevel')
const test1 = sub(db('http://127.0.0.1:9000/'), opts).sublevel('test1')
test1.open([opts])
$ sudo npm install -g multilevel2-http
$ multilevel2-http -h 127.0.0.1 -P 3000 -u user -p pass path/to.db
$
$ # Alternatively, enable debug to get a simple access log on your console
$ # Can help understand what sort of queries are being sent to your leveldb
$ DEBUG=multilevel2-http/server multilevel2-http -h 127.0.0.1 -P 3000 -u user -p pass path/to.db
Use get-params to pass options to LevelDB, like ?encoding=json
Get meta information about the DB.
// GET /meta
{
"compression" : false,
"cacheSize" : 8 * 1024 * 1024,
"encoding" : 'utf8',
"keyEncoding" : 'utf8',
"valueEncoding" : 'utf8',
"path" : path
}
Get the value stored at :key.
// GET /data/foo
bar
Store data at :key.
// POST /data/foo bar
'ok'
Delete data stored at :key.
// DEL /data/foo
'ok'
Store many values batched.
/* PUT /data [
{ key : 'bar', value : 'baz' },
{ key : 'foo', value : 'bar' }
] */
Do many operations batched.
/* PUT /data [
{ type : 'put', key : 'bar', value : 'baz' },
{ type : 'del', key : 'foo' }
] */
Get an approximation of disk space used to store the data in the given range.
// GET /approximateSize/a..z
123
Get all the data.
// GET /data/12
;[
{ key: 'bar', value: 'baz' },
{ key: 'foo', value: 'bar' }
/* ... */
]
Get all data in the given range.
// GET /range/a..c
;[{ key: 'bar', value: 'baz' }]
Get all the keys.
// GET /keys
;['bar', 'foo']
Get all the keys in the given range.
// GET /keys/a..c
;['bar']
Get all the values.
// GET /values
;['baz', 'bar']
Get all the values in the given range.
// GET /values/a..c
;['baz']
// server
var level = require('multilevel2-http/lib/server')('my.db')
level.listen(3000)
Start serving on the given port.
The stored db and meta data exposed.
By default, all requests to server are CORS enabled to '*'.
Access-Control-Allow-Origin: *
Most likely, the following would be upcoming in future versions-
(MIT)
Copyright (c) 2018 Shantibhushan Naik <visitsb@gmail.com>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
Access a leveldb instance from multiple processes over HTTP
The npm package multilevel2-http receives a total of 4 weekly downloads. As such, multilevel2-http popularity was classified as not popular.
We found that multilevel2-http 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
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.