[FEATURE-REQ] SHA256 of geohashes in the intersection code about safeplaces-dct-app HOT 4 OPEN

My view is that these should use a slow hash algorithm, and scrypt is my favoured approach for various reasons detailed here:

https://pathcheck.atlassian.net/wiki/spaces/TEST/pages/61112371/Design+for+MVP1+HA+JSON+Changes

from safeplaces-dct-app.

@tremblerz - If I'm reading your issue description correctly, #806 is the first step in this process that can be done independently, and this can be added only after #806 is finished. Did I understand that correctly?

from safeplaces-dct-app.

For anyone who wants to work on tis please see Jira SAF-268 for a proposed alternate plan of attack.

Same basic outcome, but proposing different sequencing to ensure Safe Paths & Safe Places retain compatibility as much as possible during this change.

from safeplaces-dct-app.

To clarify, we're going to hash the concatenation of the geohash and timestamp using Scrypt, not SHA256

from safeplaces-dct-app.