Generating a cryptographically secure random string is a useful feature to have both outside the context of an entry and outside the context of an open database file. For example, if you're creating a database file for the first time, you'd want to be able to generate that password for it securely, but you don't yet have a file. Copy the generate password functionality out of entry and make it usable from any of the artifact files; for example, perhaps it can go into the header of all loader pages or into the footer.
The biggest challenge here is where to put it and is it worth the change: in the loader or the artifacts it'd need a kw- message, which adds bulk for a non-essential function, which seems like a bad trade.
Generating a cryptographically secure random string is a useful feature to have both outside the context of an entry and outside the context of an open database file. For example, if you're creating a database file for the first time, you'd want to be able to generate that password for it securely, but you don't yet have a file. Copy the generate password functionality out of entry and make it usable from any of the artifact files; for example, perhaps it can go into the header of all loader pages or into the footer.
The biggest challenge here is where to put it and is it worth the change: in the loader or the artifacts it'd need a kw- message, which adds bulk for a non-essential function, which seems like a bad trade.