Collaborative Viper

[botherder]

As initiated in #147, let's discuss here what would be the requirement for introducing collaborative support into Viper.

Integrating Git could be an easy solution for a collaborative setup, although the main problem would be replacing the SQLite database with an alternative flat text database. This could be an option: https://github.com/adewes/blitzdb

Now, as we're not storing any command results in a database now, the collaborative aspect is very limited to just binaries and their metadata.

[morallo]

Maybe a little hacky, but COOPY could do the trick for keeping SQLite: http://share.find.coop/doc/tutorial_git.html#tutorial_git_config_sqlite

[botherder]

That's interesting, certainly something to consider. The interesting thing about BlitzDB is that it's fundamentally JSON, which could potentially let us introduce some interesting options to store commands results in the database as well.

[jaegeral]

but wouldn`t we need some kind of user management as well to collaborate?

I would dream about a tool that enables me to reverse a file together with others, exchange notes, results, findings etc. Is that the path you are thinking of @botherder?

[XVilka]

In https://github.com/radare/radare2 we're using https://github.com/radare/sdb - simple key-value database, on top of modified CDB from DjB.

[botherder]

@deralexxx If we integrate git, authentication and user management is done at the git server level.

@XVilka Sounds interesting, I'll look into it. Thanks.

[botherder]

I'm boosting this to revive some discussion as I think it would be great to have.