On Mon, Apr 22, 2019 at 1:18 PM whitehexagon via golang-nuts < golang-nuts@googlegroups.com> wrote:
> Thanks everyone, plenty more reading for me! > .... > The argon2 looks interesting, but it sounds like it could be very memory > heavy. The code I'm porting is running on a PAAS/SAAS setup, and that > might have cost implications exceeding the worth of my low value data. > Try to not judge the value of your data as being low. Store only hashed and salted passwords and data. Passwords in the clear or stored in a lame or fragile manner is something that gets negative and snarky press world wide. Data at rest should be safe. Revisions to update to a better solution might be hampered if you start out thinking your data is low value and success happens. The size of a go program is likely darn close to the netsum memory footprint of a C program and the resident set size might be smaller with go. Plan ahead. -- T o m M i t c h e l l -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
