Encryption

Question

Encryption

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply

Matt Miller (4) SSC Guru Points: 124210 More actions · Answer 1

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 SSCarpal Tunnel Points: 4392 More actions · Answer 2

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 SSCrazy Points: 2260 More actions · Answer 3

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.

TomThomson SSC Guru Points: 104773 More actions · Answer 4

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