asymmetric encryption

Is there a step by step cookbook on setting up asymmetric encryption. My
goal is to encrypt a couple of tables from one of my dataabses. Thanks!Do not use asymmetric key encryption to protect data; it is too slow for
that purpose, plus there are limitations on how large a piece of data you
can encrypt. For symmetric key encryption examples, see my blog:
http://blogs.msdn.com/lcris/ .
Thanks
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Keith" <Keith @.discussions.microsoft.com> wrote in message
news:511B39A3-071D-45D7-8C7B-C33C5E744385@.microsoft.com...
> Is there a step by step cookbook on setting up asymmetric encryption. My
> goal is to encrypt a couple of tables from one of my dataabses. Thanks!|||It's an awesome encryption blog. If anyone needs to learn
more on encryption in 2005, it's *the* resource. Just
checked your blog today - thanks for the posting the
proposed updated sp_helprevlogin. Awesome!
Thanks for all time you've put into your blog.
-Sue
SQL Server MVP
On Wed, 5 Apr 2006 10:50:02 -0700, "Laurentiu Cristofor
[MSFT]" <laur@.nospam.com> wrote:

>Do not use asymmetric key encryption to protect data; it is too slow for
>that purpose, plus there are limitations on how large a piece of data you
>can encrypt. For symmetric key encryption examples, see my blog:
>http://blogs.msdn.com/lcris/ .
>Thanks|||Awesome... Thanks for the help. Will this method encrypt data already in m
y
database?
"Laurentiu Cristofor [MSFT]" wrote:

> Do not use asymmetric key encryption to protect data; it is too slow for
> that purpose, plus there are limitations on how large a piece of data you
> can encrypt. For symmetric key encryption examples, see my blog:
> http://blogs.msdn.com/lcris/ .
> Thanks
> --
> Laurentiu Cristofor [MSFT]
> Software Design Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Keith" <Keith @.discussions.microsoft.com> wrote in message
> news:511B39A3-071D-45D7-8C7B-C33C5E744385@.microsoft.com...
>
>|||Yes, you can encrypt existing data. Here are some caveats: The output of
encryption is varbinary, so if you're trying to encrypt a table column that
is not varbinary, you'll need to change the table definition. The ciphertext
is also larger than the cleartext, so you may need to do this even if your
data is already varbinary; if the column is too small.
One other caveat is that we only allow encrypting values less than 8k.
See this blog entry for additional details:
http://blogs.msdn.com/yukondoit/arc.../24/496521.aspx
Note that the YukonDoIt blog is not active anymore. Raul, who wrote this
post, now has a blog at:
http://blogs.msdn.com/raulga/
Thanks
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Keith" <Keith@.discussions.microsoft.com> wrote in message
news:2654724A-2B10-4F94-B51E-C1A2B2FD7A30@.microsoft.com...[vbcol=seagreen]
> Awesome... Thanks for the help. Will this method encrypt data already in
> my
> database?
> "Laurentiu Cristofor [MSFT]" wrote:
>|||Thank you. I'm glad you found my blog posts useful.
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:q0o832t10pvevq2a0v0pl3der2q3vmfau6@.
4ax.com...
> It's an awesome encryption blog. If anyone needs to learn
> more on encryption in 2005, it's *the* resource. Just
> checked your blog today - thanks for the posting the
> proposed updated sp_helprevlogin. Awesome!
> Thanks for all time you've put into your blog.
> -Sue
> SQL Server MVP
> On Wed, 5 Apr 2006 10:50:02 -0700, "Laurentiu Cristofor
> [MSFT]" <laur@.nospam.com> wrote:
>
>|||If you use symmetric encryption do the end users, connecting with a
front-end, need to input a password to acess the encrypted data? Or will
their logging into the system grant them access to the encrypted data?
"Laurentiu Cristofor [MSFT]" wrote:

> Yes, you can encrypt existing data. Here are some caveats: The output of
> encryption is varbinary, so if you're trying to encrypt a table column tha
t
> is not varbinary, you'll need to change the table definition. The cipherte
xt
> is also larger than the cleartext, so you may need to do this even if your
> data is already varbinary; if the column is too small.
> One other caveat is that we only allow encrypting values less than 8k.
> See this blog entry for additional details:
> http://blogs.msdn.com/yukondoit/arc.../24/496521.aspx
> Note that the YukonDoIt blog is not active anymore. Raul, who wrote this
> post, now has a blog at:
> http://blogs.msdn.com/raulga/
> Thanks
> --
> Laurentiu Cristofor [MSFT]
> Software Design Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Keith" <Keith@.discussions.microsoft.com> wrote in message
> news:2654724A-2B10-4F94-B51E-C1A2B2FD7A30@.microsoft.com...
>
>|||It depends on how you design your database application. Both of these
scenarios are possible.
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Keith" <Keith@.discussions.microsoft.com> wrote in message
news:D8AE6555-A2C3-499D-838D-546F8D13092A@.microsoft.com...[vbcol=seagreen]
> If you use symmetric encryption do the end users, connecting with a
> front-end, need to input a password to acess the encrypted data? Or will
> their logging into the system grant them access to the encrypted data?
> "Laurentiu Cristofor [MSFT]" wrote:
>