kin-backup | Secure , simple backups for your next of kin | Continuous Backup library

by pcrockett Rust Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | kin-backup Summary

kin-backup is a Rust library typically used in Backup Recovery, Continuous Backup applications. kin-backup has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

tl;dr: Create several small encrypted backups and distribute them to a few trusted family members or friends. No individual can decrypt their own copy of the backup, but they can decrypt someone else’s. Thus when something happens to you, two trusted people together have what they need to gain access to your sensitive information. Kin is a simple system that creates backup packages for your relatives to keep locked away in fire safes, safe deposit boxes, etc. Each backup package contains an unencrypted zip archive of public documents, for things like [last will and testament] documents or [living trust] documents. It also contains an encrypted archive for things like password manager backups, two-factor authentication recovery codes, sensitive personal information, etc. Of course giving any one person such sensitive "keys to the kingdom" is arguably a bad idea. Which is why Kin prevents any one individual from being able to decrypt the backup that they have access to. Kin is designed so that you give backups to at least two different people (recommended three or more). Each person cannot decrypt their own backup, but they can decrypt a backup that someone else holds. This isn’t just to protect you from one family member going rogue, but also protects you when your trusted backup-holders experience burglary or otherwise lose track of your backups. Kin also helps generate a clear, concise, non-technical readme HTML file for your relatives. You can customize the readme however you want using a markdown template. Encryption is implemented using the widely-used and trusted [libsodium] library. That said, Kin should definitely not be used as an online backup, is definitely not meant to be given to untrustworthy people, and will definitely not protect you from the NSA.

Support

Quality

Security

License

Reuse

Support

kin-backup has a low active ecosystem.

It has 2 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

There are 11 open issues and 17 have been closed. On average issues are closed in 15 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of kin-backup is current.

Quality

kin-backup has 0 bugs and 0 code smells.

Security

kin-backup has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

kin-backup code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

kin-backup is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

kin-backup releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

It has 12 lines of code, 0 functions and 1 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of kin-backup

Get all kandi verified functions for this library.

kin-backup Key Features

No Key Features are available at this moment for kin-backup.

kin-backup Examples and Code Snippets

No Code Snippets are available at this moment for kin-backup.

Community Discussions

Trending Discussions on Continuous Backup

How to disable azure cosmos db continious backup

Consistency of Continuous backup of Azure Cosmos DB

Mongo atlas recommends cloud provider snaphots for backup - Is it effective?

QUESTION

How to disable azure cosmos db continious backup

Asked 2022-Feb-22 at 10:59

I enabled the Azure cosmos DB continuous backup for one of my Cosmos DBs.
How can I disable it? It just says you have successfully enrolled in continuous backup.

...

ANSWER

Answered 2022-Feb-22 at 10:59

I am not sure if you have seen this message in the portal when you created the account/also mentioned in the doc

"You will not be able to switch between the backup policies after the account has been created"

since you need to select either "Periodic" or "Continuous" at the creation of Cosmos Account, it becomes mandatory.

Update:

You will not see the above in portal anymore, you can Switch from "Periodic" to "Continous" on an existing account and that cannot be reverted. You can read more here.

Source https://stackoverflow.com/questions/69347197

QUESTION

Consistency of Continuous backup of Azure Cosmos DB

Asked 2021-Nov-25 at 17:15

What would be the consistency of the continuous backup of the write region if the database is using bounded staleness consistency? Will it be equivalent to strong consistent data assuming no failovers happened?

Thanks Guru

...

ANSWER

Answered 2021-Nov-25 at 17:15

Backups made from any secondary region will have data consistency defined by the guarantees provided by the consistency level chosen. In the case of strong consistency, all secondary region backups will have completely consistent data.

Bounded staleness will have data that may have stale or inconsistent data inside the defined staleness window (minimum 300 seconds or 100k writes). Outside of that staleness window the data will be consistent.

Data for the weaker consistency levels will have no guarantees for consistency from backups in secondary regions.

Source https://stackoverflow.com/questions/70099953

QUESTION

Mongo atlas recommends cloud provider snaphots for backup - Is it effective?

Asked 2020-May-19 at 10:12

MongoDB has deprecated the continuous back up of data. It has recommended using CPS (Cloud provider snapshots). As far as I understood, snapshots isn't really going to be effective compared to continuous backup coz, if system breaks, then we can only be able to restore the data till the previous snapshot which isn't gonna make the database up-to-date or close to it atleast.

Am I missing something here in my understanding?

...

ANSWER

Answered 2020-May-19 at 10:12

Cloud provider snapshots can be combined with point in time restore to give the recovery point objective you require. With oplog based restores you can get granularity of one second.

Source https://stackoverflow.com/questions/61886736

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install kin-backup

Kin Backup is created using Rust, so you need a Rust development environment.
A C compiler (cc, clang, etc.)
The libssl-dev package installed on your computer (for compiling libsodium)
The libgtk-3-dev package installed on your computer (for nativefiledialog)
Once you have Kin installed, it’s time to create an empty backup project. Recommended: Because you will probably be storing sensitive files in this backup project, you should create it in a location where drive encryption is enabled.
A public folder where you put your public files. These will not be encrypted.
A private folder where you put all your private files. These will be encrypted.
A readme-template.md file, which is a [markdown](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet) file that will be used to generate nice looking readme files for your backup recipients.
A public.zip file that contains all the files in your public folder
A private.kin file, which is an encrypted archive that contains all the files in your private folder
A readme.html file, which when opened, explains what this is and how to decrypt the backup. Notice that it shows you Alice’s randomly-generated passphrase.
A decrypt program, which if you run it, will decrypt the private.kin file when you enter either Bob’s or Chuck’s passphrase. If you try to enter Alice’s passphrase, the decryption will fail; you cannot decrypt Alice’s backup with Alice’s passphrase.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: