You are viewing a single comment's thread from:
RE: Let Zappl Clerify some things. FUD Correction
Seems you don't save keys, but if they so happen to be leaked in logs, the fix for that will take weeks?
I am not impressed by how you handled this and will advise everyone to change their keys if they used zappl.
Should you have the fix live at some point, please comment on the github issue.
No this fix shouldn't take weeks. Also the issues is the node crashes well we load balance so the chances are low. But just in case we will be adjusting what is logged in the failure of said transaction.
Zappl didn't try to hide anything, just not used to having to comment on bug reports. This is our first Open source project so we wasn't used to always given feed back. But as you stated it was unprofessional of us to just look over problem.
@thedegensloth and @inertia have talk about this issue before privately before. But till today it didn't reach the point of were we found the bug report saving issue which has never occurred.
We were being truthful when we said we didn't store keys, but there was a issue we didn't think about. Which is why zappl is open source. So we've been working on browserify methods which will be coming.
But the temp method will be modifying what shows up in the logs. We thank you for your concern and realize our fault and hope we can continue to earn everyone trust.
Thank you for this! Being open source means accepting that there will be bugs and reacting to them publicly. And I am glad that you are open about this issue.