SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Encryption


Encryption

Author
Message
SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (144K reputation)SSC Guru (144K reputation)SSC Guru (144K reputation)SSC Guru (144K reputation)SSC Guru (144K reputation)SSC Guru (144K reputation)SSC Guru (144K reputation)SSC Guru (144K reputation)

Group: General Forum Members
Points: 144773 Visits: 18651
Kenneth Wymore (3/23/2010)
Not to be too picky but if cell level encryption was available since SQLServer 7 wouldn't SQLServer 7 have been the correct answer? Even if it was undocumented and poorly performing, it was still technically available, correct?



Though that hash function was available, it provided no means to be able to retrieve the data unencrypted and is still somewhat different than the feature at the premise of the question.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Learn Extended Events

SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (144K reputation)SSC Guru (144K reputation)SSC Guru (144K reputation)SSC Guru (144K reputation)SSC Guru (144K reputation)SSC Guru (144K reputation)SSC Guru (144K reputation)SSC Guru (144K reputation)

Group: General Forum Members
Points: 144773 Visits: 18651
Nice Question. It was good to have this question and discussion.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Learn Extended Events

Ric Sierra
Ric Sierra
SSCommitted
SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)

Group: General Forum Members
Points: 1855 Visits: 342
vk-kirov (3/23/2010)
Ric Sierra (3/22/2010)
this undocumented function is available since SQLServer 7

PWDENCRYPT is a hash function, which means it's a one-way function. Once hashed, data cannot be restored. With cell-level encryption, data can be both encrypted and decrypted.


Is a semantic issue. The question is open, looking for the SQL Server version where Encryption (call as you wish: Hash function, two way encryption, masking, obfuscating, base64) can be done.
Paul White
Paul White
SSC Guru
SSC Guru (79K reputation)SSC Guru (79K reputation)SSC Guru (79K reputation)SSC Guru (79K reputation)SSC Guru (79K reputation)SSC Guru (79K reputation)SSC Guru (79K reputation)SSC Guru (79K reputation)

Group: General Forum Members
Points: 79938 Visits: 11400
Complete guess, but correct. Thanks for the question.



Paul White
SQLPerformance.com
SQLblog.com
@SQL_Kiwi
Ken Wymore
Ken Wymore
SSCrazy Eights
SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)SSCrazy Eights (9.6K reputation)

Group: General Forum Members
Points: 9618 Visits: 2470
Thanks for the explanation! Makes more sense now.
Matt Miller (4)
Matt Miller (4)
SSC Guru
SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)SSC Guru (68K reputation)

Group: General Forum Members
Points: 68066 Visits: 19995
Ric Sierra (3/24/2010)
vk-kirov (3/23/2010)
Ric Sierra (3/22/2010)
this undocumented function is available since SQLServer 7

PWDENCRYPT is a hash function, which means it's a one-way function. Once hashed, data cannot be restored. With cell-level encryption, data can be both encrypted and decrypted.


Is a semantic issue. The question is open, looking for the SQL Server version where Encryption (call as you wish: Hash function, two way encryption, masking, obfuscating, base64) can be done.



Sorry - i have to bite on this one: under which circumstances do any of the following qualify as "encryption"
- Base64 (it's an enCODING technique, it's certainly NOT an encryption method)
- Obfuscation (the process of making names of constructs and objects very confusing so that code becomes difficult to follow)
- hash function: a function to turn a variable length value to an integer to speed up comparison.

Calling those things the same thing as "encryption" is really comparing apples to oranges.

----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Peter Trast
Peter Trast
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1740 Visits: 655
Matt Miller (#4) (4/1/2010)
Ric Sierra (3/24/2010)
vk-kirov (3/23/2010)
Ric Sierra (3/22/2010)
this undocumented function is available since SQLServer 7

PWDENCRYPT is a hash function, which means it's a one-way function. Once hashed, data cannot be restored. With cell-level encryption, data can be both encrypted and decrypted.


Is a semantic issue. The question is open, looking for the SQL Server version where Encryption (call as you wish: Hash function, two way encryption, masking, obfuscating, base64) can be done.



Sorry - i have to bite on this one: under which circumstances do any of the following qualify as "encryption"
- Base64 (it's an enCODING technique, it's certainly NOT an encryption method)
- Obfuscation (the process of making names of constructs and objects very confusing so that code becomes difficult to follow)
- hash function: a function to turn a variable length value to an integer to speed up comparison.

Calling those things the same thing as "encryption" is really comparing apples to oranges.


Pile on... I agree. Thanks for not being as lazy as me...

Peter Trast
Microsoft Certified ...(insert many literal strings here)
Microsoft Design Architect with Alexander Open Systems
Ric Sierra
Ric Sierra
SSCommitted
SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)

Group: General Forum Members
Points: 1855 Visits: 342
Matt Miller (#4) (4/1/2010)
Ric Sierra (3/24/2010)
vk-kirov (3/23/2010)
Ric Sierra (3/22/2010)
this undocumented function is available since SQLServer 7

PWDENCRYPT is a hash function, which means it's a one-way function. Once hashed, data cannot be restored. With cell-level encryption, data can be both encrypted and decrypted.


Is a semantic issue. The question is open, looking for the SQL Server version where Encryption (call as you wish: Hash function, two way encryption, masking, obfuscating, base64) can be done.



Sorry - i have to bite on this one: under which circumstances do any of the following qualify as "encryption"
- Base64 (it's an enCODING technique, it's certainly NOT an encryption method)
- Obfuscation (the process of making names of constructs and objects very confusing so that code becomes difficult to follow)
- hash function: a function to turn a variable length value to an integer to speed up comparison.

Calling those things the same thing as "encryption" is really comparing apples to oranges.



All your definitions are correct, but the in the context of make a "text" unreadability all the options can be.
Tom Thomson
Tom Thomson
SSC Guru
SSC Guru (50K reputation)SSC Guru (50K reputation)SSC Guru (50K reputation)SSC Guru (50K reputation)SSC Guru (50K reputation)SSC Guru (50K reputation)SSC Guru (50K reputation)SSC Guru (50K reputation)

Group: General Forum Members
Points: 50780 Visits: 13159
Ric Sierra (4/1/2010)
Matt Miller (#4) (4/1/2010)
Ric Sierra (3/24/2010)
vk-kirov (3/23/2010)
Ric Sierra (3/22/2010)
this undocumented function is available since SQLServer 7

PWDENCRYPT is a hash function, which means it's a one-way function. Once hashed, data cannot be restored. With cell-level encryption, data can be both encrypted and decrypted.


Is a semantic issue. The question is open, looking for the SQL Server version where Encryption (call as you wish: Hash function, two way encryption, masking, obfuscating, base64) can be done.



Sorry - i have to bite on this one: under which circumstances do any of the following qualify as "encryption"
- Base64 (it's an enCODING technique, it's certainly NOT an encryption method)
- Obfuscation (the process of making names of constructs and objects very confusing so that code becomes difficult to follow)
- hash function: a function to turn a variable length value to an integer to speed up comparison.

Calling those things the same thing as "encryption" is really comparing apples to oranges.



All your definitions are correct, but the in the context of make a "text" unreadability all the options can be.

A semantic issue - certainly. What are the semantics of the phrase "Cell-level Encryption" which is the phrase used in the question? They are absolutely clear: "Cell-level Encryption" means the function provided to encrypy a column so that its values can be recovered using the appropriate key and only (unless someone breaks the cipher) using that key.
The password hashing function in SQLS 7 certainly didn't provide that function. So the semantic issue is quite cleqar, anmd the answer "SQLS 7" is completely wrong.

Tom

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search