On Thu, 13 Jul 2006 15:32:26 -0400, "Steven"
<Lazans@xxxxxxxxx> wrote:
What is the recommended way to store data in SQL Server 2000 encrypted so
not even DBA can see the values? I know SQL 2005 has encryption at the row
level, but what are my options in SQL 2000?
Re: Usenet Fuckology-101 ... as links to this faq... is the security faq from the ng that caused ... Security and Encryption FAQ Revision 15 ... Revisions in this version of the FAQ include BestCrypt version 6. ... (sci.space.policy)
Re: how to decrypt an encrypted stored proc in 2005 ...SQL 2005 still obfuscates object encryption in a similar manner to SQL 2000. ...tinyint,@procNameLength int ... SELECT @BasePos = 1 ... (microsoft.public.sqlserver.security)
Re: how to decrypt an encrypted stored proc in 2005 ... remove the feature for the same reason. ... Using a stronger encryption algorithm... So the feature is unchanged in SQL 2005 from SQL 2000. ... SELECT @BasePos = 1 ... (microsoft.public.sqlserver.security)
Re: Encryption of application configuration block ... If your trying to protect an Sql login password then instead create an Sql ... access to Sql Server objects based on the current users' Windows account. ... If your really must encrypt your connection strings here are some links, ... I come to secure the app.config file via encryption.... (microsoft.public.dotnet.general)
Re: how to decrypt an encrypted stored proc in 2005 ... Everyone that cares needs to realize that object "encryption" in SQL 2005 is ...tinyint,@procNameLength int ... SELECT @BasePos = 1 ... (microsoft.public.sqlserver.security)
