Gaetano Giunta

Ok, thanks for the insight. Keep up the good work :-)

PS: I must admit that I've been using KeePass 1 and 2, and they never crashed on me once :-D

Hello. Excuse my ignorance on the matter - maybe this is already implemented, or it makes no sense whatsoever for keepass - I might look like an incompetent fool with this proposal. However, here it is: I have recently been working on an application (server-side, written in php) for the developer of VeraCrypt, designed to gather anonymised data of crash reports such as program version info, stack trace, etc. The app has not yet been put online, but it is basically complete. It is quite simple, with,...

@idrassi I have created a new branch which changes the interaction between VC and the CC: - GET is used by default instead of POST - if there are errors in the data, an html page is shown instead of a plaintext one - the names of the query string args are the same as in the existing VC code - the php code takes care of decoding the custom format used by VC to send call stack data See: https://github.com/veracrypt/VeraCrypt-CrashCollector/compare/master...gggeek:gg/fix-interactin-with-vc?expand=1...

Honestly, this goes beyond what I expected for this feature and it is evolving into a dedicated project for reusable crash reporting. Indeed, I am also surprised at how much code had to be written to achieve the required functionality :-D On one hand, I might have avoided putting in all the extension points and layers and flexibility; on the other hand, I had more free time than planned, and indeed it would be nice if this ended up being used by other projects too! Given the call stack example, I...

Yes, filling out the form is all that is needed. You might have to specify the names of all the collaborators you are asking licenses for, and mention the fact that there are more than one github repo involved. Getting the licenses is not a given though - they used to be much more liberal about it, but have tightened the rules over time. Human examination of the submission is involved. Licenses have to be renew every year (maybe it is 6 months now?) by basically sending an email, and they might not...

Hello hello. I messed up a bit with GitHub, and the currently open PR has been updated with the tip of my development branch. i.e. it has all functionality atm. Apart from adding tests, this is a list of possible improvements and new features which I'd like to discuss: 1. adding a pepper in the password hasher config - it is recommended by owasp best practices 2. also: set min. length for passwords / maybe other rules? 3. also: should we make user email unique? (it helps with the forgotpassword logic)...