Yes, I did. But that is the same concept that we discussed here. If we had their resources, I would also argue that FB should do such thing too. But this feature is rather orthogonal to the primary task of the database engine. It is protection against hostile environment, not against authenticated users of the database.

However things like column-based security, possibly with encryption, is completely different story.

Roman

PS. Sorry for quoting the whole email, but so far it is almost impossible to cut big portions of text on android phones without hardware keyboard.



"ettotev" <emilt@...> schrieb:

>
>
>--- In Firebird-Architect@yahoogroups.com, Roman Rokytskyy <roman@...>
>wrote:
>
>> I deliberately wrote that Oracle / MS SQL have different approach.
>Some
>> time ago I invested some time to check whether it would be feasible
>for
>> FB to implement something similar to what they do.
>>
>> In few words, one part of their security concept addresses the issue
>of
>> encrypting sensible information in some columns while leaving the
>> database operational for the normal users (they would see encrypted
>data
>> unless a key is stored in the session).
>>
>> This goes in the direction of the column-based security and might be
>> quite interesting topic directly related to the database engine...
>>
>> Roman
>>
>
>Roman,
>Did you look at the links where TDE (Transparent Data Encryption) is
>discussed? This is for both MSSQL and Oracle. It seems to be relatively
>new so you may have missed it last time.
>
>
>
>------------------------------------
>
>Yahoo! Groups Links
>
>
>

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.