Feature #2099

Updated by Szilárd Páll over 3 years ago

__We We should come up with a robust and secure way to share accounts/credentials related to the GROMACS infrastructure. If only X knows the password because he/she set up the machine/service is bad. Not having access to a s compiler because only Y knows the Intel account's credentials is silly. Using crappy passwords just because they're easy to remember is a bad excuse.

I'd think a password database with strong encryption and strong master pass (+ key?) would be best. I'd recommend keepass, it has clients for everything, so it mostly just works, but there could be even simpler/better alternatives.

I know a single point of failure is not ideal, but some of the current practices are just poor, don't scale, and don't allow sharing responsabilities.