Re: TripleDES output size
- From: Arturo Buonanni <leave_this_out_deer.chief.this.also@xxxxxxxxx>
- Date: Wed, 11 Oct 2006 14:55:10 +0200
On Tue, 10 Oct 2006 10:21:02 -0500, "Joe Kaplan"
<joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
It is probably a good idea to use either Unicode or UTF-8 if you may need to
support non-ASCII characters, as you'll have much better luck getting the
data back into the right format when you decrypt if you just use Unicode
consistently. That's what it is there for.
You could save some actual size in some cases by using UTF-8, but since it
is variable length, it will be harder to predict how big the encrypted data
will be. Using Unicode, if your strings have a maximum length, your size
will be very predictable.
You also have the option of not storing the data in SQL as string but as
binary instead. That will save you 1/3 with the overhead generated by
base64, but you'll have to be a little more careful getting the data in and
out of the database. Base64 is easiest.
I'd suggest trying not to worry about it too much and just making your SQL
columns be the size they need to be. :)
That's the way I'm going.
Thanks again.
.
- References:
- TripleDES output size
- From: Arturo Buonanni
- Re: TripleDES output size
- From: Valery Pryamikov
- Re: TripleDES output size
- From: Arturo Buonanni
- Re: TripleDES output size
- From: Joe Kaplan
- Re: TripleDES output size
- From: Arturo Buonanni
- Re: TripleDES output size
- From: Joe Kaplan
- TripleDES output size
- Prev by Date: IL code fails with VerificationException
- Next by Date: Re: TripleDES output size
- Previous by thread: Re: TripleDES output size
- Next by thread: Re: TripleDES output size
- Index(es):
Relevant Pages
|
