Microsoft SQL Server
 
Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
 
 
User Name:
Password:
Remember me
Go Back   ASP Free ForumsDatabaseMicrosoft SQL Server

Reply
Add This Thread To:
  Del.icio.us   Digg   Google   Spurl   Blink   Furl   Simpy   Y! MyWeb 
Thread Tools Search this Thread Rate Thread Display Modes
 
Unread ASP Free Forums Sponsor:
  #1  
Old December 8th, 2003, 11:25 AM
asr asr is offline
Contributing User
ASP Free Newbie (0 - 499 posts)
 
Join Date: Oct 2003
Posts: 40 asr User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: 26 m 12 sec
Reputation Power: 6
Question Encryption

I want to do encryption of the password field in the database. I have read about the encrypt(), pwdencrypt(), pwdcompare() functions. Here are some questions that i am concerned about.

a) Does using a standard SQL function that could be called in a script make the data susceptible to dictionary-style attacks?

b) How long would the field need to be in the database and of what type to store the encrypted text?

But is there any other way other than the above three functions so that i can have the contents of the field encrypted?? Please let me know if there any encryption algorithms are available.

Please let me know.

Reply With Quote
  #2  
Old December 8th, 2003, 02:43 PM
Scorpions4ever Scorpions4ever is offline
Mad Rater
ASP Free Newbie (0 - 499 posts)
 
Join Date: Sep 2003
Posts: 126 Scorpions4ever User rank is Corporal (100 - 500 Reputation Level)Scorpions4ever User rank is Corporal (100 - 500 Reputation Level)Scorpions4ever User rank is Corporal (100 - 500 Reputation Level)Scorpions4ever User rank is Corporal (100 - 500 Reputation Level) 
Time spent in forums: 11 h 31 m 44 sec
Reputation Power: 8
(a) Any encryption scheme is vulnerable to a dictionary attack. It is basically a brute force technique, so the defence against this is to not use passwords that can be found in a dictionary.
(b) VARBINARY(255) ought to be long enough (at least most of the docs I've seen indicate this).

Be aware though that these functions are undocumented by Microsoft. So they don't have to necessarily support/port them to future versions of SQL Server. Also, the algorithm was changed between SQL Server 6.5 and 7.0, so data encrypted with 6.5's PWDENCRYPT would not equal the password which was compared with 7.0's PWDCOMPARE. This caused programs to break for people who were upgrading their databases from 6.5 to 7.0. Who knows, maybe Microsoft may change the encryption scheme again in the next version of SQL server.

You could always use the front end language (PHP, Perl etc.) to do an MD5 hash and store that into the database. This might be a safer alternative to using an undocumented MS function

More reading: http://www.sqlmag.com/Articles/Index.cfm?ArticleID=9809
__________________
Up the Irons
What Would Jimi Do? Smash amps. Burn guitar. Take the groupies home.

Reply With Quote
Reply

Viewing: ASP Free ForumsDatabaseMicrosoft SQL Server > Encryption


Thread Tools  Search this Thread 
Search this Thread:

Advanced Search
Display Modes  Rate This Thread 
Rate This Thread:


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox
Forum Jump


Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
  
 





© 2003-2008 by Developer Shed. All rights reserved. DS Cluster 2 hosted by Hostway
Stay green...Green IT