KVS
Key Value Services is a cli tools that help to you create your Key-Value store services.
Motivation
I want to create a content sharing tool that is managed by only one person and readable by many people in a secure network environment, so that I can use some common content in the terminal.
Install
Warning
This project is still in the early stage of development and is only used as a development tool. Do not use it for data storage in the production environment. If you have this requirement, I recommend that you use redis. Some APIs will undergo destructive changes without notice.
Usage
- Start kvs in your server
> kvs
- Login the kvs services from client
> kvs
- Create a private key value
> kvs create foo "hello world"
default, kvs will encrypt the value use your priv_key in local. Remote just judge the key's owner. The decryption process needs to be completed by the client itself.
- Read a key
> kvs read foo
hello world
- Create a public key value
> kvs create priv_foo "priv hello world" -p
If you just do. kvs will send the value and save value as plaintext in remote.
- Read a private key
> kvs cat priv_foo
priv hello world
- Delete a Key
> kvs delete priv_foo
You just can delete key that owner is you.
- Update a Key
kvs create priv_foo "this is change data"
kvs read priv_foo
this is change data
- show remote info
> kvs remote
0.1.3
- show local info
> kvs local
scope: 0x4d7153428dd617a410f114468d212a9cd1b7ccd0
pub: MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD9qWAweIhnLfBdjYj8oty1z2FYycQ8qhebrDLCQBJPTF1IfV282WCHET7Fsjd1C9+XMbW2xT0f73cZgSExgILeGjZFlx9gEf5VVJyBezfQ6yU2V9Emo58zRh6fjfoBGUsXmVIJIGCpnVjHg/ECEVKuDVQ3h0SEHrdxE98bSl9RIQIDAQAB
- Read other scope key
> kvs read -s 0xad359ae3e478342ed2b5512ed7ff4ebb3ceb2dd test_pub
pub content
- Restart the kvs Server
> kvs restart
- Stop the kvs Server
> kvs stop
- remove all keys
> kvs list | awk -F '\t' '{print "kvs delete " $2}' | bash
Examples
Case1 sync info in one team
Your team have a big list of resource id.
# important_resource_id.txt
Some times, the team member need create the url by the big list.
# important_resource_urls.txt
Let's assume we have written a command line tool named transform to handle this case.
cat important_resource_urls.txt | transform
The question is, how do I share important_resource_urls.txt with other team members.
Granted, there are many ways to share it. But you can fast finish it if you use the kvs.
# create the key
# and then, other team member can use it.
|
Case1 sync info in public
| |
Case2 prove yourself
You can tail your pub key to some website.
> kvs local
scope: 0x4d7153428dd617a410f114468d212a9cd1b7ccd0
pub: MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQD9qWAweIhnLfBdjYj8oty1z2FYycQ8qhebrDLCQBJPTF1IfV282WCHET7Fsjd1C9+XMbW2xT0f73cZgSExgILeGjZFlx9gEf5VVJyBezfQ6yU2V9Emo58zRh6fjfoBGUsXmVIJIGCpnVjHg/ECEVKuDVQ3h0SEHrdxE98bSl9RIQIDAQAB
Website will tail you a cipher text.
website: (your pub key) + (random value) -> (cipher text)
Now you can use kvs de command to decrypt the (cipher text)
> kvs de (cipher text)
(random value)
Tail the (random value) to website. you will prove yourself to website.
Road Map
Community
-
add
synccommand to sync all file in one directory and use the relative directory as key. -
add
listcommand to list all key meta in your scope. -
add
restartcommand to restart the server. -
add
stopcommand to stop the server. -
add
setandgetcommand to config some value in client local. -
add
setcommand to set the config in client local. -
add
--fileoption in create and upload command. -
add the same option in
synccommand look likecreateupdate. -
append show public key in
kvs local. -
add
kvs decommand to decrypt some content. use local private key by default. -
add
kvs encommand to encrypt some content. use local public key by default. -
remove
--scopeoption in read, you can usekvs read your_scope:some_keyto read a public key. -
add
kvs set whitelistcommand to set a whitelist. -
add
kvs searchcommand to search some content in different repository. -
fix
--fileoption in create and upload command can be not give the filename, kvs will use the stdin content as value if you do that. -
add server config to config the store backend.
-
add unit test and docs.
-
add github action to release the bin file. -
refactor the
Remote Actionmodel. -
refactor the
aes sessionto be aaes stream. -
config docker container.
-
``
Commercial
- add the p2p in share key progress.
- Build a free central storage node.
- add
upgradecommand to sync the remotekvscli to client local.