datavaccinator / dv-vault Goto Github PK

If the target file and some config file is already found, we may ask for a simple executable update.

If user says YES, we only stop the service, update the executable, run some optional update script and restart the service.

Instead of IP whitelisting with ID and password, we might also support oAuth 2.0 for client authentication.

Currently, the search hash is built like this:

• Hash the word character by character
• Add random bytes to the generated hash

The drawbacks are:

• False positive hits during search for words with the same beginning and random matches
• The entropy for the word length is only added by max 3 characters

As a suggestion, we might build the hash like this:

• Add a NULL byte to the word
• Add random bytes to the word until it reaches the size of 16 characters. Use 32 if the word is longer than 16 characters.
• Hash the word character by character

Benefits:

• Enhanced entropy for the words
• Impossible to predict anything by the length of the search hash (all 16 or 32 bytes)
• Eliminate possible false positives during search

The client executable may get command line options to add/update/delete providers.

By using the same executable, all database functionality is already available and does not need any duplication.

Today, the VIDs and searchwords are submitted as a space separated string. The protocol API should alternatively support an array of strings, too.

Affected protocol operations:

• getpublished
• get
• delete
• search

The check protocol call should return the limits for max payload, max searchword length and max publish duration.

Allow submitting own VID in ADD function. In this case, we need to verify uniqenes and return error in case it is not unique.

Currently, authentication uses sid and spwd values from json form field. This generates overhead if a service provider has to supplement a call with those values (decode, add, encode).

Instead of this, we might accept sid and spwd as additional form key/value parameters. This will stop the service provider from having to decode and encode the json parameter.