|
Home > Archive > SQL Anywhere Feedback > July 2005 > Re: dbfhide extension
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: dbfhide extension
|
|
| Zbynek Svec 2005-05-23, 7:24 am |
| We would like to avoid misuse of configuration file from one
database utility (for example dbtran) with another utility
(for example dbunload).
We are using dbfhide for hiding connection string with DBA
password, but we still need to freely change all other
parameters. So we have hidden configuration file only with
connection string. Other parameters are entered in command
line.
Unfortunately everybody can use our protected "connection"
file with another database utility having @data parameter.
The solution is easy. Allow us to specify requested database
utility in configuration file.
Sorry for delay.
[color=darkred]
> I do not quite understand what is needed
> Can you elaborate a bit on what you are looking for?
>
> Perhaps you can give some examples.
> --
> Mark Culp
> ASA Research and Development
> ----------------------------------------------------------
> --------------- ** Whitepapers, TechDocs, bug fixes are
> all available through the ** ** iAnywhere Developer
> Community at http://www.ianywhere.com/developer **
> ----------------------------------------------------------
> ---------------
>
> Zbynek, Svec wrote:
| |
| Mark Culp 2005-05-26, 3:23 am |
| Ok, so if I understand correctly, you want a way of saying
"this configuration file which is 'hidden' is only allowed
to be used with tool 'x' (or 'y', 'z', etc) where x,y,z are
explicitly mentioned in the config file (and thus hidden)
from the user and therefore cannot be changed?
- Mark
Zbynek, Svec wrote:[color=darkred
]
>
> We would like to avoid misuse of configuration file from one
> database utility (for example dbtran) with another utility
> (for example dbunload).
> We are using dbfhide for hiding connection string with DBA
> password, but we still need to freely change all other
> parameters. So we have hidden configuration file only with
> connection string. Other parameters are entered in command
> line.
> Unfortunately everybody can use our protected "connection"
> file with another database utility having @data parameter.
>
> The solution is easy. Allow us to specify requested database
> utility in configuration file.
>
> Sorry for delay.
>
| |
| Zbynek Svec 2005-07-20, 11:23 am |
| Yes, right.
Zbynek
[color=darkred]
> Ok, so if I understand correctly, you want a way of saying
> "this configuration file which is 'hidden' is only allowed
> to be used with tool 'x' (or 'y', 'z', etc) where x,y,z
> are explicitly mentioned in the config file (and thus
> hidden) from the user and therefore cannot be changed?
>
> - Mark
>
> Zbynek, Svec wrote:
> ----------------------------------------------------------
> are all available through the ** ** iAnywhere
> ----------------------------------------------------------
|
|
|
|
|