# Krab: Encrypted IPFS Keystore Management

**URL:** <https://discuss.ipfs.tech/t/krab-encrypted-ipfs-keystore-management/4325>\
**Category:** Ecosystem and Usage\
**Tags:** go-ipfs\
**Created:** [November 23, 2018, 9:10pm UTC](https://discuss.ipfs.tech/t/krab-encrypted-ipfs-keystore-management/4325 "2018-11-23T21:10:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![postables](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/postables/32/2729_2.png) [@postables](https://discuss.ipfs.tech/u/postables)\
**Post date:** [November 23, 2018, 9:10pm UTC](https://discuss.ipfs.tech/t/krab-encrypted-ipfs-keystore-management/4325/1 "2018-11-23T21:10:36Z")

</div>

tl;dr: encrypted IPFS keystore management [https://github.com/RTradeLtd/rtfs/tree/v0.3.3/krab](https://github.com/RTradeLtd/rtfs/tree/v0.3.3/krab)

It’s been pretty frustrating for a long time that the only option for storing IPFS keys was in a method that can be used by existing IPFS projects was storing them in plaintext on disk, or in memory which is a gigantic security risk for anyone running IPFS nodes long-term, or as a service.

RTrade Technologies ltd just recently released an open-source keystore manager named Krab, which allows you to store your IPFS keys in an encrypted datastore, while maintaining compliance with the `Keystore` interface that is specified in `go-ipfs-keystore`. Thus `krab` can easily be used in place of the filesystem, and memory keystore that `go-ipfs` and the multitude of other IPFS proejcts use.