If I understand correctly, you don't need to know that - since I'm
referencing a database that does not yet exist ("C:\\Windows\\Temp\\exploit")
I can get away with specifying default credentials - "sa" with no password.
And that is what actually caused my original question - how can we secure
this default setup properly? Is there a way to disable the original "sa"
user with no password for a newly created database? Or maybe prevent
automatic creation of a new database in this scenario?
Thanks!
On Thursday, November 1, 2018 at 1:35:47 PM UTC-4, Noel Grandin wrote:
>
> thanks, but that assumes you know the username and password to access the
> db
>
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
