| Author |
Topic |
|
avmreddy17
Posting Yak Master
180 Posts |
 Posted - 2006-04-19 : 11:16:02
|
| Is there a way to encrypt all the Stored Procedures in a database at a time?ThxVenu |
|
|
Srinika
Master Smack Fu Yak Hacker
1378 Posts |
Posted - 2006-04-19 : 11:18:48
|
| Yes but then even u want be able to view / editU can create users / assign roles to access the DB and limit the access by thatSrinika |
 |
|
|
avmreddy17
Posting Yak Master
180 Posts |
Posted - 2006-04-19 : 11:51:44
|
| can't I Decrypt it back again to see and edit it? |
|
|
|
Srinika
Master Smack Fu Yak Hacker
1378 Posts |
Posted - 2006-04-19 : 11:58:46
|
| Its not that straight forwardThis is what has been metioned in SQL server Help-----------------------------If you are creating a stored procedure and you want to make sure that the procedure definition cannot be viewed by other users, you can use the WITH ENCRYPTION clause. The procedure definition is then stored in an unreadable form.After a stored procedure is encrypted, its definition cannot be decrypted and cannot be viewed by anyone, including the owner of the stored procedure or the system administrator.-----------------------------U may need to use 3rd party software<snip> URL removed </snip>Srinika |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2006-04-19 : 19:49:45
|
quote:
<snip> URL removed </snip>
In the future, please do not post links on how to decrypt or otherwise circumvent SQL Server security measures. Let people use Google to find that stuff if they need it. I'd prefer not to have SQL Team become a resource for script kiddie h4X0rZ.Also, DON'T EVEN THINK ABOUT encrypting your stored procedures if you are not storing them in some kind of source control system. If you don't know about or use source control, STOP. Google for it and read all about it. Get yourself a source control system (CVS, Subversion, anything except Visual Source Safe) and put your procedure code in it. THEN you can think about encrypting it. That way, you never have to worry about decrypting your procs, because you'll never need to. |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-04-19 : 22:41:13
|
| You should not count on it to secure sensitive information, like passwords. There are tools that can be used to decrypt encrypted stored procedures, triggers, views, and functions, at least with SQL 2000 or 7.0. I don't know about 2005.There are third party tools available that offer much higher security for procedure encryption, like SQL Shield.CODO ERGO SUM |
|
|
|
PSamsig
Constraint Violating Yak Guru
384 Posts |
Posted - 2006-04-20 : 02:08:13
|
quote:
Originally posted by robvolk
[quote]<snip>... anything except Visual Source Safe ...</snip>
Why ? |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2006-04-20 : 07:57:21
|
| It doesn't stack up compared to CVS / SubVersion or the commercial alternatives like Vault.The SourceSafe checkout system reduces concurrent ability to edit files, makes it more difficult to edit files offline (e..g travelling with a laptop), and the SourceSafe repository has all sorts of horror stories about corruption which you don't hear about of the other systems.See: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=61248Kristen |
|
|
|
afrika
Master Smack Fu Yak Hacker
2706 Posts |
Posted - 2006-04-21 : 13:44:38
|
| talk to activecrypt he is a memeber of this forums or visit their website www.activecrypt.com |
|
|
|
|
encrypt all the Stored Proc