I'm trying to change the default passwords that come with v1.02 (Mac) as
well as create some new ones with various privileges. I have successfully
changed the default passwords, and can open ebase with these changed
passwords without incident. When I try to create new passwords, however, I
am not able to open ebase correctly. Here's what happens:
When I open ebase.102, I enter my new password ("maiden" for example).
Initially, this appears to work, but quickly I am asked to enter a password
for every file ebase is attempting to open (e.g., "Custom," "Help," "Notes,"
"Payments," etc).
Furthermore, I get an error message saying my new password (i.e., "maiden")
is not valid. I have to open all files with my previously created "master"
password ("yoda" in this case) in order to gain access to the home screen,
and even then things don't work quite right (i.e., subsequent password
dialogue boxes will occasionally pop up). If, however, I close ebase and
open it again using my master password ("yoda"), everything works fine.
So, it would appear that one can rename the default passwords that come with
ebase, but not create new ones. Is this correct? Is there a fix?
I know the ebase programmers are hard at work on version 2, but if this is a
systemic problem with verion 1.02, then I would think that it would call for
a bug fix. I want to convince my local school system that they can
confidently share information with us with no qualms about security, but
this will "put a nail in that coffin" (or "lockbox" as Al might say) if I
can't get ebase security protocols working.
TIA,
Colin
