Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

reverse use of encryption and decryption

2 views
Skip to first unread message

Daniel Otte

unread,
Jan 4, 2010, 8:58:27 PM1/4/10
to
Hi all,
I have a small question which I could not satisfiable answer myself:
Is it secure to use the decryption algorithm of a secure cipher for encryption
and using the encryption algorithm for decryption?
As this may be dependent on the cipher choosen, I would prefer to talk about AES
(I'm only talking about symmetric ciphers, the asymmetric stuff is quite another
thing)

The reason for considering this use is simple:
1) most cipher are optimized for fast encryption, but data is often encrypted
only once but decrypted multiple times
2) in the case of AES the code for encryption is smaller than for decryption as
you need the forward S-box for the key-schedule and the reverse S-box for the
actual decryption while encrypting onl uses the forward S-box. (in my
application this 256 bytes really matter)

best regards,
Daniel Otte

Joseph Ashwood

unread,
Jan 4, 2010, 9:28:49 PM1/4/10
to
"Daniel Otte" <danie...@rub.de> wrote in message
news:7qfkv4...@mid.dfncis.de...

> Hi all,
> I have a small question which I could not satisfiable answer myself:
> Is it secure to use the decryption algorithm of a secure cipher for
> encryption
> and using the encryption algorithm for decryption?
> As this may be dependent on the cipher choosen, I would prefer to talk
> about AES
> (I'm only talking about symmetric ciphers, the asymmetric stuff is quite
> another
> thing)

In the case of AES it is believed to be equivalent.

> The reason for considering this use is simple:
> 1) most cipher are optimized for fast encryption, but data is often
> encrypted
> only once but decrypted multiple times
> 2) in the case of AES the code for encryption is smaller than for
> decryption as
> you need the forward S-box for the key-schedule and the reverse S-box for
> the
> actual decryption while encrypting onl uses the forward S-box. (in my
> application this 256 bytes really matter)

Use CCM mode, you only need the encryption code, problem solved.
Joe

rossum

unread,
Jan 5, 2010, 8:44:51 AM1/5/10
to
On Mon, 4 Jan 2010 18:28:49 -0800, "Joseph Ashwood" <ash...@msn.com>
wrote:

Or plain CTR mode if you do not need the MAC included in CCM mode.
You would need to be very sure that a MAC was not needed though.

rossum

0 new messages