Closed ZopharShinta closed 5 years ago
When @miles200 reverted to a prior release and rebuilt, the dbtool.exe
hash changed. Whenever the binary is modified, the hash needs to be updated in register.cgi
under the web directory. It is an added layer of security for now as we would not want to execute something that has potentially been tampered with. In the future, we'll likely use SQL queries instead of executing dbtool
directly to avoid having to do this. The hash has been updated and registration is working properly again.
Good to know, thanks Dilleys!
On Wed, 3 Apr 2019 at 04:19, Lloyd Dilley notifications@github.com wrote:
When @miles200 https://github.com/miles200 reverted to a prior release and rebuilt, the dbtool.exe hash changed. Whenever the binary is modified, the hash needs to be updated in register.cgi under the web directory. It is an added layer of security for now as we would not want to execute something that has potentially been tampered with. In the future, we'll likely use SQL queries instead of executing dbtool directly to avoid having to do this. The hash has been updated and registration is working properly again.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Segs/Segs.io/issues/30#issuecomment-479318186, or mute the thread https://github.com/notifications/unsubscribe-auth/Ah0_auvw78fVpdkWe6MNmHuDbNgtvUrHks5vdB3IgaJpZM4cZbb_ .
I'm getting a hash error trying to create an account through https://red.segs.io/register.cgi