>> I expressed surprise that the software would have received government certification if it was set up wrongly from a security perspective. Only your supplier/developer can go through this with you and explain what (if anything) you need to do.

At 06:53 p.m. 7/01/2014, Marc Hakman wrote:

>>
>Every client has a pw and different rights: the cabinet. In my view, the database file with the unchanged default admin account name and pw is the missing rear wall. Is that correct?

If the SYSDBA password is 'masterkey' then YES, your assessment is correct.

>>> It is possible to sent you a personal mail? Uncleared ist my problem with the chip card.
>>
>> No; except in the context of a support arrangement with IBPhoenix.
>>
>OK. So youraccount@... is blocked.

The account helebor@... is not blocked out here. It is a different matter if it is being blocked by your mail server.

>Still untouched: patient chip card.
>Where can I find info about the possible risks of patients chip cards. In your books?

Not in my books. I'm not even sure what you are talking about. I suppose it must be some kind of smartcard storing patient data that can be read by a dedicated reader device.

> How can I read out, wether they do something / nothing with my database file.

I guess that the authority that issues these cards must have some information available about the data format and the device API, so that people like your software developer can write applications to read from the card and (if supported) write to it.

I have never heard of a smartcard that could log into a database as SYSDBA, I must confess! That would be some amazing wee beastie. ()()()()()()()()(^ ^)

> I don�t like to trust not trust my developer, because he has interest in selling and therefore in certification; not in the security of my database files (= patients and financial company files).

Really? I thought the primary reason for certification was quality assurance, of which data security is a significant part and customer support is another. I get the impression that you haven't made contact with the software support people about this chip card issue.

>Could an arrangement with IBPhoenix be helpful?

Possibly; although the chip card issue is more likely to be in the bailiwick of one of my European colleagues than in mine, down here in Australasia.


Helen Borrie, Support Consultant, IBPhoenix (Pacific)
Author of "The Firebird Book" and "The Firebird Book Second Edition"
http://www.firebird-books.net
__________________________________________________________________