d3zd3z/gosure

File integrity implemented in Go

gosure's Issues

Add option to check other revisions

Currently check always verifies the latest revision. Add a flag so that it can also specify earlier versions from the surefile.

Better documentation

The current documentation is just barely an overview of how to use gosure. Expand this to include sample use cases, and a clearer overview.

Scan of `-d` dir doesn't work

The commands always scan from the current directory, and the -d option is always ignored.

Trying to add code to scan the dir shows that other code assumes the scan is taking place in the current directory.

MD5? Consider SHA256

Hi - While doing a quick review after seeing the project on reddit, I found myself cringing at the use of MD5. While I understand that your indented use case is not specifically security related, using MD5 specifically excludes any security related use cases. Please consider a secure cipher like sha256.

Clean up progress indicator

Instead of just logging periodic progress messages, integrate the progress meter with the logging system. Overwrite the lines unless something is printed. Look to how restic does this for inspiration.

Print progress during scan

The initial scan can take time with large filesystems (and cold caches). Print progress during this scan so the program feels like it is still working.

Scan with unreadable file panics

Encountering a file that can be statted but not read panics with "panic: Attribute sha1 is empty" when trying to write the output.

Thoughts are to make the encoder/decoder able to skip the empty attribute, or output a blank sha1 (such as all zeros).

Allow alternative hash functions

Gosure and friends (rsure, etc) all use SHA1 has the hash function. Since these programs are more oriented toward integrity and not security, it isn't that harmful to use a weaker hash function. But, the user may want to consider other tradeoffs between performance and robustness of the hash function. Maybe they want increased performance, and use something like siphash or xxhash.

Add exclusion support

Add some type of --exclude option to support exclusion.

One complication with this is that if it is specified differently on each run, it can appear that files and directories are added when it was just the exclusion that changed. One possibility is to put the exclusion into the datafile and reuse it on subsequent updates.

Add build script to allow gosure to be built outside of a workspace.

Use something like build.go from restic to make it easier for packagers and other non-go developers to build gosure.

No warning for unreadable directory

If a directory has read by not 'x' permission, it is silently ignored. Perhaps this should print a warning at least.