to be honest there's little point as anyone can download a proc to decrypt them. .. but -- script them all out and do a find and replace on the as to with encryption as
If you want to protect the procs a far better way is to restrict the permissions on syscomments - that way the procs can't be viewed.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/